Skip to content

Somehow allow for "Bootstrapping" of writeback values #1009

@cbn-targit

Description

@cbn-targit

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions