Is there any general advice for a `pulumi up` that...
# general
Is there any general advice for a
pulumi up
that seems to be taking a very long time without failure? An way to get more detailed logs while
pulumi up
is still spinning?
You can pass
where N is a number between 1 and 11 to get increasing degrees of verbosity (generally >10 should be avoided as Pulumi will emit secrets at levels higher than 9). You can also pass
to print all the logs to stderr (instead of to the standard log files) and
to flow all logs from the various sub-parts (e.g. the providers such as AWS, GCP, etc.). TL;DR, it'll spit out a lot but you should get more information from something like:
Copy code
pulumi up -v=9 --logtostderr --logflow 2>&1 | tee /path/to/some/log/file
is obviously "straight to 100" -- you might find
is enough 🙂 )