This message was deleted.

so cool!

party

am I getting it right, basically you give an ability to run the

pulumi up

using the code and you can

await

for specific resource?

basically you give an ability to run the 

pulumi up

 using the code

Yes, you can create and select stacks programatically. This also includes lifecycle operations like getting/setting config, running

up

refresh

destroy

preview

. In addition to this, you can write your pulumi program "inline", meaning you don't have to have a separate project.

you can 

await

 for specific resource

This is not quite true. The same pulumi programming model is used, nothing has changed there. You'll still have to use

All

and

Apply

as normal. But you can

await stack.up()

, and then synchronously retrieve the outputs.

thanks for reply @lemon-agent-27707, I did already check it

The new inline style does mean you can set breakpoints and debug. This is really cool!

taking DB Migration example: the

migration

steps itself will not make any records in the stack, which is probably will not give you any vision to the state? Basically, we can’t see that the migration has been applied to the stack. Thanks

You've got it. The database migration is more of an imperative activity. The example has it written in an idempotent way. It allows you to combine declarative infrastructure with all of the other things you need to do as well but aren't handled by pulumi.

Today it’s available in preview for TypeScript/JavaScript

Is that link wrong?

Ah, good catch! Here's the correct link https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/x/automation/ I'll get the post updated.

Thanks! On the topic, I'd love to see a https://github.com/spotify/backstage plugin using the pulumi automation API

@millions-judge-24978 that sounds really interesting. What sort of things would you want it to do?

I'm still just kind exploring the backstage project, but I imagine some UI in backstage would trigger the pulumi automation API to deploy/update stacks, and status reported back to backstage. Project templates are a concept in backstage I believe. New project from template would correspond to deploying a pulumi stack with parameters