(docdb): copyTagsToSnapshot is missing in the DatabaseCluster Construct

[mazyu36]

Describe the feature

In the DatabaseCluster Construct, copyTagsToSnapshot is missing.

Use Case

Use this when you want to copy tags to snapshots.

Proposed Solution

Add copyTagsToSnapshot to the DatabaseCluster Construct.

const cluster = new docdb.DatabaseCluster(this, 'Database', {
  masterUser: {
    username: 'myuser', // NOTE: 'admin' is reserved by DocumentDB
    excludeCharacters: '\"@/:', // optional, defaults to the set "\"@/" and is also used for eventually created rotations
    secretName: '/myapp/mydocdb/masteruser', // optional, if you prefer to specify the secret name
  },
  instanceType: ec2.InstanceType.of(ec2.InstanceClass.MEMORY5, ec2.InstanceSize.LARGE),
  vpc,
  copyTagsToSnapshot: true, // Add
});

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.140.0

Environment details (OS name and version, etc.)

MacOS

[ashishdhingra]

Refer AWS::DocDB::DBCluster, CopyTagsToSnapshot is a supported property.

@mazyu36 Looks like you linked this issue to a PR for experimental aws-neptune-alpha construct. Please check if you intended to create a separate PR for aws-cdk-lib.aws_docdb DatabaseCluster construct.

Thanks,
Ashish

[mazyu36]

@ashishdhingra
Thanks for your confirmation.
I mistakenly linked a neptune PR, so I've now removed.

For the different module, I plan to create a separate pull request for the docdb changes, distinct from the one for neptune. Apologies for the confusion.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[aws-cdk-automation]

Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.