iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add debugging info to debugging page as well

This commit is contained in:
Khai Do 2019-09-03 09:01:00 -07:00
parent ca61b443c5
commit b442c0ad45
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/CONTRIBUTING.md vendored
View File

@ -293,7 +293,7 @@ Acceptance tests typically require other environment variables to be set for
things such as API tokens and keys. Each test should error and tell you which things such as API tokens and keys. Each test should error and tell you which
credentials are missing, so those are not documented here. credentials are missing, so those are not documented here.
#### Debugging #### Debugging Plugins
Each packer plugin runs in a separate process and communicates with RCP over a Each packer plugin runs in a separate process and communicates with RCP over a
socket therefore using a debugger will not work (be complicated at least). socket therefore using a debugger will not work (be complicated at least).

9
website/source/docs/other/debugging.html.md
View File

@ -71,6 +71,15 @@ to force the log to always go to a specific file when logging is enabled. Note
that even when `PACKER_LOG_PATH` is set, `PACKER_LOG` must be set in order for that even when `PACKER_LOG_PATH` is set, `PACKER_LOG` must be set in order for
any logging to be enabled. any logging to be enabled.
### Debugging Plugins
Each packer plugin runs in a separate process and communicates with RCP over a
socket therefore using a debugger will not work (be complicated at least).
But most of the Packer code is really simple and easy to follow with PACKER_LOG
turned on. If that doesn't work adding some extra debug print outs when you have
homed in on the problem is usually enough.
### Debugging Packer in Powershell/Windows ### Debugging Packer in Powershell/Windows
In Windows you can set the detailed logs environmental variable `PACKER_LOG` or In Windows you can set the detailed logs environmental variable `PACKER_LOG` or