(iotevents-actions): Add missing actions
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
At the moment, we are exposing:
[ClearTimerAction](https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-iotevents-actions-alpha.ClearTimerAction.html)
[LambdaInvokeAction](https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-iotevents-actions-alpha.LambdaInvokeAction.html)
[ResetTimerAction](https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-iotevents-actions-alpha.ResetTimerAction.html)
[SetTimerAction](https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-iotevents-actions-alpha.SetTimerAction.html)
[SetVariableAction](https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-iotevents-actions-alpha.SetVariableAction.html)
[TimerDuration](https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-iotevents-actions-alpha.TimerDuration.html)
What are missing from `DetectorModel` and `AlarmModel` are following:
* `DynamoDB`
* `DynamoDbv2`
* `Firehose`
* `IotEvents`
* `IotSiteWise`
* `IotTopicPublic`
* `Sns`
* `Sqs`
### Use Case
To allow users to use these actions vi L2 constructs.
### Proposed Solution
Should be similar to how the current actions are implemented.
### Other Information
_No response_
### Acknowledgements
- [X] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.46.0
### Environment details (OS name and version, etc.)
Linux
Contributor guide
Research direction
Start by comparing the existing ClearTimerAction, LambdaInvokeAction, ResetTimerAction, SetTimerAction, and SetVariableAction implementations for DetectorModel and AlarmModel. Add the missing DynamoDB, DynamoDbv2, Firehose, IotEvents, IotSiteWise, IotTopicPublic, Sns, and Sqs actions in the same style, with all listed actions available through the L2 constructs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100