You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using bosh create-env, the cli may start quite some sub-processes to compile releases. It works on some temporary directories looking like ${HOME}/.bosh/installations/<some-uuid>/tmp/<release-folder>.
Folders in there get cleaned-up after the bosh-cli finishes. This happens as well in case of an error. This however is unfortunate and significantly complicates debugging. Can the bosh-cli please either not delete these directories in case of an error or – at least – offer a cli-option to keep everything within the working-directories?
The text was updated successfully, but these errors were encountered:
When using
bosh create-env
, the cli may start quite some sub-processes to compile releases. It works on some temporary directories looking like${HOME}/.bosh/installations/<some-uuid>/tmp/<release-folder>
.Folders in there get cleaned-up after the bosh-cli finishes. This happens as well in case of an error. This however is unfortunate and significantly complicates debugging. Can the bosh-cli please either not delete these directories in case of an error or – at least – offer a cli-option to keep everything within the working-directories?
The text was updated successfully, but these errors were encountered: