Am Montag, den 24.08.2020, 11:06 -0700 schrieb pkraw...@gmail.com:
> Justin, I implemented the suggestion you made however after running
> the curl command against the 2 environments having the issue and
> receiving the 204 response, the puppet module is still getting the
> 500 error. Do you or an
VERSION 2.24.1
*in this release*
🔧 *bug fix*
- This release fixes a critical bug introduced in Bolt 2.24.0 that would
cause Bolt to fail when it tried to write the bolt-debug.log file to a
project directory that did not exist. Bolt will now only try to write this
log file when the p
VERSION 2.24.0
*in this release*
✨ *new features*
- Debugging Bolt commands just got easier, and no longer requires
re-running a command with the --debug option. Bolt now automatically
logs activity at the debug level to bolt-debug.log in the project
directory. This log will be trun
Justin, I implemented the suggestion you made however after running the
curl command against the 2 environments having the issue and receiving the
204 response, the puppet module is still getting the 500 error. Do you or
anyone else have any other suggestions? Is it possible it's related to
r