cloudfoundry / cloudfoundry/cli
Allow setting application features in deployment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 990
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 8
Description
When doing a "cf push" I am able to add information such as a manifest using -f flag.
I would like to add a flag for application features -
https://v3-apidocs.cloudfoundry.org/version/3.195.0/index.html#update-an-app-feature
something like:
cf push --features '{"file-based-vcap-services":enabled}'
This is important as it's not something that is opened in the manifest.
although I think it should have been.
What's the user value of this feature request?
The developer using the CLI can push the application in a ready state without needing to do a restart.
Who is the functionality for?
Operations and developers that are using the cloud foundry platform.
How often will this functionality be used by the user?
Since we use blue-green deployment it will be used massively.
Who else is affected by the change?
There is no affect on whoever is not using the new flag.
Is your feature request related to a problem? Please describe.
The problem is that application features are not exposed in the manifest of an app, I can't change them using a manifest.
Describe the solution you'd like
cf push --features '{"file-based-vcap-services":enabled}'
Describe alternatives you've considered
Additional context
This feature request is related to the new binding feature: file-based-vcap-services which from my perspective should be also configurable in the manifest but unfortunately it's not.
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 at the cf push command and review the Cloud Foundry v3 update-an-app-feature API linked in the issue. Determine how the requested --features input should be represented during deployment, then verify that cf push can leave the application with the requested features enabled without requiring a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100