feat: Use sensitive values from 1Password vault in helm deployment workflow #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR extends existing helm chart deployment reusable workflow by adding a possibility to use sensitive values stored in 1Password vault.
Workflow is extended by:
VALUE_FILES
environmental variable - coma-separated list of value files used by the helm chart deployment actionAdditionally, it sorts input values in a alphabetical order.
Related Issue(s)
https://github.com/FlowFuse/CloudProject/issues/366
Checklist
flowforge.yml
?FlowFuse/helm
to update ConfigMap TemplateFlowFuse/CloudProject
to update values for Staging/ProductionLabels
backport
labelarea:migration
label