-
Notifications
You must be signed in to change notification settings - Fork 63
activate
does not send and enable new --env configuration
#109
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
Milestone
Comments
Thank you so much for opening your first issue in this project! We'll try to get back to it as quickly as possible. While you are waiting...here's a random picture of a corgi (powered by dog.ceo) |
philnash
added a commit
to philnash/serverless-api
that referenced
this issue
Jun 15, 2020
Previously activating a build would not set any env vars, this fixes that. twilio-labs/serverless-toolkit#109
philnash
added a commit
to philnash/serverless-api
that referenced
this issue
Jun 15, 2020
Previously activating a build would not set any env vars, this fixes that. twilio-labs/serverless-toolkit#109
philnash
added a commit
to philnash/twilio-run
that referenced
this issue
Jun 15, 2020
This was referenced Jun 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When activating between two environments,
--env
files specified during the command aren't enabled in the new environment.Example:
dev
:twilio serverless:deploy --env=.env.dev --environment=dev
dev
now running with.env.dev
variablesdev
tostage
:twilio serverless:activate --env=.env.stage --source-environment=dev --environment=stage
stage
now running with.env.dev
variables, not.env.stage
variablesThe text was updated successfully, but these errors were encountered: