Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CLI should ask before creating cloud data

See original GitHub issue

Is your feature request related to a problem? Please describe. When you do amplify init it is unclear that Amplify will create anything in the cloud`

Describe the solution you’d like Before creating anything during init phase, CLI should explicitly ask permission to create anything in the cloud

Issue Analytics

State:
Created 5 years ago
Reactions:4
Comments:5 (1 by maintainers)

Top GitHub Comments

9reactions

jkeys-ecg-nmsucommented, Dec 12, 2018

Agreed that amplify init probably shouldn’t provision AWS resources until the first amplify push.

0reactions

HknLofcommented, May 15, 2020

This feature also makes sense in AWS Accounts which are governed under AWS orgs. Scenario:

3 Accounts: dev, staging, prod

Only for dev one has “human” assumable role and the others are staged through CICD. Let’s say we create an env dev in dev and just want to stage the same setup all the way towards prod.

Then amplify init actually fails as it does not have local state for the environment staging and prod.