-
Notifications
You must be signed in to change notification settings - Fork 0
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 relevant components discovery and add support for ArgoCD "native" application discovery #8
Conversation
to ArgoCD diff functionality
unsure of the component that where changed
/publish |
oci-image-publish-on-comment: succeeded ✅ |
component the telefonistka dedicated sha1 label and the ArgoCD native `manifest-generate-paths` annotation
* mocks: use go run to reduce dependency Using go run will automatically install the tool and run it if it is not installed already. * argocd: fix import path The import path for the mocks package is incorrect causing errors. The mocks package should be imported from internal/pkg/mocks instead of mocks/argocd. This also removes the aliased import and uses the package as named, which aligns with the directory name. --------- Co-authored-by: Hannes Gustafsson <[email protected]>
Log time of API call with questionable performance :)
upsate go.mod
/publish |
oci-image-publish-on-comment: succeeded ✅ |
This PR is missing a Jira ticket reference in the title or description. |
Co-authored-by: Yazdan Mohammadi <[email protected]>
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.
LGTM!
There a couple of nitpicks i or we 'll cover with a following PR.
🥷 Code experts: no user but you matched threshold 10 Oded-B has most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame: To learn more about /:\ gitStream - Visit our Docs |
Description
Context:
ArgoCD diffs all “relevant”(possibly affected by PR) ArgoCD apps to every PR to dispaly the diff and checks for “no-diff” PRs
“no-diff” PRs are automatically merged! failure to understand what ArgoCD apps to diff can lead to auto merging (auto-promoting) a change that does change the cluster state
The current way to understand which app to diff is based telefonistka sourcePath configuration, but deployment target that are “last” in the promotion flow (like the prod clusters in a "dev">"staging" > "prod" flow) are referenced not in sourcePath (they are only in
targetPath
).PR desc:
This PR will add "affected component paths" to telefonistka PR metadata(the metadata Telefonistka hide in promotion PR "body" field)
And it will change the argoCD app discovery mechanism to get the affected paths from the metadata on promotion PRs (non-promotion PR will keep the
sourcePath
based code path)Additionally we are adding another discovery mechanism - one that doesn't require ussage of a dedicated telefonistika(
sha1
) label no all application objects but one that is less performant on repos will large number of hosted ArgoCD appsType of Change
Checklist