feat: add initial support for HTTP endpoint destination #34564
Closed
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.
Issue # (if applicable)
Addresses #20354
Reason for this change
Rather than waiting on full L2 support maybe we can simply add L1 support in the DestinationConfig interface. This would allow people to extend the interface and address the issue in the meantime.
Without adding this to the interface JSII will not let us extend the interface and compile it since we'd be the return signature. See aws/jsii#3495
Description of changes
This should be a small enough change where we can merge in without much worry.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license