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.

Pulumi Community

Hi team, very new to pulumi. Wanted to understand if it's possible to enacapsulate pulumi as dependency in our cli tool to manage the lifecycle of our custom resources ?

If yes, would this be done using the automation api ?

Yes, and yes. Or you could use Pulumi IaC as your CLI tool and call other things from it :slightly_smiling_face:

Thanks for the reply <@U012UJTT55M>. Will start with a small POC on this.

We've done a CLI tool for parameterisation (Go templated YAML files for global, env and app/module) - also runs a set of modules in right order based on another YAML file.  Works nicely, using Pulumi Automation API.

We also run Terraform (via Terragrunt) under same CLI, and do K8s manifest templating (Helm-like but without Helm).

This is a pattern I've seen in various places before using Pulumi, ranging from wrapper shell scripts to Ansible to custom CLIs.

Our tool also does S3 state backend, making this invisible to user with actual S3 bucket determined by the target AWS account for a given environment