Better handling of cluster-scoped template lookups #115
Conversation
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
Previously, there were some inconsistencies in how a hub template lookup for a cluster-scoped resource worked. As a result, the propagator would throw an error, and not be able to populate a real status for policies that tried to use that kind of lookup. Now, in general, using lookup in a hub template for a cluster-scoped resource will fail with a template error that can be seen in the propagated policy. The one current exception is that a lookup of the ManagedCluster where the policy is replicated is allowed. Refs: - https://issues.redhat.com/browse/ACM-5547 Signed-off-by: Justin Kulikauskas <[email protected]>
mprahl
approved these changes
Jun 14, 2023
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JustinKuli, mprahl The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Previously, there were some inconsistencies in how a hub template lookup for a cluster-scoped resource worked. As a result, the propagator would throw an error, and not be able to populate a real status for policies that tried to use that kind of lookup.
Now, in general, using lookup in a hub template for a cluster-scoped resource will fail with a template error that can be seen in the propagated policy. The one current exception is that a lookup of the ManagedCluster where the policy is replicated is allowed.
Refs: