cloudfoundry / cloudfoundry/multiapps-cli-plugin
Question: Is it possible to keep the old instances after a bg-deploy --no-confirm
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 87
- Forks
- 42
- Avg merge
- 17d 21h
- Merged PRs (30d)
- 1
Description
We would like to keep the old instances after a blue-green deployment so that we can switch easily after we found an issue that was not found by the pipeline.
Looking at cf bg-deploy --help, there seems to be no option.
Wdyt? Would you consider adding such an option?
The community cf-cli plugin for blue-green deployments of native apps also supports this https://github.com/bluemixgaragelondon/cf-blue-green-deploy
Contributor guide
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 reading the cf bg-deploy --help entry point and tracing how blue-green deployments handle old instances when --no-confirm is used. Compare the requested behavior with the linked community cf-cli plugin, then identify the relevant tests or deployment flow. Done means an option can preserve old instances and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100