cloudfoundry / cloudfoundry/cli
Update the cli libraries
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 990
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 8
Description
Please provide details on the following items. Failure to do so may result in deletion of your feature request.
What's the user value of this feature request?
Currently the cli while actively maintained has several depending libraries (For E.G https://github.com/cloudfoundry-incubator/cfnetworking-cli-api are archived meaning there are no updates or maintenance. Could cf client update these. It seems like the go-cf client in the cf-community is in a better shape of maintenance compared. can that be used.
**Who is the functionality for? Who will use this feature? **
A common reusable client package that is used by the CLI and other clients (for eg terraform provider) can reduce duplication and improve uniformity.
How often will this functionality be used by the user? How often will they use this feature?
The focus is on the development and code quality. The libraries need to be up to date for security and maintainability reasons.
Who else is affected by the change?
Everybody that uses this client and has a concern for security
Is your feature request related to a problem? Please describe.
Some of the packages in the CLI are outdated and archived. Since the CLI is the 'model' client it should be made available as reusable packages that are easy to consume in other clients as well. (For eg terraform providers etc)
Describe the solution you'd like
A new CLI is built using a common set of cf client packages (for eg go-cf client) and the CLI can be referenced for the implementation of other CF clients as well.
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
The issue names no files, tests, or entry points. Start by inventorying the CLI's dependencies and comparing them with the referenced go-cf client, then define the reusable package scope and migration criteria; done would require an agreed implementation plan and updated client dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100