Obtaining Image Sharing Policies
Function
Obtain image sharing policies.
Constraints
N/A
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:listRepoShares
List
repo *
-
-
-
URI
GET /v2/manage/namespaces/{namespace}/repos/{repository}/shares
| 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. |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| share_type | No | String | Sharing type. |
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 an IAM API. The value of X-Subject-Token in the response header is the user token. |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| [items] | Array of ShowRepoSharesResponse objects | Image sharing rules. |
| Parameter | Type | Description |
|---|---|---|
| id | String | ID |
| namespace | String | Organization. |
| repository | String | Image repository. |
| share_type | String | Sharing type. The value can be account or organization. |
| share_principals | Array of strings | Information about the principals the image will be shared with. |
| permission | String | Permission. |
| deadline | String | Expiration time. |
| description | String | Description. |
| creator_id | String | Creator ID. |
| creator_name | String | Creator name. |
| created | String | Time when the image was created, in Coordinated Universal time (UTC). You need to calculate the offset based on local time. For example, GMT+8 is 8 hours ahead of UTC. |
| updated | String | Time when the image was updated, in Coordinated Universal time (UTC). You need to calculate the offset based on local time. For example, GMT+8 is 8 hours ahead of UTC. |
| status | Boolean | Sharing status. true indicates valid. false indicates expired. |
Example Requests
GET https://{endpoint}/v2/manage/namespaces/{namespace}/repos/{repository}/shares Example Responses
Status code: 200
[ {
"id" : "1",
"namespace" : "nsname",
"repository" : "paas",
"share_type" : "account",
"share_principals" : [ "fb3f175c1fd146ab8cdae3272be6107b" ],
"permission" : "read",
"deadline" : "2018-10-01T16:00:00.000Z",
"description" : "description",
"creator_id" : "fb3f175c1fd146ab8cdae3272be6107b",
"creator_name" : "creator",
"created" : "2017-04-08T14:12:23Z",
"updated" : "2017-04-13T21:01:11Z",
"status" : false
} ] Status Codes
| Status Code | Description |
|---|---|
| 200 | Obtained. |
| 400 | Bad request. |
| 401 | Unauthorized. |
| 500 | Internal error. |
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