cloudfoundry / cloudfoundry/cf-java-client
Migrate Operations to use V3 API
Open
Nobody has claimed this yet.
6.0.0
CAPI v2 EOL
- Dominant language
- Java
- Stars
- 334
- Forks
- 319
- PR merge metrics
- No merged PRs in 30d
Description
To address CAPI v2 EOL (#1312), we need to migrate all Operations classes to use the v3 API. This work will induce breaking changes.
This issue tracks all the operations individually to follow what has been ported
To port
- DefaultApplications
- DefaultServices
- DefaultOrganizationAdmin
- DefaultOrganizations.java
- DefaultServiceAdmin
- DefaultSpaceAdmin
- DefaultSpaces
- DefaultUserAdmin
- DefaultNetworkPolicies
- DefaultRoutes
Done
- DefaultBuildPacks (#1323)
- DefaultDomains (#1327)
- DefaultStacks (#1329)
Delivered
None
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
Begin with #1312 and the completed migration issues #1323, #1327, and #1329 to understand the migration pattern, then inspect the remaining named Operations classes. Done when every unchecked class is ported to the v3 API and the checklist reflects the completed work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100