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
Vault Integration #3138
Labels
kind/feature
Issues that represent larger new pieces of functionality, not enhancements to existing functionality
Milestone
Comments
will-chan
added
kind/enhancement
Issues that improve or augment existing functionality
release/v1.0.0
and removed
release/v1.0.0
labels
Dec 28, 2015
👍 |
+1 |
👍 |
of course as Passwords in $ENVs is strictly avoided by the production security team and blocks some deployments |
deniseschannon
added
kind/feature
Issues that represent larger new pieces of functionality, not enhancements to existing functionality
and removed
kind/enhancement
Issues that improve or augment existing functionality
release/future
labels
Jun 28, 2016
This is being addressed in the secrets API |
@cloudnautique is there a ticket to follow progress on this API, or is it already implemented? |
Closing and testing with #1269 instead |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/feature
Issues that represent larger new pieces of functionality, not enhancements to existing functionality
#1269
I want to suggest explicitly to genuinly support Hashicorp's vaultproject for Secrets Management as a first class rancher artifact. This is for conses gathering, please share your opinion or close if it is not inline with product strategy...
https://www.vaultproject.io/
The text was updated successfully, but these errors were encountered: