Hey I'm diving into the database migration example to try to do something very similar for each way I want to seed a new database. I'm looking for best practices on shared configuration since this seeded database will share 100% of its configuration (cluster name, database name) with the feature app layer it's being created for. Is there a way to reference external stack outputs inside an automation inline program? My naive attempt at call

new pulumi.Config()

yielded:

throw new Error("Program run without the Pulumi engine available; re-run using the `pulumi` CLI");`

You could create a ConfigMap on the top level and pass it to setAllConfig for each stack.

My cluster-configuration stack sets up the cluster. I'd like to use that cluster to spin up a rails app in a job to do migrations/(seed or load a sanitized copy of some real data). Ideally I could just pass the parent stacks as process args to the automation api script to initialize/destroy the database at the appropriate start and end caps for a particular feature life cycle.

The multi_stack_orchestration example is only in Go but it applies to this use case. If you’re willing to read through some Go code, the concept is applicable: https://github.com/pulumi/automation-api-examples/blob/main/go/multi_stack_orchestration/main.go

Totally, thank you