fix(dynamoDB): make TableV2 taggable

[5d]

Issue # (if applicable)

Closes #30631

Reason for this change

The AWS::DynamoDB::GlobalTable resource does not natively support tags. However, at the L2 level (TableV2), the tags option is available when creating this resource, which may give customers the impression that it is taggable. When customers apply tags using the aspect at the TableV2 level, it’s likely they intend to tag all replicas, as each replica has its own tags property as well. This behavior also aligns with the related construct documentation.

Description of changes

• Enable tagging for TableV2
• If a tag key is defined in the replica tags properties, it will take precedence over the TagAspect for that key, as it is more specific.
• Keep the tags property behavior in TableV2
  • Update the description doc on it to reflect that it only applies to the default replica table

Description of how you validated changes

• added new unit test cases
• deployed related integration test cases

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[GavinZZ]

IMO I think this is an issue with the spec2cdk generation and something we should fix in the L1 generation instead of L2 side.

[GavinZZ]

Thanks for addressing the other comments. I'm happy to approve once we check with the service team and update the documentation.

[5d]

Thanks for addressing the other comments. I'm happy to approve once we check with the service team and update the documentation.

Thanks for reviewing this! @GavinZZ, I'll follow up with the product team.

Pull request has been modified.

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[moelasmar]

In general looks good to me, I just left some minor comments.

Pull request has been modified.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 4506d29
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

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.