Repository navigation
fix auditing of resources addressed by name and payload filtering of on-demand resources - #154
Merged
Merged
Conversation
…dies through include
notque
requested review from
a team,
Carthaca,
fwiesel,
joker-at-work,
notandy and
sebageek
as code owners
November 2, 2026 17:53
sandzwerg
approved these changes
Nov 3, 2026
ibakshay
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ironic accepts node names in place of UUIDs, so a request like PUT /v1/nodes//states/provision was audited as compute/baremetal/node/X/Xstates with no node ID, and that on-demand resource recorded payloads the mapping had disabled for nodes. Unmapped resources now inherit their parent's payloads settings, exclude/include also cover wrapped and list bodies, unmapped children of singletons get the singleton's type URI, and the new id_environ_key option lets a service hand over the ID it resolved for a name.
Heads-up: exclude now applies at any depth, so e.g. nova's
metadataexclude also drops metadata inside action bodies, and unknown children of singletons change type URI from<service>/X...to<singleton>/X....