Skip to content

(custom-resources/provider-framework): can not set the correct physical resource id for an asynchronous provider #18670

@pflorek

Description

@pflorek

What is the problem?

If I use the asynchronous provider I can't set the physical resource id in the isComplete handler.

Reproduction Steps

Create an asynchronous provider and try to set the physical resource in the isComplete handler.

What did you expect to happen?

I can set the correct physical resource id of the actual created resource in the isComplete handler.

What actually happened?

I can use the request id or a temporary creation handle or anything else. This forces me to store the correct physical resource id in DynamoDB, SSM Paramstore, ... and writing a lot of more glue code.

CDK CLI Version

2.8.0

Framework Version

2.8.0

Node.js Version

14

OS

MacOS

Language

Typescript

Language Version

4.5.5

Other information

#18630 🚀

Metadata

Metadata

Assignees

No one assigned

    Labels

    @aws-cdk/custom-resourcesRelated to AWS CDK Custom ResourcesbugThis issue is a bug.effort/smallSmall work item – less than a day of effortp1

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions