(assets, aws-lambda): Add asset metadata for nested stack and image-type Lambda Function

[hawflau]

Add CloudFormation resource metadata for SAM to find local assets for the resources below:

1. local nested stack
2. image-type Lambda Function

Use Case

In this PR, resource metadata was added for zip-type Lambda Function for SAM to find local assets (for example, for running sam local invoke). As SAM CLI now supports local nested stacks and image-type Lambda Function, adding resource metadata for these two types of resources will enable SAM CLI to support CDK-synthed templates with these two types of resources.

Proposed Solution

I believe the implementation will be very similar to the PR mentioned above.
For local nested stack, the value of aws::asset::property should be "TemplateURL".
For image-type Lambda Function, it's a bit tricky - because the local path has to sit inside the ImageUri property under Code, I propose the value of aws::asset::property to be "Code.ImageUri".

Example for local nested stack (in yaml):

nestedstackNestedStacknestedstackNestedStackResource71CDD241:
    Type: AWS::CloudFormation::Stack
    Properties:
      TemplateURL:
        Fn::Join:
          - ""
          - - https://s3.
            - Ref: AWS::Region
            - "."
            - Ref: AWS::URLSuffix
            - /
            - Ref: AssetParameters8cb8f69d88bba4ff29b6cfb1808b58a5d4b721166d137c367a744f8b6e5e65bfS3BucketFD698EA9
            - /
            - Fn::Select:
                - 0
                - Fn::Split:
                    - "||"
                    - Ref: AssetParameters8cb8f69d88bba4ff29b6cfb1808b58a5d4b721166d137c367a744f8b6e5e65bfS3VersionKey60183D77
            - Fn::Select:
                - 1
                - Fn::Split:
                    - "||"
                    - Ref: AssetParameters8cb8f69d88bba4ff29b6cfb1808b58a5d4b721166d137c367a744f8b6e5e65bfS3VersionKey60183D77
      Parameters:
        # ...
    UpdateReplacePolicy: Delete
    DeletionPolicy: Delete
    Metadata:
      aws:cdk:path: root-stack/nested-stack.NestedStack/nested-stack.NestedStackResource
      aws:asset:path: rootstacknestedstackACD02B51.nested.template.json # <- new
      aws:asset:property: TemplateURL # <- new

Example for image-type Lambda Function (in yaml):

containerfunction2D259B7A:
    Type: AWS::Lambda::Function
    Properties:
      Code:
        ImageUri:
          Fn::Join:
            - ""
            - - Ref: AWS::AccountId
              - .dkr.ecr.
              - Ref: AWS::Region
              - "."
              - Ref: AWS::URLSuffix
              - /aws-cdk/assets:58ff0b9a5ea87b6462d9a416b6066e346ae4b60f8f7ec6018972f50867181a9c
      Role:
        Fn::GetAtt:
          - containerfunctionServiceRole5EB80FD7
          - Arn
      ImageConfig:
        Command:
          - app.get
        EntryPoint:
          - /lambda-entrypoint.sh
      PackageType: Image
    DependsOn:
      - containerfunctionServiceRole5EB80FD7
    Metadata:
      aws:cdk:path: root-stack/container-function/Resource
      aws:asset:path: path/to/lambda_code # <- new
      aws:asset:property: Code.ImageUri # <- new

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[eladb]

@hawflau makes total sense to add support for this. I've tagged it as P1, which means it should be on our near-term roadmap.

We welcome community contributions! If you are able, we encourage you to contribute a bug fix or new feature to the CDK. If you decide to contribute, please start an engineering discussion in this issue to ensure there is a commonly understood design before submitting code. This will minimize the number of review cycles and get your code merged faster.

[moelasmar]

Added PR to add Asset metadata to SpecRestApi resource when it contains AssetApiDefinition.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.