logs: fix put_metric_data
client for multi-account/region
#11691
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
As an initiative to make the -ext multi-account/multi-region compatible this PR fixes functionality for logs service.
So whenever we use values other than
000000000000
for account ID orus-east-1
for region, it should still create the consequent resources in these accounts and region.Failing workflow: https://github.com/localstack/localstack-ext/actions/runs/11268466307/job/31335436967
Changes
Add the region and account id from context to the
connect_to
client input_log_events
used to put the metrics data.This fixes:
tests.aws.services.logs.test_logs.TestCloudWatchLogsPro.test_json_metric_filters
in -ext for non-default credentials.Testing
Set the environment variables
TEST_AWS_ACCOUNT_ID=111111111111
,TEST_AWS_ACCESS_KEY_ID=111111111111
,TEST_AWS_REGION=us-west-1