fix(signer): not correctly passing signingProfileName to CfnSigningProfile

[pahud]

Issue # (if applicable)

Closes #35030.

Reason for this change

The signingProfileName property set in the AWS CDK's Signer module L2 construct is not being properly propagated to the generated L1 CloudFormation template. This causes AWS Signer profiles to be created without the specified name, which leads to unexpected behavior and difficulty in managing resources.

Description of changes

• Modified the SigningProfile class constructor to pass this.physicalName to the L1 CfnSigningProfile resource's profileName property
• Updated unit tests to explicitly verify that the ProfileName property is correctly included in the CloudFormation template when signingProfileName is provided, and absent when not provided

These changes ensure that when a user specifies a signingProfileName, it will be included in the generated CloudFormation template as the ProfileName property. The fix maintains backward compatibility and doesn't introduce any breaking changes to the API.

Describe any new or updated permissions being added

No new or updated IAM permissions are needed for this change.

Description of how you validated changes

• Updated existing unit tests to verify the fix
• Verified that the existing integration test for SigningProfile with a name works correctly
• Manually tested with a simple test application that uses SigningProfile with signingProfileName

Why we need a FF to avoid BC

If we had specified a signingProfileName in their SigningProfile construct, the CloudFormation template will now include this name as the ProfileName property.

Previously, this name was ignored in the CloudFormation template, causing CloudFormation to auto-generate a name for the signing profile.

Upon deployment with the updated CDK version, CloudFormation will detect this as a change and will:
Create a new signing profile with the specified name.

Delete the old signing profile that had an auto-generated name

This replacement of the signing profile can break existing references to the profile and disrupt workflows that depend on the existing profile hence this PR introduced a FF to avoid this.

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]

(This review is outdated)

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

[aws-cdk-automation]

AWS CodeBuild CI Report

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

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

[aws-cdk-automation]

➡️ PR build request submitted to test-main-pipeline ⬅️

A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

[aemada-aws]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

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

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks.

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

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