aws-cloudformation / aws-cloudformation/cloudformation-resource-schema
Specify properties for serialized behavior
- Dominant language
- Java
- Stars
- 96
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to create an AWS::S3::BucketNotification resource to fix a [longstanding problem](https://read.acloud.guru/cloudformation-is-an-infrastructure-graph-management-service-and-needs-to-act-more-like-it-fa234e567c82) in CloudFormation. And when I do, I'd like to enable individual notification configuration items to be managed separately. But because [the API](https://docs.aws.amazon.com/AmazonS3/latest/API/archive-RESTBucketPUTnotification.html) only supports updating the entire notification configuration, I need to serialize access to the notification configuration for a given bucket. I plan to do with a resource provider that relies on a user-account-side mechanism involving an SQS FIFO queue. It would be great if, in my schema, I could specify a property or set of properties that would cause all resources with the same values for those properties to have their requests serialized (but resources with different values for those properties could be processed in parallel).
Contributor guide
Research direction
No implementation file or test is identified. Start by reviewing the current resource schema definition and the linked S3 notification API, then determine how serialization properties would be represented and validated; done means the schema can express the requested grouping while allowing different groups to proceed in parallel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100