This message was deleted.

sparse-intern-71089

12/29/2022, 9:14 PM

This message was deleted.

lemon-agent-27707

12/30/2022, 5:46 PM

Happy to help out with the automation API route, but have you considered using deployments? Deployments makes this a lot easier because it allows you to monitor long running async updates (creating a EKS or GKE cluster for instance might take 5 mins which is too long for sync HTTP request)

lemon-agent-27707

12/30/2022, 5:46 PM

https://www.pulumi.com/blog/pulumi-deployments/

miniature-whale-15437

01/09/2023, 8:51 AM

Thanks. We haven’t tried

Pulumi Deployments

we will look to it. Regarding long running async updates we are planning to use workflow engine to manage these “async” HTTP requests. In our current case only single workflow step is in pulumi, other steps (which not based on pulumi) still need workflow engine.

lemon-agent-27707

01/09/2023, 12:38 PM

We don't have it scheduled, but we do want to add webhook support to deployments (web hooks in response to events like deploy complete, fail, etc). That might significantly reduce the amount of code you need to write for your workflow engine. If you're seriously considering deployments as a part of the solution, we could look at trying to get the webhooks work scheduled soon.

lemon-agent-27707

01/09/2023, 12:40 PM

And multi-step workflows is something we're looking to add into deployments eventually. If you have ideas on what you would want to see here, we would appreciate it if you would open an request in the public issue tracker: https://github.com/pulumi/service-requests/issues/new/choose

2 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.