fix: return revision from getGitGeneratorInfo #8979
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.
Originally posted here argoproj/applicationset#520 but moved to argo-cd since the applicationset codes is now integrated here.
Signed-off-by: Reinier Timmer reinier.timmer@ah.nl
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist:
Description
It seems that the applicationset webhook endpoint is not working completely as expected when tracking a repository branch (other than the default branch).
It turns out that the revision that is being used to compare against the targetRevision is always empty. So the test on https://github.com/argoproj/argo-cd/blob/master/applicationset/utils/webhook.go#L247 would always return false.
The revision field is already being evaluated on https://github.com/argoproj/argo-cd/blob/master/applicationset/utils/webhook.go#L147, but for some reason it was never included in the response.
After this change, we verified this on our own installation (when the code was still in the separate applicationset project) and there the webhook processing does recognize the correct branches on push events from GitHub. It is not live-tested yet after the applicationset code was moved to argo-cd