New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix cluster targeting and missing customizations #1473
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work, thanks for this :)
Leaving a few comments here, happy to discuss them to better understand your focus and any additional context.
17da2f9
to
f9457f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a few suggestions on wording of test descriptions, similar to what has already been applied on the first test case. Happy to discuss, also feel free to reword ;)
There are two types of Targets: - Targets defined in a GitRepo. These targets are used to create BundleDeployments, and are duplicated into TargetRestrictions - TargetCustomizations defined in fleet.yaml. There are used just for customization Check if there is any TargetCustomization that should be applied, and it is not in the TargetRestrictions. Add the iteration for clusters groups inside the loop of matches, that guarantees the order will never be different Signed-off-by: raul <raul.cabello@suse.com>
Co-authored-by: Corentin Néau <tan.neau@suse.com> Signed-off-by: raul <raul.cabello@suse.com>
…integration tests Signed-off-by: raul <raul.cabello@suse.com>
Co-authored-by: Corentin Néau <tan.neau@suse.com>
Conditions inside ignore conditions field will be ignored when checking the Bundle state Signed-off-by: raul <raul.cabello@suse.com>
There are two types of Targets:
Targets
defined in aGitRepo
. These targets are used to createBundleDeployments
, and are duplicated intoTargetRestrictions
TargetCustomizations
defined infleet.yaml
. There are used just for customizationThis PR fixes two issues:
Check if there is any
TargetCustomization
that should be applied, and it is not in theTargetRestrictions
. Before we were matching target just if they were insideTargetRestrictions
. This was causing some customizations to be ignoredWe were iteration a map here which order might be different in different executions. This was causing this issue. This PR adds the iteration for clusters groups inside the loop of matches, that guarantees the order will never be different.
refers to #1254