chore: update fa³st chart#158
Merged
arnoweiss merged 2 commits intoJun 1, 2026
Merged
Conversation
arnoweiss
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
WHAT
ArgoCD Vault Plugin allows to define paths to vault secrets in deployment configurations. These paths are resolved after helm template is executed. The current FA³ST chart's deployment.yaml does not allow this to work, modifying the path reference before it can be resolved by the plugin. It has since been updated (in the snapshot repository, version 1.0.1)
WHY
Deployment fails due to wrong order of vault secret injection + string manipulation.
FURTHER NOTES
See FraunhoferIOSB/FAAAST-Service#1452 for FA³ST chart changes