-
Notifications
You must be signed in to change notification settings - Fork 43
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
Folders support for credentials #161
Comments
Hi, folder support is a feature that has not been implemented in the plugin so far. However, off the top of my head, it could potentially be implemented. Perhaps with a new tag on the Secrets Manager secret which says which folder to restrict it to. |
Thanks for the update chris - do you know how long would it take to include this feature ? |
@maqzee-git after several attempts at different approaches to multi-tenancy, multi-environment, and folders support, I've finally got an approach which should work with and support all of those... Basically I'm implementing folders support for the credentials provider (using the OSS Cloudbees Folders Plugin) downstream in a new plugin, https://github.com/chriskilding/aws-secrets-manager-credentials-provider-folders-plugin The idea is this will behave very similarly to the main plugin (supports all the same credential types, and configuration properties), with 2 differences:
In future, you'll be able to use this plugin and the extension plugin in 3 different ways:
I'm looking for initial feedback on a super early stage version of it, so if you (or anyone watching this issue) would like to alpha test it and provide feedback, please head over to chriskilding/aws-secrets-manager-credentials-provider-folders-plugin#1 and indicate your interest :) |
Looping in @edwardprzeniczny @NoamGoren @tuxy85 @alandevine |
I just stumbled upon this. Is there any development going on anymore on this? We would benefit of this feature on our multi-tenant Jenkins instance. @chriskilding |
We also really need this feature, are there any plans to roll this out? @chriskilding |
Description
The text was updated successfully, but these errors were encountered: