I am getting the already exists error when I moved...
# seedm
Michael Robellard
06/07/2022, 5:31 PMI am getting the already exists error when I moved an app from running locally using npx sst deploy to running the same deploy in seed. Seems like an issue if I/users can't move to seed without deleting their cloudfront distribution and dynamodb tables, or am I doing something wrong?
Copy code
INFO: Deploying 4 stacks...
48.52 s
❌ dev-the-coach-essentials-dynamodb-stack: /dev/mproveData already exists in stack arn:aws:cloudformation:us-east-2:811320874249:stack/dev-tce-dynamodb-stack/12c9fec0-e676-11ec-8106-0a607fc8eac0
✅ dev-the-coach-essentials-s3-stack: Deployed
➖ dev-the-coach-essentials-api: Skipped
❌ dev-the-coach-essentials-site-stack: /dev/siteurl already exists in stack arn:aws:cloudformation:us-east-2:811320874249:stack/dev-tce-site-stack/3d8c6950-e67f-11ec-be6e-065a8584e8c0Michael Robellard
06/07/2022, 5:42 PMI figured out what I did wrong. Renamed the thing sst.json which changed the names of everything in Cloudformation... big mistake, don't do that,
f
Frank
06/07/2022, 5:58 PM
Ah, yeah.. the app name in
sst.jsonFrank
06/07/2022, 5:58 PM
it can be overwritten, but not recommended.
m
Michael Robellard
06/07/2022, 6:00 PMJust glad I figured it out, and it was just dumb mistake on my part. The other thing I just noticed is that even though my sst.json says us-east-2, I need to set that in pipeline configuration as well or the post deploy actions will try and use the wrong region