https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
g
Sorry for the response delay. We're running an update to our debugging docs to help with this info (I've got that fix in review!). That being said, if you're using the classic AWS provider, you want to add an environment variable 
TF_LOG=TRACE
with the logging level you're needing to get the diagnostics data from the provider itself. Here's the basic command I'll use:
Copy code
TF_LOG=TRACE pulumi up -v=11 --logflow --logtostderr 2>&1 | tee -a pulumi_log.txt
The environment variable asks the classic provider to bubble up data. The 
--logflow
flag bubbles up data from providers that aren't on the Terraform bridge. The end of the command tells Pulumi to share logs both to stdout/stderr and append them to a file called 
pulumi_log.txt
.
It's a lot of information that you'll get, including a lot of information from the Pulumi deployment engine that may not be applicable to you. If you can drop a code snippet (with anything confidential redacted, please!), I'll see if I can help.
w
Super helpful thanks @great-queen-39697!
g
You're welcome!!
b
@wonderful-twilight-70958: Was this problem resolved for you? I’m running into something similar and could use the help.
w
For the logging? Yes the logging works. But I haven't resolved the underlying issue (launch templates), bug still somewhere.
Open in Slack
PreviousNext
Powered by

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.

Powered by