-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
chore: define rest of explicit state containers for providers #13433
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
Test Results (amd64) - Acceptance7 tests 5 ✅ 3m 23s ⏱️ Results for commit 11c7a5e. ♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 13m 7s ⏱️ Results for commit 11c7a5e. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files 2 suites 1h 40m 33s ⏱️ Results for commit 11c7a5e. ♻️ This comment has been updated with latest results. |
64d9a33 to
bc73f29
Compare
6d04112 to
65231d0
Compare
65231d0 to
6e3e7f3
Compare
6e3e7f3 to
11c7a5e
Compare
giograno
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🧹
Motivation
Follow-up from #13423, this PR migrates the rest of the service providers to properly indicates which state container(s) they use.
It migrates the rest of the Community services.
Changes
Migrate the following services to be explicit about their state containers:
route53route53resolvers3controlschedulersecretsmanagersessns v1sns v2sqsssmstssupportswftranscribeTests
Full Pro run ✅: https://github.com/localstack/localstack-pro/actions/runs/19830037292