This message was deleted.

The closest we have currently is

pulumi stack --show-ids

, but that's not in a parseable format. We plan to add a

pulumi resource

command to get details of a given resource - see https://github.com/pulumi/pulumi/issues/184. BTW - PRs welcome on this 🙂!

And if I want to do it without using the cli at all. 100% code approach. Not considered ?

Hmm - maybe I misunderstand the question then. What did you have in mind when you say "reference after deployment in a Node script"? Is that script something that is not part of a deployment, but just used to script against some cloud APIs?

Yep exactly, it a dynamoDB seeder

Got it. Currently there is no way to do that unless you run the DB seeder as part of the deployment program (potentially only when a config variable is set, or as part of a custom resources that only triggers when a resource gets re-created). It's an interesting idea though to provide a way to load into a normal Node program a realized view of the resources in a Pulumi deployment.

Yep, that's what I figured. I didn't want to include it in the deployment phase because I like the flexibility of it being an outside script. Would be really cool to be able to have a resource view in any Node program. A lot of work also I think 😆