You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all: Thanks for your awesome work with this repo. I've used it for the second time already and I'm really glad you provided such a nice boilerplate 😊 👍
I ran into an issue with this, though, and I figured I might raise this as a small issue since this has a simple fix from what I understood.
When setting up the cloudfront.OriginRequestPolicy, you're setting a static name for it here. This works well for a single Remix application deployed via this template. As soon as another one gets added in the same account, though, that stack cannot be deployed. Simple reason: There already is the named OriginRequestPolicy.
The simple fix for this would be to "just" remove that line from the stack. Naming is then automagically taken care of and won't break when adding more environments.
The text was updated successfully, but these errors were encountered:
Hey 👋
First of all: Thanks for your awesome work with this repo. I've used it for the second time already and I'm really glad you provided such a nice boilerplate 😊 👍
I ran into an issue with this, though, and I figured I might raise this as a small issue since this has a simple fix from what I understood.
When setting up the
cloudfront.OriginRequestPolicy
, you're setting a static name for it here. This works well for a single Remix application deployed via this template. As soon as another one gets added in the same account, though, that stack cannot be deployed. Simple reason: There already is the namedOriginRequestPolicy
.The simple fix for this would be to "just" remove that line from the stack. Naming is then automagically taken care of and won't break when adding more environments.
The text was updated successfully, but these errors were encountered: