Create Camel-Compliant SQS Subscriptions #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Right now when an SQS subscription is created via the
/subscribeendpoint with anhttp/httpsURL we simply save the URL to the subscription endpoint. Publishing to the subscription fails as we need to have a Camel-compliant endpoint definition (aws2-sqs://....). This change corrects the subscribe behavior to convert the SQS endpoint URL to the Camel-compliant version.Changes
/subscribeendpoint to convert the subscription endpoint to the Camel-compliant format for SQS subscriptions.Testing and Validation Steps