feat(cognito): add tags property for user pool

[kdnakt]

Issue # (if applicable)

Reason for this change

The userPoolTags property existed in the L1 construct but was not present in the L2 construct

Description of changes

Add the tags property for UserPool

Description of how you validated changes

Added a unit test and an integration test.

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

[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.

[badmintoncryer]

Thank you for your contribution! I've added 2 minor comments.

[kdnakt]

@badmintoncryer Thank you for the suggestion, I've just committed them.

[badmintoncryer]

Thanks!

[aws-cdk-automation]

AWS CodeBuild CI Report

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

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

[GavinZZ]

In L2 construct, we don't directly provide tags property even though it's supported in the relevant L1 construct.

The typical way of adding tag is through Tags.of(this).add. Does this method work for you?

[kdnakt]

Thank you, the Tags.of(this).add solution worked for me.
Would you recommend that I close this PR now?

[GavinZZ]

As a side note, if you use this, it will default to result in tags being added at stack level this propagating to all resources created in the stack.

If this is not the ideal solution you could also do Tags.of(resource).

Let’s close this PR as I believe this change is not needed anymore.

[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.