Error Status Codes from Cloud Foundry API V3
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reading the getApplicationInstances example in DefaultApplications and the behavior of ExceptionUtils.statusCode. Compare the listed V2 status codes with the Cloud Foundry API V3 error documentation linked in the issue, then identify authoritative sources for endpoint-specific errors. Done means documenting the source or confirming that no equivalent list exists.
Written by the indexing model from the issue text.
Description
Hello everyone. Currently I am working on contribution for the get() operation for applicatons. The essence of contrubution is to migrate client implementation from v2 CF APIs to v3. In DefaultApplications Java class this method is used for getting Application details:
private static Mono<ApplicationInstancesResponse> getApplicationInstances(CloudFoundryClient
cloudFoundryClient, String applicationId) {
return requestApplicationInstances(cloudFoundryClient, applicationId)
.onErrorResume(ExceptionUtils.statusCode(CF_BUILDPACK_COMPILED_FAILED, CF_INSTANCES_ERROR,
CF_STAGING_NOT_FINISHED, CF_STAGING_TIME_EXPIRED, CF_STAGING_ERROR),
t -> Mono.just(ApplicationInstancesResponse.builder().build()));
}
Here we see the handling of various errors by their status codes. Method ExceptionUtils.statusCode just checks if at least one of the passed codes to this method matches the code returned from the API of the V2.
In the DefaultApplications defined following status codes:
private static final int CF_APP_STOPPED_STATS_ERROR = 200003;
private static final int CF_BUILDPACK_COMPILED_FAILED = 170004;
private static final int CF_INSTANCES_ERROR = 220001;
private static final int CF_SERVICE_ALREADY_BOUND = 90003;
private static final int CF_STAGING_ERROR = 170001;
private static final int CF_STAGING_NOT_FINISHED = 170002;
private static final int CF_STAGING_TIME_EXPIRED = 170007;
I want to ask a question where the list of these codes was taken from?
(I tried to find them in the CF API V2 documentation but didn't find them unfortunately.).
Also, do we have similar list of errors for CF V3 APIs? If we have could please share with me some sources, where I can find them? (I tried to find them there: https://v3-apidocs.cloudfoundry.org/version/3.131.0/index.html#errors) But it is common information about the errors and there we don't have info about the returning errors for a specific API endpoint.
- Dominant language
- Java
- Stars
- 334
- Forks
- 319
- PR merge metrics
- No merged PRs in 30d
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.
More from cloudfoundry/cf-java-client
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cloudfoundry/cf-java-client#1374 ·
-
Integration tests fail: test-service-broker.jar incompatible with java-buildpack v5 (JDK 17 default) Open
Difficulty 2/5 Half a day Newbie friendliness 74/100
cloudfoundry/cf-java-client#1344 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
cloudfoundry/cf-java-client#1376 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
cloudfoundry/cf-java-client#1373 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
cloudfoundry/cf-java-client#1370 ·
All issues in cloudfoundry/cf-java-client
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100