[Backport to 6.1] Native message attributes are not loaded when using LocalStack #2298
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.
Symptoms
When using LocalStack, the transport doesn't load native message attributes in native integration scenarios.
Who's affected
You're affected if you're using LocalStack and doing native integration.
Root cause
The transport uses the undocumented (but supported)
*
syntax to load all attributes instead of the supported.*
orAll
This PR fixes a bug that prevents native integration from working when using localstack, a local AWS cloud stack implementation.
More information in #2288