chore(codepipeline): generate stack name in codepipeline when stack name is unresolved token

[GavinZZ]

Issue # (if applicable)

Closes #31436.

Reason for this change

When nested stack is used with CodePipeline, the stack name is actually a token which will fail regex check. We can't simply add a Token.isUnresolved check before the regex check because stack name must be a resolved string otherwise the template file would include Token[xxx].

Description of changes

The only feasible fix would be allowing users to override the nested stack name if users provide one. Currently nested stack names are auto-generated and are a token value. Allow users to specify the stack name.

Description of how you validated changes

New integ tests pass. Existing tests pass.

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]

Pending integration test.

[Leo10Gama]

Looks pretty good, just a few minor comments. The description also mentions unit tests added but I only see an integ test change. If we can only see the changes in effect when deploying, it should be fine to omit unit tests, but we should update the PR description.

[Leo10Gama]

LGTM, thanks!

[Leo10Gama]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[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: 4a13c45
• 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.