Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

Amphaal
Copy link

@Amphaal Amphaal commented Jun 17, 2024

following up argoproj/argo-cd#18546 (comment) instructions

@pasha-codefresh
Copy link
Member

@Amphaal please fix DCO check

@pasha-codefresh
Copy link
Member

@CodiumAI-Agent /review

@CodiumAI-Agent
Copy link

CodiumAI-Agent commented Jun 17, 2024

PR Reviewer Guide 🔍

(Review updated until commit 9d9e735)

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Possible Bug
The context key added at line 31 introduces a new variable argocdUrl. Ensure that <argocd_host_url> is properly documented and validated to avoid misconfiguration.

Code Smell
The templates for sync statuses (e.g., app-sync-succeeded, app-sync-failed, etc.) added between lines 66-120 are repetitive. Consider refactoring to reduce redundancy and improve maintainability.

Possible Bug
The repoURLPath and revisionPath in the app-deployed template (line 126-127) seem inconsistent with the other templates. Verify if this is intentional or an oversight.

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}}"
Copy link
Member

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?

Copy link
Author

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 ?

Copy link
Member

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

@Amphaal Amphaal closed this by deleting the head repository Dec 13, 2024
@CodiumAI-Agent
Copy link

Persistent review updated to latest commit 9d9e735

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants