allow headers to be set from integration definition for HTTP integrat… #10035
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
Unlike the lambda integration, which allows headers to be set from the integration definition, the HTTP integration passes the invocation context headers directly to the backend without applying the headers from the integration. This change addresses #10034 and allows additional headers to be sent to the backend which matches our ability to do this in the AWS cloud.
Changes
Headers defined in an integration are now able to be sent along to the backend.
Testing