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

Properly handle not existing secrets #641

Open
hirenko-v opened this issue May 28, 2024 · 0 comments
Open

Properly handle not existing secrets #641

hirenko-v opened this issue May 28, 2024 · 0 comments

Comments

@hirenko-v
Copy link

It would be great to have some "fallcack" configuration for placeholders.

In our case application consists of multiple resources one of them creates secrets which application should use when it will appear.
If secret is not existing we'd like to sert some fallback value to placeholder and do not fail with the following error

failed exit status 1: Error: Replace: could not replace all placeholders in Template:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant