Flink v1.15 was released on Kinesis Analytics a couple of weeks ago, and it’s still not possible to use it when deploying via Pulumi. Same thing with node.js v18 on Lambda. I knew Flink v1.15 was being released on Kinesis in November so I built my analytics app to work with it, and have been eagerly waiting for Flink v1.15 for a couple of months now. I feel kinda disappointed that the holdup now is Pulumi not allowing me to deploy the app, despite the new enum value being available in the Terraform AWS provider since 9 days ago The team & everyone on Slack have been super helpful when I’ve asked about the new Kinesis and Lambda runtimes, and I also note that there was the Thanksgiving break in the US. But I’m now concerned about the lead time here to add a new entry to an enum value, and starting to research whether I should just move my IaC over to terraform to avoid running into this type of issue again I know Pulumi is free & open source, and I’m not criticising the time taken to bring the new enum value through to the CLI, just thought it might be a feedback signal the pulumi team might want to think about as I imagine this can impact adoption

Hi Matt, on the classic or native provider?

Hi @icy-controller-6092 have you raised an issue in the AWS provider repo about this? https://github.com/pulumi/pulumi-aws

Hey there, yes I raised this issue 9 days ago: https://github.com/pulumi/pulumi-aws/issues/2230 Levi has been very helpful 🙇‍♂️ and I can see that it appears to be a complicated upstream pipeline to bring the latest updates through to the CLI

@icy-controller-6092 As I said in the other thread, you can use the string value of the enum. So this works:

const fn = new aws.lambda.Function("fn", {
    code: new pulumi.asset.AssetArchive({
        ".": new pulumi.asset.FileArchive("./app")
    }),
    handler: "index.handler",
    runtime: "nodejs18.x",
    role: role.arn
})