awslabs / awslabs/aws-solutions-constructs
fix(Make IoT and KinesisStreams Constructs Consistent): Update IoT and KinesisStreams constructs to match DESIGN_GUIDELINES.md
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 268
- Avg merge
- 5h 18m
- Merged PRs (30d)
- 5
Description
DESIGN_GUIDELINES.md has been updated to reflect some additional Props and Properties that had been implemented on some constructs but were not consistent.
We need to align all the iot and kinesisstreams constructs with the current DESIGN_GUIDELINES.md, including, but not necessarily limited to:
**Kinesis Streams**
createCloudWatchAlarms
cloudWatchAlarms
**Iot**
iotTopicRule (as a property)
### Use Case
### Proposed Solution
### Other
* [ ] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change
---
This is a :rocket: Feature Request
Contributor guide
Research direction
Start with DESIGN_GUIDELINES.md and locate the IoT and KinesisStreams constructs it describes. Compare their props and properties with the guideline entries, especially createCloudWatchAlarms, cloudWatchAlarms, and iotTopicRule; the work is done when both constructs consistently expose the current documented API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100