Amplify-cli: How would you handle dev/prod enviroments with the CLI?

[jarrettj]

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
There's no dev and prod.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
How would you go about creating a development and production environment?

Steps to reproduce the issue:

1. amplify publish
2. updates aws environment
3. only one environment available

What is the expected behavior?
Some way to push to a test environment first.

Additional environment details

• OS version (ie Windows 10 build X, macOS Sierra 10.12.6, etc.)
  MacOS
• Output of amplify --version:
  0.1.14
• Did this work in previous versions?: Y/N
  N

[chrisco255]

+1 - Right now it seems as though you would need to duplicate your API in order to get prod/dev/staging environments.

[kaustavghosh06]

Yes, you're right @chrisco255 . We're working currently to make the staging experience better and will soon have a solution for it.

[jarrettj]

Awesome stuff. Will keep an eye out. Regards.

Sent from my iPhone

On 05 Sep 2018, at 19:42, Kaustav Ghosh [e-mail] wrote:

Yes, you're right @chrisco255 . We're working currently to make the staging experience better and will soon have a solution for it.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[swaminator]

@jarrettj @chrisco255 I'm a PM on the team and would love to chat with you to understand your expectations for managing multiple environments. If you could share your email I'll get in touch.

[jarrettj]

Hi

Good day.

Awesome man. It’s jarrett.l.[email protected]. I can see if I can think of some ideas. Thanks.

Regards.
JJ

Sent from my iPhone

On 07 Sep 2018, at 17:13, Nikhil Swaminathan [e-mail] wrote:

@jarrettj @chrisco255 I'm a PM on the team and would love to chat with you to understand your expectations for managing multiple environments. If you could share your email I'll get in touch.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[chrisco255]

Hi @swaminator [email protected] works for me. Thanks!

[andrewtpoe]

I'm looking to learn the amplify CLI as it appears to be a superb resource. I would love to see support for testing/staging/production environments.

[kaustavghosh06]

@jarrettj @chrisco255 @andrewtpoe
We're currently brainstorming and working towards providing a CI/CD workflow as a part of the Amplify CLI, and in doing so we want to work backwards from the customer needs and we've opened up an issue (#286) as a part of the CLI repo to track this story.
Would be great, if you guys could take a look at it and respond back with some answers to the questions mentioned in the issue (#286) which would give us a better idea about your needs. Thanks!

[kaustavghosh06]

Based on all of your feedback, we’ve released a beta version of the CLI (npm install -g @aws-amplify/cli@multienv) to support multiple environments, team workflows and integrate with your CI/CD flows.
Please check out this documentation for more details - https://aws-amplify.github.io/docs/cli/multienv?sdk=js
Also, as a part of our feedback mechanism, we’ve opened up another GitHub issue, to track feedback from everyone, iterate on this beta version and then merge it to master. We'll close this issue and track feedback in #508. Looking forward to your feedback on this release.

[kaustavghosh06]

Closing this issue since this problem is solved with the release of the multienv feature-set mentioned above. Please feel free to re-open the issue if you've further questions about this.

[jarrettj]

Awesome! Started looking at amplify again and setting it up for multiple devs is all good. Thanks.