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.
This PR will add
--recursive
flag to recursively diff encountered Kustomizations similar to discussions #2466, #2434, #820. (Currently it doesn't expand HelmReleases, probably could be added later).Sources of additional repositories can be provided as comma-separated list by
--local-sources Kind/namespace/name=path
(i.e.--local-sources GitRepository/flux-system/flux-gitops=$HOME/git/flux-gitops
)Couple of words on our use case and motivation. We have number of clusters of different kinds sharing common GitOps repository with Kustomizations and overrides. To avoid unexpected changes most clusters are locked to a specific SHA instead of main branch. So promoting to a new SHA requires comparing the changes in Git and figuring out how it will affect the specific cluster.
This feature will allow to run on all applicable to the cluster Kustomizations indicating only ones that have the actual change. Example of the output: