cloudformation-resource-schema
cloudformation-resource-schema copied to clipboard
The CloudFormation Resource Schema defines the shape and semantic for resources provisioned by CloudFormation. It is used by provider developers using the CloudFormation RPDK.
*Issue #, if available:* *Description of changes:* Fix default tagging metadata value will be override issue. By submitting this pull request, I confirm that my contribution is made under the...
- Update test and readme to use JQ instead of JSONata to be compatible with the backend *Issue #, if available:* *Description of changes:* By submitting this pull request, I...
Troubleshooting schema validation errors is cumbersome and should be more customer focused. While troubleshooting a resource being provisioned the builder is left trying to figure out a few things. Based...
* [x] a property can't be readOnly and writeOnly. * [x] a property can't be readOnly and createOnly. * [x] an identifier must be either createOnly or readOnly (note: this...
Hi, I noticed the pattern requirement for the `BackupSelection.SelectionName` property of the `AWS::Backup::BackupSelection` resource in `eu-central-1` is different to other regions. The schema definitions for this property are as follows:...
Currently, the CloudFormation resource specification and the documentation do not distinguish the difference between an update operation which _fully replaces_ a resource (including data loss) from those updates which cause...
Currently, if set a value for a readOnlyProperties, this will be silently ignored. We should have validation to enforce this validation.
We're building an S3 bucket notification resource, to solve a [long-standing problem](https://read.acloud.guru/cloudformation-is-an-infrastructure-graph-management-service-and-needs-to-act-more-like-it-fa234e567c82). Each item in the notification configuration for a bucket is a separate resource. However, the rules for bucket...
From https://github.com/aws-cloudformation/aws-cloudformation-rpdk/issues/68 At the moment, examples fields aren't validated. The result is invalid examples, e.g. this ARN (rouge dot at the end): ``` "Arn": { "type": "string", "pattern": "^arn:aws(-(cn|gov))?:[a-z-]+:(([a-z]+-)+[0-9])?:([0-9]{12})?:[^.]+$" "examples":...
Only `String` or `Number` type property can be `primaryIdentifier`. We should enforce it during schema validation.