Skip to content

Fix help message for deploying existing services with the plugin #16

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.

Sign up for GitHub

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

Jump to bottom
Closed
dkundel opened this issue Jun 28, 2019 · 0 comments
Closed

Fix help message for deploying existing services with the plugin #16

dkundel opened this issue Jun 28, 2019 · 0 comments
Labels
bug Something isn't working v-next

Comments

@dkundel
Copy link
Contributor

dkundel commented Jun 28, 2019

Right now the output has parts that are undefined when using deploy via the github.com/twilio-labs/plugin-serverless. Example

✖ Project with name "twilio-example" already exists with SID "ZSxxxxxxxxxxxxxxxxxxxxxxx".
Here are a few ways to solve this problem:
- Rename your project in the package.json "name" property
- Pass an explicit name to your deployment
  > undefined deploy -n my-new-service-name
- Deploy to the existing service with the name "undefined"
  > undefined deploy --override-existing-project
- Run deployment in force mode
  > undefined deploy --force
@dkundel dkundel added bug Something isn't working v-next labels Jun 28, 2019
@dkundel dkundel changed the title 🐛 Fix help message for deploying existing services with the plugin Fix help message for deploying existing services with the plugin Jun 28, 2019
@dkundel dkundel mentioned this issue Jul 9, 2019
Closed
6 tasks
dkundel added a commit that referenced this issue Aug 10, 2020
@dkundel
fix(environments): fix deploying to production (#16)
3ca0ec5 
* fix(environments): fix deploying to production

When no domain suffix is set we should deploy to production. Similarly we should handle the lookup
of the right environment which was broken til now

* fix(client): adjust message for bare enviroments
dkundel added a commit that referenced this issue Aug 10, 2020
@dkundel
fix(environments): fix deploying to production (#16)
fc09142 
* fix(environments): fix deploying to production

When no domain suffix is set we should deploy to production. Similarly we should handle the lookup
of the right environment which was broken til now

* fix(client): adjust message for bare enviroments
dkundel added a commit that referenced this issue Aug 12, 2020
@dkundel
fix: pass yargs compatible flags
b9c8c65 
Yargs has two flags `$` for the command that was executed and `_` for all
remaining arguments. This simulates the two, to be compatible with
twilio-run messages.

fix #16
dkundel added a commit that referenced this issue Aug 12, 2020
@dkundel
fix: pass yargs compatible flags
6dfcdf0 
Yargs has two flags `$` for the command that was executed and `_` for all
remaining arguments. This simulates the two, to be compatible with
twilio-run messages.

fix #16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working v-next
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dkundel