Checking Whether an Image Has Been Shared with an Account
Function
This API is used to check the existence of an shared tenant.
Constraints
None
Calling Method
For details, see Calling APIs.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
- If you are using identity policy-based authorization, the following identity policy-based permissions are required.
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependencies
swr:repo:getRepoDomain
Read
repo *
-
-
-
URI
GET /v2/manage/namespaces/{namespace}/repositories/{repository}/access-domains/{access_domain}
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| namespace | Yes | String | Organization name. Enter 1 to 64 characters, starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, periods (.), underscores (_), and hyphens (-) are allowed. Periods, underscores, and hyphens cannot be placed next to each other. A maximum of two consecutive underscores are allowed. |
| repository | Yes | String | Image repository name. The name contains 1 to 128 characters, starting and ending with a lowercase letter or digit. Only lowercase letters, digits, periods (.), slashes (/), underscores (_), and hyphens (-) are allowed. Periods, slashes, underscores, and hyphens cannot be placed next to each other. A maximum of two consecutive underscores are allowed. If the parameter value contains a slash (/), replace it with a dollar sign ($) before sending the request. |
| access_domain | Yes | String | Name of the account that an image is shared with. |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| Content-Type | Yes | String | Message body type (format). Possible values: application/json;charset=utf-8 application/json |
| X-Auth-Token | Yes | String | User token. It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| exist | Boolean | true: exist; false: not exist. |
| namespace | String | Organization name |
| repository | String | Image repository name |
| access_domain | String | Name of the account that an image is shared with. |
| permit | String | Permission |
| deadline | String | Deadline |
| description | String | Description |
| creator_id | String | Creator ID |
| creator_name | String | Creator username |
| created | String | Time when an image is created. It is the UTC standard time. |
| updated | String | Time when an image is updated. It is the UTC standard time. |
| status | Boolean | Status. true: valid; false: expired |
Example Requests
GET https://{endpoint}/v2/manage/namespaces/{namespace}/repositories/{repository}/access-domains/{access_domain} Example Responses
Status code: 200
{
"exist" : true,
"namespace" : "group",
"repository" : "busybox",
"access_domain" : "xxx",
"permit" : "read",
"deadline" : "2021-10-01T16:00:00Z",
"description" : "description",
"creator_id" : "0504186e6a8010e01f3ec009a7279baa",
"creator_name" : "xxx",
"created" : "2021-06-10T08:14:42.56632Z",
"updated" : "2021-06-10T08:14:42.566325Z",
"status" : true
} Status Codes
| Status Code | Description |
|---|---|
| 200 | The query succeeded. |
| 400 | An request error occurred. |
| 401 | The authentication failed. |
| 500 | An internal error occurred. |
Error Codes
See Error Codes.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot