Introducing SAM support for EventBridgeRule, modeled after the existing CloudWatchEvent... #1241
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.
…, and guiding users to new service
Description of changes:
Add support for explicitly referencing "EventBridge" - the service that superseded "CloudWatch Events
The meaningful part of this CR is actually ONLY 3 lines of code in push.py:
The rest is examples, doc, and test file updates
There are 2 code samples in serverless-application-model that refer to cloudwatchevents. I kept the directories of the old ones for someone who’s only familiar with “cloudwatch events” to be able to discover them, but copied the code to new eventbridge - named code sample directories. In the original directory i added README referencing the move and linking to the new none
Schedule triggers use Events rules underneath, so no specification requirements have to be made. However a couple places in the code refer to them as “CloudWatchEvents Schedule” - since that’s not backwards incompatible i just renamed those to EventBridge Schedule"
Description of how you validated changes:
make test/make pr
Pure renaming
Checklist:
make pr
passesexamples/2016-10-31
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.