Fix KeyError in log format for requests without AWS context #9132
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
With #9084, logs contain the account ID and region from the request context when trace logging is enabled.
However, not all HTTP requests have an AWS context, a la ones made to the health endpoint
/_localstack/health
or stack info/_localstack/stackinfo
.This was caused following:
Implementation
This PR adjusts the log formatters so that the account ID and region is only included for requests with AWS context. Now,
Requests with an AWS context produce:
All other requests produce: