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

Change the default .argocd-source path #871

Open
darklight147 opened this issue Sep 25, 2024 · 1 comment
Open

Change the default .argocd-source path #871

darklight147 opened this issue Sep 25, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@darklight147
Copy link

Describe the bug
The bug am facing is that i have different branches for different environements, preprod, staging, prod, and image updater commit and push to a branch with the .argocd files, means i cannot merge from one branch to another without affecting the deployments of the apps in the other environements

To Reproduce
1- have a branch per environements
2- each app has its app for preprod, staging, prod
3- image updater commits to the same file for all environemnts

Expected behavior
have a way to seperate files by targetRevision, so that the file commited by image updater is something like .argocd-source-preprod-myapp.yaml so that when image updater for a different environement tries to perform an update, it doesnt override the file used by the other envirronements too

Additional context
Add any other context about the problem here.

@darklight147 darklight147 added the bug Something isn't working label Sep 25, 2024
@chengfang
Copy link
Collaborator

Does specifying argocd-image-updater.argoproj.io/write-back-target: xyz help? Each branch and env can have its own write-back-target. The default write-back-target file name already includes application name and namespace name, and we may not want to overload it with too much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants