cloudfoundry / cloudfoundry/bosh-cli
Cleanup complicates error-analysis for `bosh create-env`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 186
- Forks
- 170
- Avg merge
- 21h 48m
- Merged PRs (30d)
- 3
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how bosh create-env creates and cleans temporary release directories under ${HOME}/.bosh/installations/<some-uuid>/tmp/<release-folder>. Determine how cleanup behaves after an error, then preserve those directories on failure or identify where a CLI option could control retention; done means error-analysis can access the working directories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100