benpottier

> ah the empty values should be okay, if you use `copilot env package --upload-assets` those values will be filled. > > Would you mind running `copilot env deploy` again...

Yes, I'm seeing v1.12.2 ... I updated the sid in the console but I'm still hitting the same error. The issue seems to be that its trying to create a...

Okay, so maybe this is the issue then?  Thats a screenshot of the currently deployed stack.

> ah yeah! > > Like you suspect, I think while skipping the rollback the permission got retained and the version remained `v1.8.0`. > > What I am confused by...

It's okay. I appreciate your helping (and I especially appreciate this app you all have built). So, changing just the metadata won't work because cloudformation complains that there are no...

Metadata is fixed.  Should I attempt to deploy?

> Yup, go for it! We're back! Thank you so much. But, what happened? Maybe I did something wrong the first time? I'm done for the week now but I...

> Hey @benjaminpottier! Sorry to hear you're running into this issue - Could you share your manifest for the service? Also, what Copilot version are you upgrading from, and have...

> Oh I see, so basically what happened for this service was: > > 1. `[email protected] svc deploy` 2. `[email protected] svc deploy` 3. `[email protected] svc deploy` > Is that right?...

> Hi @benjaminpottier ! > > Am I understanding correctly that you're adding the permission to the other AWS account, so that you can pull the images from the other...