-
Notifications
You must be signed in to change notification settings - Fork 195
Added support for azure keyvault provider #319
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
base: master
Are you sure you want to change the base?
Conversation
|
Devbox support was also added since used for local development, but not manadatory to be merged. If needed I can remove it Also nightly branch was conflicting with my computer (arm64 macOS) so moved to stable branch. |
|
not sure if there is something blocking this PR but it would be great to have Azure Key Vault support. Any chance to get this merged ? |
|
@jondot / @kaplanelad ? |
|
|
||
| #[cfg(feature = "azure_keyvault")] | ||
| ProviderKind::AzureKeyVault => Box::new( | ||
| crate::providers::etcd::Etcd::new( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the new provider to be used should not be Etcd here. right ?
|
@ManuInNZ as far as I know, the CNCF colleagues marked the project as archived since no support has been given from the developers. I would like to keep it up with the fork if I have the time at some point. Help is welcome! |
|
To be fair I am not a pro Rustacean and even qualified beginner but I can read code and make sense. |
No description provided.