Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix a bug related to unnamed objects
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 marked `exists` as true without setting `existingObj` in the input to `handleSingleObj`. There was an assumption that `existingObj` would always be set if `exists` was set. Commit ffc115c made this panic because `GetUID` was being called on a nil `existingObj`. Prior to this, it seems it would just erroneously say it was compliant without checking it. Relates: https://issues.redhat.com/browse/ACM-8731 Signed-off-by: mprahl <mprahl@users.noreply.github.com> (cherry picked from commit a901475)
- Loading branch information