2.2. API endpoints
The following API endpoints are available:
/apis/oauth.openshift.io/v1/oauthaccesstokens-
DELETE: delete collection of OAuthAccessToken -
GET: list or watch objects of kind OAuthAccessToken -
POST: create an OAuthAccessToken
-
/apis/oauth.openshift.io/v1/watch/oauthaccesstokens-
GET: watch individual changes to a list of OAuthAccessToken. deprecated: use the 'watch' parameter with a list operation instead.
-
/apis/oauth.openshift.io/v1/oauthaccesstokens/{name}-
DELETE: delete an OAuthAccessToken -
GET: read the specified OAuthAccessToken -
PATCH: partially update the specified OAuthAccessToken -
PUT: replace the specified OAuthAccessToken
-
/apis/oauth.openshift.io/v1/watch/oauthaccesstokens/{name}-
GET: watch changes to an object of kind OAuthAccessToken. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
-
2.2.1. /apis/oauth.openshift.io/v1/oauthaccesstokens 링크 복사링크가 클립보드에 복사되었습니다!
- HTTP method
-
DELETE - Description
- delete collection of OAuthAccessToken
| Parameter | Type | Description |
|---|---|---|
|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
| HTTP code | Reponse body |
|---|---|
| 200 - OK |
|
| 401 - Unauthorized | Empty |
- HTTP method
-
GET - Description
- list or watch objects of kind OAuthAccessToken
| HTTP code | Reponse body |
|---|---|
| 200 - OK |
|
| 401 - Unauthorized | Empty |
- HTTP method
-
POST - Description
- create an OAuthAccessToken
| Parameter | Type | Description |
|---|---|---|
|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
| Parameter | Type | Description |
|---|---|---|
|
|
|
| HTTP code | Reponse body |
|---|---|
| 200 - OK |
|
| 201 - Created |
|
| 202 - Accepted |
|
| 401 - Unauthorized | Empty |