bc-org/Set Helm Tags
Setting application version tags (e.g. for docker image versions) in (e.g. Helm) configuration files for different deployment phases (e.g. dev/stage/prod).
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Dec 22, 2021
- License
- None
Pinned Snippet
uses: bc-org/gha-update-application-version-tags@de8f2d633c56c8ea114205e2fa56d66a6ff6cd31 # v0.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| app | Application to change all version tags for e.g. application docker images in a configuration file (e.g. Helm values files) | yes | — |
| phase | Deployment phase (dev/stage/prod/ignore). In mode single the user is free to use whatever name suits except for ignore. | yes | dev |
| prefix | File prefix of configuration file (default: values-) | yes | values- |
| tag | Version tag to use | yes | — |
| hash | Version digest hash. The digest will be edited in the configuration file(s) if present. | no | null |
| working-directory | working directory | no | ./ |
| mode | Whether to cascade or not. When cascading, prod will be deployed to all three stages, stage to stage and dev, and dev to dev only. | yes | cascade |
| delimiter | Delimiter as regex between application and version tag. Default :\s (e.g. [app]: [tag]). If you use yaml defaults the delimiter will be \s only. | yes | : |
Outputs
no outputs