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

Somehow allow for "Bootstrapping" of writeback values #1009

Open
cbn-targit opened this issue Jan 13, 2025 · 0 comments
Open

Somehow allow for "Bootstrapping" of writeback values #1009

cbn-targit opened this issue Jan 13, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@cbn-targit
Copy link

Is your feature request related to a problem? Please describe.

For our specific workflow, we use a folder structure like /values/generated/{environment}.yaml
This is the yaml we write back to when ArgoCD-Image-Updater updates a deployment.

This leads to an issue when creating new applications, that the image updater has not yet touched.

The values that the image updater writes, will not yet have been written, and the application cannot successfully come up, which causes it to be ignored by the image updater, making sure the values never get updated

Describe the solution you'd like
An annotation to allow argocd-image-updater to not ignore an application in failed/processing state, allowing for the image updater to write image and tag to a git repo of a 'processing' application

Describe alternatives you've considered
We could obviously just prefill the values with some placeholders such as nginx or busybox, however, this seems cluncky and unintuitive

@cbn-targit cbn-targit added the enhancement New feature or request label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant