r/aws_cloudwatch_event_connection: Add connectivity_parameters
argument
#41561
+230
−5
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.
Description
Adding
connectivity_parameters
toaws_cloudwatch_event_connection
for supporting OAuth on private APIs.Note: The creation of a connection with OAuth on a private API takes a little longer. I tested with different configurations, and got the following results. Creating a connection with OAuth on a private API might take up to 20 minutes before accessing a target state of
AUTHORIZED
,DEAUTHORIZED
orACTIVE
. By acceptingAUTHORIZING
as a target state for a valid creation I could lower the timeout to 10 min (seeOutput from Acceptance Testing
). I would go with this setup, otherwise we have to stay with a timeout of 20 min as it seems (seeOutput from Acceptance Testing - Option 2
below).More Information on connection states here https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-target-connection-states.html. As far as I understand this documentation
AUTHORIZING
is only used for private API OAuth, so there shouldnt be any conflicts.Comment if you wish for the second implementation, then I will update this branch.
Relations
Closes #41220
References
Output from Acceptance Testing - current implementation (10 min timeout & target states: AUTHORIZED, DEAUTHORIZED, ACTIVE, AUTHORIZING)
Output from Acceptance Testing - Option 2 (20 min timeout & target states: AUTHORIZED, DEAUTHORIZED, ACTIVE)