Custom DomainHard fail on IAM permission error #649
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a π bug fix.
This is a π§ documentation change.
bundle exec rspec
to verify this)Summary
Fixes #557
Know, it's 99% of the time bad to
rescue Exception
π It's a bummer it cause issues for the users who were kind enough to provide detailed issue reports. Vaguely remember that was mentally spent from working on Custom Domain and Custom CloudFormation resources and used the rescue Exception. π€¦π»ββοΈ It's been removed and using more targeted rescues now.Related: Also, wanted to note: #640 Made some important hardening improvements to Custom Domain Custom CloudFormation Resource Lambda Function that handles the custom domain. This takes rollback times down from 3 hours to 3 minutes. This should save everyone time from these related issues.
Context
How to Test
Tested by adding a Deny policy, something like this:
Note: Did not
Deny
thecloudformation:DescribeStackResources
also because that is already failing hard in newer code where Jets checks for changed routes.The
jets deploy
command should fail hard with an IAM permission error.Version Changes
Patch