search

aws-amplify / amplify-studio

AWS Amplify Studio (Formerly Admin UI)
136 stars 31 forks source link

Data Models: Save Data Models Before Actually Deploying (decouple the functionalities) #156

Open DanielDanaee opened 3 years ago

DanielDanaee commented 3 years ago

This has got very frustrating as work on entering/updating our data models and it fails on deploy and all the changes have been lost.

The ideal approach

Save and Deploy should be TWO SEPARATE FUNCTIONALITIES

Saving will save the structure of the models and deployment makes them live. It is idiotic and redundant to have them both in one single function with no history of changes or saves.

Also, when the deployment fails there is no error/reason message to say why the deployment failed.

hsspain commented 3 years ago

@DanielDanaee Thank you for the feedback. We will add this feature request to our backlog. For error surfacing, you can see more verbose messaging in your CloudFormation console, but we are working to display better messages to give developers a better experience.

DanielDanaee commented 3 years ago

@hsspain Thank you! Looking very much forward to it!

nilyin commented 3 years ago

why it is closed? The problem is not solved yet. I just also lost 2 hours of my work and all data entities I've created.

DanielDanaee commented 3 years ago

@hsspain Please reopen this issue if it is not resolved yet.

pananapread commented 2 years ago

Thank you for posting this Github issue (and sorry for the delay in replying)! We have marked this as a feature request and are looking into prioritizing this with the team :)

For everyone else, if you agree with @DanielDanaee or have your own details to add to this issue post, please do post your support here by adding a comment or +1-ing with an emoji!!

Christopher-Hayes commented 2 years ago

I've had the same issue. I added additional models to my current setup and was confused to find when I came back after I ran "Save and Deploy", the models I just added are missing. It could use an error notification that the deployment failed, I wasn't sure what led to the new models disappearing. Separating "Save" and "Deploy" would be nice to avoid losing work.

neilhunt1 commented 1 year ago

Since data models take 5-10+ minutes to deploy, it is quite disruptive within our flow to need to deploy our data model and so we don’t do it often. Sadly, the only way to save our work is to also do a deploy, and so on multiple occasions we have lost our work for one reason or another because in effect saving takes so long. Really, the save and deploy functions should be separate actions/buttons so we could quickly save our state somehow but not deploy to our API.