-
Notifications
You must be signed in to change notification settings - Fork 149
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
Update Github integration instructions #306
base: master
Are you sure you want to change the base?
Conversation
@Amphaal please fix DCO check |
@CodiumAI-Agent /review |
PR Reviewer Guide 🔍
|
template.app-deployed: | | ||
message: | | ||
Application {{.app.metadata.name}} is now running new version of deployments manifests. | ||
github: | ||
repoURLPath: "{{.app.spec.source.repoURL}}" | ||
revisionPath: "{{.app.status.operationState.syncResult.revision}}" | ||
revisionPath: "{{.app.status.operationState.operation.sync.revision}}" |
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.
why would you take it from operation instead syncResult?
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.
Because it did not work otherwise with my setup, and I could not tell why ! In my Application
manifests, syncResult
was missing for some reasons. I double checked this time and I can now find it. What is the difference between both ? Why would this happen ?
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.
syncResult exist when sync already finished. It may not exist if application is just created and sync still didnt happen before
following up argoproj/argo-cd#18546 (comment) instructions