amplify push dry run?

[hisham]

** Which Category is your question related to? **
deployment for all categories

Is there a way to do a dry run of 'amplify push' to see what changes it would make without actually doing anything? I understand CloudFormation supports something like this through change sets. Does amplify expose this somehow?

[UnleashedMind]

amplify status will list what categories will be added / updated / deleted, but currently the cli does not provide push dry run.

[kaustavghosh06]

@hisham What other information do you think would be valuable to you before pushing local configurations to the cloud?
The amplify status command does provide an overview of whats getting created/updated/deleted with your next push but would like to know better about the specific needs.

[hisham]

1. For Auth, the most important thing is right now there is risk of cloudformation deleting and recreating userpool if you want to change certain attributes, so for safety purposes, I want to know if cloudformation is going to attempt to do that as we definitely don't want to delete our userpool accidentally. Currently all amplify status would show in this case is 'Update'.

2. For GraphQL API, what dynamodb tables will be created/deleted and what indices will be created. Again, we wouldn't want to accidentally delete a dynamodb table even if we remove a @model from the graphql schema. Again I believe amplify status only shows 'Update' in this case.

So maybe something more granular than general "Update", especially if any deletes are going to happen. I also read a bit that on dynamo tables we can put a 'retain' setting so that cloudformation does not delete these even if it wants to, but I have not looked into that closely yet.

I have not played with aws cdk yet but it seems from their demo that they do offer a 'cdk diff' functionality which gives you a granular view of what's going to happen:

Something like this would be nice for learning purposes, but the most important thing I think is what resources are going to be deleted by amplify (especially dyanamo tables and userpools).

[Bec-k]

Same here, would like to know if some resource will be deleted and re-created...

[renebrandel]

Hi @hisham @denissabramovs - we've now launched the ability to use amplify status -v to give you a "cdk diff"-like experience. It'll indicate every single resource change. LMK if this is addresses your concern. If not, @mention me, and let's discuss further!

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.