handle aws arns without region#9946
Conversation
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9946 +/- ##
=======================================
Coverage 49.34% 49.35%
=======================================
Files 636 636
Lines 48778 48788 +10
=======================================
+ Hits 24069 24078 +9
Misses 22878 22878
- Partials 1831 1832 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
sylvainsf
left a comment
There was a problem hiding this comment.
Looks good, thanks for walking me through the problem.
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Signed-off-by: nithyatsu <nithyasu@microsoft.com>
Signed-off-by: nithyatsu <nithyasu@microsoft.com>
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Description
Many AWS resources are global and not tied to a region.
This includes AWS policies, roles, users, and many other IAM entities.
There are also other resources such as route 53 and cloudfront.
Since with UDTs we are open to managing any AWS resource through a recipe, we want to remove the region requirement for valid ARNs.
Type of change
Fixes: #issue_number
Contributor checklist
Please verify that the PR meets the following requirements, where applicable: