-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
CFNV2: fix community issues after attempted pro fixes #13101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This reverts commit 0221c45.
Test Results (MA/MR) - Preflight, Unit22 117 tests 20 379 ✅ 6m 36s ⏱️ Results for commit 9fe5707. ♻️ This comment has been updated with latest results. |
Test Results - Preflight, Unit22 117 tests 20 379 ✅ 6m 31s ⏱️ Results for commit 9fe5707. ♻️ This comment has been updated with latest results. |
Test Results (amd64) - Acceptance7 tests 5 ✅ 3m 11s ⏱️ Results for commit 9fe5707. |
Test Results (amd64, MA/MR) - Acceptance7 tests 5 ✅ 3m 4s ⏱️ Results for commit 9fe5707. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 21m 42s ⏱️ Results for commit 9fe5707. |
Test Results (amd64, MA/MR) - Integration, Bootstrap 5 files 5 suites 2h 23m 26s ⏱️ Results for commit 9fe5707. |
LocalStack Community integration with Pro 2 files 2 suites 1h 43m 30s ⏱️ Results for commit 9fe5707. |
Motivation
While performing the last minute fixes for the Pro resources in #13045 we found that the v2 community tests were not being run. This meant that some bugs slipped in to the new provider undetected. This was only picked up in #13098.
Changes
try_load_resource_provider
is called with aNothing
value