set the channel description: Pulumi/CDK interoperability discussions. pulumi-cdk preview is now available! See https://github.com/pulumi/pulumi-cdk.

Someone had a question in the CDK slack workspace:

Anyone know if Aspects work with the interop?

hey guys, how do i use the pulumi convert option? i want to convert pulumi code from python to typescript

Would it work with CDK pipelines? Does pulumi support Stages?

I am a bit curious what it does under the hood. Is it translating the AWS CDK-generated CloudFormation to Puiumi internal representation, or a different approach? Are asset uploads handled? AWS CDK bootstrap optionally sets up S3 bucket and various IAM roles for cross-account handling, lookup etc. Are these handled in some way? This comes back to the question from @freezing-umbrella-5483 above about CDK Pipelines.

I'm guessing CDK Pipelines are out of the question because they deploy CloudFormation? They're the main benefit of AWS CDK for me, making CI/CD seamless and abstract, is there are alternative?

Any devs can chime in on the above?

just trying to test a bit this pulumi-cdk thing and I’m facing the following error:

$ pulumi up
Previewing update (pulumi-cdk-poc):
     Type                              Name                            Plan       Info
 +   pulumi:pulumi:Stack               pulumi-cdk-poc-pulumi-cdk-poc   create     1 error
 +   └─ cdk:index:Stack                teststack                       create
 +      └─ cdk:construct:TestStack     teststack/teststack             create
 +         └─ cdk:construct:Bucket     teststack/teststack/TestBucket  create
 +            └─ aws-native:s3:Bucket  testbucket560b80bc              create

Diagnostics:
  pulumi:pulumi:Stack (pulumi-cdk-poc-pulumi-cdk-poc):
    error: Error: invocation of aws-native:index:getSsmParameterString returned an error: operation error SSM: GetParameter, https response error StatusCode: 400, RequestID: e2426943-44df-4bbf-b45f-05854c386a05, ParameterNotFound:
        at Object.callback (/Users/neovasili/workspace/lab/pulumi-cdk-poc/node_modules/@pulumi/runtime/invoke.ts:162:33)
        at Object.onReceiveStatus (/Users/neovasili/workspace/lab/pulumi-cdk-poc/node_modules/@grpc/grpc-js/src/client.ts:338:26)
        at Object.onReceiveStatus (/Users/neovasili/workspace/lab/pulumi-cdk-poc/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34)
        at Object.onReceiveStatus (/Users/neovasili/workspace/lab/pulumi-cdk-poc/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
        at /Users/neovasili/workspace/lab/pulumi-cdk-poc/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
        at processTicksAndRejections (node:internal/process/task_queues:78:11)

Hello everyone! Anyone have an example using the Pulumi-CDK for cross account codepipeline deployments?

… sooo … I have a

remapCloudControlResource

question my cdk stack creates an iam user

const user = new iam.User(scope, "user", {
      userName: id,
    });

which triggers an

error: Resource type aws-native:iam:User not found

I go ahead and add logging to the adaptor to get the type name

console.log(`id ${logicalId}, type: ${typeName}`);

but I don’t see the request for a user hitting the adaptor

id eventsEventsTable18AFE818, type: AWS::DynamoDB::Table
    id eventsEventBus329C33D3, type: AWS::Events::EventBus
    id accountpublisherServiceRole224F6DB0, type: AWS::IAM::Role
    id accountpublisherServiceRoleDefaultPolicy255EE974, type: AWS::IAM::Policy
    id accountpublisher3BC67E57, type: AWS::Lambda::Function

any insights into what am I doing wrong?

okay … I’m an idiot and I retract my statement above 🙂 .. i had two stacks and I wasn’t passing the remapCloudControlResource to the second. funny how writing things out helps

Hi folks, could somebody shed some light on the vision for this project? I noticed there's been hardly any activity in the repo since Public Preview came out in May, it frankly seems pretty dead. Is there a path to GA here? Maybe a roadmap that could be shared? Or just anything that could help guide my expectations regarding the future of the project. Thanks.

Diagnostics:
  aws-native:events:EventBus (ApiEventBus0174951C):
    error: Resource type aws-native:events:EventBus not found

Hi guys, seeing the above error when using a CDK construct. Any ideas?

I have a question about names and length of names. When set up an sample infrastructure with Pulumi CDK I got this error message when running `pulumi preview`:

Diagnostics:
  aws:lb:LoadBalancer (loadbalancedserviceLB1BE8EDCE):
    error: aws:lb/loadBalancer:LoadBalancer resource 'loadbalancedserviceLB1BE8EDCE' has a problem: "name" cannot be longer than 32 characters: "loadbalancedserviceLB1BE8EDCE-403d9b7". Examine values at 'LoadBalancer.Name'.

The corresponding code looks like this:

const lbservice = new ApplicationLoadBalancedFargateService(this, 'loadbalanced-service', {
  cluster,
  taskDefinition: taskdef,
  desiredCount: 2,
  serviceName: 'my-service',
  circuitBreaker: { rollback: true },
  publicLoadBalancer: true,
  listenerPort: webserverPort,
});

The name part is not an issue with regular AWS CDK, and Pulumi generates a different (shorter) name than AWS CDK, but still too short compared to name lengths allowed by CloudFormation, it seems. The question is really what to think and consider in terms of name issues here, what would be preferred approaches besides keeping construct id values short - and how many levels will this work out with?

Is there a way to pass a pulumi provider to a cdk resource?

How should i think about a Pulumi CDK Stack? When I think of a Stack in AWS CDK land, I think of a very heavy thing at the very top-level of my app. It seems like a Pulumi CDK Stack is less impactful and can be thought more of as a Construct that simply bridges between CDK and Pulumi? It really doesn't matter where I use them? As a CDK Construct library author looking to bridge my Construct, should I extend pulumi-cdk.Stack or expect users to do that?

Is there anyway to map a pulumi.Input to a CDK Token? I'd like to have a pure Pulumi input/output contract for my Construct. Props will include

pulumi.Inputs

, be mapped to

cdk.Tokens

within the Stack and then map all

cdk.Tokens

declared within to

pulumi.Output

. This should totally encapsulate the CDK nature of the Construct such that it can be used naturally within a Pulumi app?

Oh nevermind, looks like I need to convert Output->Token or Promise->Output->Token

export declare type Input<T> = T | Promise<T> | OutputInstance<T>;

I've started creating issues to track missing resources as I find them. Let me know if this is too noisy and whether I should consolidate them into a single Issue: • https://github.com/pulumi/pulumi-cdk/issues/65 • https://github.com/pulumi/pulumi-cdk/issues/66 • https://github.com/pulumi/pulumi-cdk/issues/67 • https://github.com/pulumi/pulumi-cdk/issues/68 My remapping function can be found here: https://github.com/sam-goodwin/pulumi-cdk-classic/blob/main/src/remap.ts

Running into a problem where my logical ID is pretty long. Looks like the name of a Pulumi Resource is limited to 93 characters (100 consisting of 93 + 7)? This could quickly become a problem for CDK applications as logical IDs can get long and they have a lot in common in the earlier parts of the ID since they are constructed from a path.

aws:lambda:Permission (StockBotApiGatewayPUTeventualexecutionsexecutionIdsignalssendsignalintegrationPermission5A589):
    error: could not make instance of 'aws:lambda/permission:Permission': name 'StockBotApiGatewayPUTeventualexecutionsexecutionIdsignalssendsignalintegrationPermission5A589-' plus 7 random chars is longer than maximum length 100

Seeing an error I haven’t seen before when I attempt to deploy a CDK stack:

Diagnostics:
  pulumi:pulumi:Stack (pulumi-cdk-dev):
    error: Error: invocation of aws-native:index:getSsmParameterString returned an error: operation error SSM: GetParameter, https response error StatusCode: 400, RequestID: 8601c689-efde-477c-abc1-fa178badb77f, ParameterNotFound:

Could this be because the AWS account I’m using hasn’t been bootstrapped for CDK? I don’t think it has, so wondering if that’s what this might be about.

hi everyone, i'm kicking the tires with pulumi-cdk and I'm running into an issue with what appears to the

Vpc.fromLookup

method. Anyone else bump into this problem? I have an existing VPC that I want to use but Pulumi is erroring out and is instead using a placeholder VPC reference (vpc-12345)

Diagnostics:
  aws:lb:TargetGroup (ServiceLBPublicListenerECSGroup0CC8688C):
    error: 1 error occurred:
    	* creating LB Target Group: ValidationError: The VPC ID 'vpc-12345' is not found
    	status code: 400, request id: 5b58926c-338e-41e0-b0f8-10e7588ce64a

  aws:ec2:SecurityGroup (ServiceSecurityGroupEEA09B68):
    error: 1 error occurred:
    	* creating Security Group (ServiceSecurityGroupEEA09B68-b2c605f): InvalidVpcID.NotFound: The vpc ID 'vpc-12345' does not exist
    	status code: 400, request id: de44e778-78ef-4a97-bdfa-14a64a294ae0

  aws:ec2:SecurityGroup (ServiceLBSecurityGroupF7435A5C):
    error: 1 error occurred:
    	* creating Security Group (ServiceLBSecurityGroupF7435A5C-f054950): InvalidVpcID.NotFound: The vpc ID 'vpc-12345' does not exist
    	status code: 400, request id: 2260d61e-dfd3-4db4-9332-7110ce670c5c

  pulumi:pulumi:Stack (pulumi-spike-demo):
    error: update failed

Code:

class FargateStack extends pulumicdk.Stack {
    clusterArn: pulumi.Output<string>;
    serviceArn: pulumi.Output<string>;

    constructor(id: string, options?: pulumicdk.StackOptions) {
        super(id, options);

        const vpc = ec2.Vpc.fromLookup(this, "VPC", {
            vpcId: "vpc-000000aaaaaab",
        });

        const service = new ecsPatterns.ApplicationLoadBalancedFargateService(
            this,
            "Service",
            {
                vpc,
                cpu: 512,
                memoryLimitMiB: 1024,
                desiredCount: 1,
                taskImageOptions: {
                    image: ecs.ContainerImage.fromRegistry(
                        "amazon/amazon-ecs-sample"
                    ),
                },
            }
        );

        this.clusterArn = this.asOutput(service.cluster.clusterArn);
        this.serviceArn = this.asOutput(service.service.serviceArn);

        this.synth();
    }
}

new FargateStack("FargateStack", {
    props: {
        env: {
            region: "us-west-2",
            account: "1234567890",
        },
    },
});

This is an error you may get with the regular AWS CDK as well, if it cannot retrieve the VPC data properly. In that scenario it should use an IAM role set up by cdk bootstrap to perform the lookup and it then should update cdk.context.json with the VPC data for caching of future lookups. I believe Pulumi also depends on these IAM roles from bootstrap being there, so is your target account+region combo bootstrapped?