APIGW: fix regional domain name to take into account region#13603
Merged
APIGW: fix regional domain name to take into account region#13603
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 18m 18s ⏱️ - 1h 38m 26s Results for commit 81db507. ± Comparison against base commit 98e5406. This pull request removes 3854 tests.♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 35m 56s ⏱️ Results for commit 81db507. ♻️ This comment has been updated with latest results. |
cloutierMat
approved these changes
Jan 12, 2026
Member
cloutierMat
left a comment
There was a problem hiding this comment.
Thanks for jumping on that fix 🚀
c6cb07b to
81db507
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
When working with Regional Domain Names from APIGW, we had a little flaw: we only used the hash of the custom domain name, but not the region is lived it. This meant that for two Custom Domain Names living in 2 different regions, their regional domain names would be the same, which defeat the purpose.
This PR adapts the utility to take into account the region now.
Changes
Tests
Related