We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using spiffe-helper as a sidecar container, configuring it via environment variables provides greater flexibility and simplifies deployment.
spiffe-helper
The preliminary consensuated solution is to use the cleanenv library with support for JSON+YAML configuration formats.
cleanenv
To maintain backward compatibility:
--config
--legacy-config
Behavior:
Deprecation Plan:
For more context, see the Slack thread. For a comparison of options, see pros and cons.
The text was updated successfully, but these errors were encountered:
I’m currently working on this.
Sorry, something went wrong.
@kfox1111 @MarcosDY @faisal-memon
Thanks @eminwux. Will you be using clean env?
Hi @faisal-memon! Yes, I plan to use cleanenv. I’ll attach a draft PR once I’ve made significant progress.
Sounds good @eminwux
No branches or pull requests
When using
spiffe-helper
as a sidecar container, configuring it via environment variables provides greater flexibility and simplifies deployment.The preliminary consensuated solution is to use the
cleanenv
library with support for JSON+YAML configuration formats.To maintain backward compatibility:
--config
should be added for the new configuration format.--legacy-config
should be used for HCL legacy configuration.Behavior:
Deprecation Plan:
For more context, see the Slack thread.
For a comparison of options, see pros and cons.
The text was updated successfully, but these errors were encountered: