-
Notifications
You must be signed in to change notification settings - Fork 19
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
Prefix for imported secrets #49
Comments
@almostjulian please check the
|
If the base path contains other folders (one more level of nesting before getting to secrets), this works as you describe, the configuration places all the folders as hierarchical configuration items. In my example above, if I set the base path to I can include screenshots to illustrate if the above isn't clear. |
So, do you want to import from Vault with a prefix, or read keys with a certain prefix, I think that's what I don't get at the moment :) |
The former, I want to import keys, and place them within a prefix of my choosing (without having to change anything on the vault side to do so). |
Ok, I see. That is something possible. I don't have much time but can do some stuff over the weekend. Feel free to submit your PR if you can. |
Sure thing, I'll try to submit something later this week before the weekend. |
Apologies for the delay, I've created #53 for this |
I'm pulling secrets from Vault from multiple secret paths. Unfortunately, some of those secrets uniquely named. Could we get a new option to insert a prefix/parentPath into the secrets imported at the path?
e.g. something like:
with code like:
would mean the
ConnectionString
value would be accessible underConfiguration[SignalR:ConnectionString]
The text was updated successfully, but these errors were encountered: