Closed LJArendse closed 3 years ago
You are correct that the Required
, Type
, and Update
required fields are auto-generated.
I would suggest changing the Required field from No
to Conditional
.
Per the note:
If you specify the SourceDBInstanceIdentifier or SnapshotIdentifier property, don't specify this property. The value is inherited from the source DB instance or snapshot.
I updated the documentation for MasterUserName and MasterUserPassword. They now have Required: Conditional.
Hi @randyurbano and @rachfop, thanks for the clarification and help. The Required: Conditional
makes the most sense š„
I am happy to close this issue, if you are?
Yes, I'll close it. Thanks again for your feedback.
The current Cloudformation User Guide for
AWS::RDS::DBCluster
lists both theMasterUsername
andMasterUserPassword
properties asRequired: No
(see https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html).Issue Labels: Resource Specification and/or question
Whilst experimenting and deploying my own RDS DB cluster with the following properties (note this is just a subset of my properties):
Please note that I am not listing the
MasterUsername
andMasterUserPassword
properties. Additionally, I did not specify theSourceDBInstanceIdentifier
orSnapshotIdentifier
.Cloudformation throws the following errors when either the
MasterUsername
and/orMasterUserPassword
properties are omitted. See error message screenshots below: Therefore, to me at least, it looks like theMasterUsername
andMasterUserPassword
properties should be listed asRequired: Yes
.From what I know, the
Required
,Type
, andUpdate requires
fields are auto-generated from the AWS CloudFormation resource specification. I am logging the issue here, as I am not sure where to log a ticket for the fix in the resource specification: i.e. af-south-1 CloudFormationResourceSpecification.json:If anyone has any additional insight or guidance please feel free to comment. I might be missing something obvious, so please comment.