This message was deleted.

sparse-intern-71089

08/02/2020, 11:34 AM

This message was deleted.

bright-policeman-55860

08/02/2020, 11:56 AM

jq

would be your friend, but not all resources have the same outputs, i.e., not everything has an

arn

id

bright-policeman-55860

08/02/2020, 12:22 PM

Something like this will help, I think:

bright-policeman-55860

08/02/2020, 12:23 PM

Copy code

pulumi stack export | jq -r '.deployment.resources[] | {"urn": .urn, "arn": .arn, "id": .id}'

chilly-hydrogen-41038

08/02/2020, 5:36 PM

Thank you @bright-policeman-55860 your solution is a good tip. I also managed to use auto-tagging (https://www.pulumi.com/blog/automatically-enforcing-aws-resource-tagging-policies/) and created a “Resource Group” in the AWS Console. It’s usefull to have a general overview of the AWS resources created by Pulumi.

white-balloon-205

08/04/2020, 12:30 AM

> From the CloudFormation console it’s easy to find an AWS resource create by the stack, everything is linked under the resources tab. Just a note that the Pulumi Console (https://app.pulumi.com/) offers a similar feature. See the links on the right hand side which deep link into the AWS console (and Azure and GCP and Kubernetes API server).

4 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.