-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
CloudWatch V2: Move tagging functionality into separate methods to enable their overriding in pro version #13748
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
base: main
Are you sure you want to change the base?
Conversation
Test Results - Alternative Providers180 tests - 1 093 39 ✅ - 687 2m 31s ⏱️ - 28m 35s Results for commit 365b9cc. ± Comparison against base commit 2046dff. This pull request removes 1093 tests. |
Test Results (amd64) - Integration, Bootstrap 5 files ± 0 5 suites ±0 1h 4m 27s ⏱️ - 1h 31m 33s Results for commit 365b9cc. ± Comparison against base commit 2046dff. This pull request removes 4346 tests. |
LocalStack Community integration with Pro 2 files 2 suites 48m 1s ⏱️ Results for commit 365b9cc. |
Motivation
This PR moves tagging logic to separate methods on the CloudWatch V2 Provider class to enable their overriding in pro version.
These methods will be overridden in the Pro version, where CloudWatch V2 will be integrated with the new ResourceGroupsTagging plugin. This integration will enable CloudWatch resources to be tagged and allow tags to be retrieved through the Resource Groups Tagging service.
Changes
Tests
Related
FLC-280