-
Notifications
You must be signed in to change notification settings - Fork 42
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
[FEATURE] Set secret visibility #453
Labels
enhancement
New feature or request
Comments
Also need to modify the models.ChangeRequest struct to accept the visibility, etc. fields. For example:
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
As a project member, I want to be able to set / specify a secret's visibility.
Describe the solution you'd like
A relatively low-lift fix would be to add an optional
--visibility
flag to thedoppler secrets set
command:It should accept one of
masked
,unmasked
, andrestricted
.This would also require the setSecrets() function to be modified:
--visibility
flag is not specified, then it can continue to use the current secrets map.--visibility
flag is specified, then it needs to compose an appropriatechange_requests
parameter for the secrets update api call(Alternatively, just use the
change_requests
parameter entirely, but compose it with just thename
andvalue
fields.)NOTE: When setting multiple secrets (e.g.
doppler secrets set A=1 B=2
then the--visibility
flag will apply to all secrets).Describe alternatives you've considered
When calling the
doppler
CLI from a shell script, compose the JSON payload directly and invoke the API usingcurl
(or, using whatever HTTP request library in your preferred language, e.g. Faraday for Ruby).Additional context
The text was updated successfully, but these errors were encountered: