Migrate Operations to use V3 API

Open
#1,325 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api

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.

Description

6.0.0 CAPI v2 EOL

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

Dominant language
Java
Stars
334
Forks
319
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfoundry/cf-java-client

All issues in cloudfoundry/cf-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.