Fix a bug related to unnamed objects #178
Merged
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.
In the case where an object-template included an unnamed object and only one object was returned, it went into the typical
handleSingleObj
flow but markedexists
as true without settingexistingObj
in the input tohandleSingleObj
. There was an assumption thatexistingObj
would always be set ifexists
was set.Commit ffc115c made this panic because
GetUID
was being called on a nilexistingObj
. Prior to this, it seems it would just erroneously say it was compliant without checking it.Relates:
https://issues.redhat.com/browse/ACM-8731