-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Move secrets to an official plugin #5278
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide. |
Just want to note that we have this already: There's a |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide. |
This is something we can keep in mind for the future, but for the time being it's not something worth the necessary commitment of time and effort. |
Reopening this for @DanSheps. |
Removal is staged in https://github.com/netbox-community/netbox/tree/feature-remove-secrets Plugin is still being developed. |
@DanSheps and I decided to push this back (slightly) to the v2.12 release. This ensures a quicker release for v2.11, and provides more warning time for users of the secrets functionality. |
Closing out this issue as the secrets code has been removed from NetBox core. Work is still underway on the plugin. |
@jeremystretch is there an issue or repo one can use to track the work on the secrets plugin? |
@DanSheps has been working on it here: https://github.com/DanSheps/netbox-secretstore |
Hello ! |
you are free to develop one yourself. Unfortunately this issue is specifically for deprecating secrets. |
Environment
Proposed Functionality
Move the secrets app to a dedicated official plugin
Use Case
There have been a few requests to improve the secrets functionality or to allow integration into a third party secret vault (HashiCorp, etc). Additionally, we have a naming collision with the "secrets" python standard library (#4553). Moving the secrets app into a dedicated plugin would allow us to:
Database Changes
Table changes to accommodate moving the app to a official plugin
External Dependencies
None
The text was updated successfully, but these errors were encountered: