-
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
Renaming repository #80
Comments
AGREED!!! |
Based on what I am seeing at hashicorp, it should be
So, "secrets" instead of "secret" ... but yes, I think it would make good sense to do this BEFORE going 1.0.0 ;) |
The reason I chose singular form is because when you do
So the type is |
I am sure it's good either way, one other thing to remember would be to update the integrations page: https://developer.hashicorp.com/vault/integrations?filter=artifactory |
Rename repo name to vault-plugin-secrets-artifactory
Rename this repository from
artifactory-secrets-plugin
tovault-plugin-secrets-artifactory
, following the same pattern as other Vault plugin repos (as well as Terraform provider).Other references to the original name (binary name, path, etc.) would not be affected by this repo name change.
The text was updated successfully, but these errors were encountered: