Is there any general advice for a `pulumi up` that...
# general
r
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?
l
You can pass
-v=N
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
--logtostderr
to print all the logs to stderr (instead of to the standard log files) and
--logflow
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
(
-v=9
is obviously "straight to 100" -- you might find
-v
is enough 🙂 )