Skip to content

(signer): signing profile name in L2 is not present in generated L1 template #35030

@aemada-aws

Description

@aemada-aws

Describe the bug

This CDK code:

const ImageSigningProfile = new SigningProfile(app, 'ImageSigningProfile', {
  platform: aws_signer.Platform.NOTATION_OCI_SHA384_ECDSA,
  signingProfileName: 'TEST_SIGNING_PROFILE_NAME',
});

produces the following CFN template:

  "ImageSigningProfile2D863058": {
   "Type": "AWS::Signer::SigningProfile",
   "Properties": {
    "PlatformId": "Notation-OCI-SHA384-ECDSA",
    "SignatureValidityPeriod": {
     "Type": "MONTHS",
     "Value": 135
    }
   },
   "Metadata": {
    "aws:cdk:path": "ZeddemoreKnowledgeBase-Lambda/ImageSigningProfile/Resource"
   }
  },

which is missing the profile name

Regression Issue

  • Select this option if this issue appears to be a regression.

Last Known Working CDK Library Version

No response

Expected Behavior

Signing name should be included in L1 template

Current Behavior

It is not included in L1 template

Reproduction Steps

const ImageSigningProfile = new SigningProfile(app, 'ImageSigningProfile', {
platform: aws_signer.Platform.NOTATION_OCI_SHA384_ECDSA,
signingProfileName: 'TEST_SIGNING_PROFILE_NAME',
});

Possible Solution

No response

Additional Information/Context

No response

AWS CDK Library version (aws-cdk-lib)

2.206

AWS CDK CLI version

2.1020.2

Node.js Version

20

OS

Mac OS

Language

TypeScript

Language Version

No response

Other information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions