-
Notifications
You must be signed in to change notification settings - Fork 60
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
Provide a way to update variables #249
Comments
In Heroku the Calling When calling
I like being more explicit about which the key and variable is, this is just a shorter hand version than using One final thing, you have the commands setup as |
Yeah I think making
As opposed to:
AS for why set the commands up that way, in OClif it would absolutely be the right way but in That being said I'm happy to explore as part of this issue how we can map |
This change introduces a new set of commands around retrieving and modifying environment variables from already deployed environments. re #249
This is merged as of #290. |
Right now there is no easy way to update environment variables using the Serverless Toolkit. You can do so using
twilio api:serverless:...
but it requires the knowledge of the Variable SID and other information.We should provide a way to set those variables more conveniently.
Suggestion
Provide a dedicated command
variables
to set, get and update environment variables without having to know whether they exist or not.Examples
Update an environment variable for
dev
environment from within a project using the Twilio CLIUpdate environment variables based on a
.env
file in productionGet variables from a
stage
environmentRemove a variable from a specific environment using the environment SID
List all environment variables
Inspiration
The terms are inspired by the Netlify CLI. The only change is that we rely on
--key
and--value
instead of positional arguments to make it more descriptive. Open for alternatives though.The text was updated successfully, but these errors were encountered: