aws-cloudformation / aws-cloudformation/cloudformation-resource-schema

New property `relationshipRef` not in `provider.definition.schema.v1.json`

Open
#151 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
96
Forks
38
PR merge metrics
No merged PRs in 30d

Description

Recent updates to some CloudFormation resource schemas

* AWS::ECS::Cluster
* AWS::S3::MultiRegionAccessPoint
* AWS::SSM::Association

have added a new property, `relationshipRef` , to certain properties, e.g.

```json
"Region": {
"type": "object",
"properties": {
"Bucket": {
"type": "string",
"minLength": 3,
"maxLength": 63,
"pattern": "^[a-z0-9][a-z0-9//.//-]*[a-z0-9]$",
"relationshipRef": {
"typeName": "AWS::S3::Bucket",
"propertyPath": "/properties/BucketName"
}
},
"BucketAccountId": {
"type": "string",
"minLength": 12,
"maxLength": 12,
"pattern": "^[0-9]{12}$"
}
},
"required": [
"Bucket"
],
"additionalProperties": false
}
```

This property has not been added to https://github.com/aws-cloudformation/cloudformation-resource-schema/blob/master/src/main/resources/schema/provider.definition.schema.v1.json, so validation of these resource schemas against the meta-schema are failing.

Contributor guide

Open the contributing guide

Research direction

Open src/main/resources/schema/provider.definition.schema.v1.json and inspect the existing property definitions in the provider meta-schema. Add the missing relationshipRef definition implied by the examples, then validate the AWS::ECS::Cluster, AWS::S3::MultiRegionAccessPoint, and AWS::SSM::Association schemas against the meta-schema to confirm validation succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, json
Domain
cloud
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.