|
23 | 23 | "DescribeRegistry": "<p>Describes the settings for a registry. The replication configuration for a repository can be created or updated with the <a>PutReplicationConfiguration</a> API action.</p>", |
24 | 24 | "DescribeRepositories": "<p>Describes image repositories in a registry.</p>", |
25 | 25 | "DescribeRepositoryCreationTemplates": "<p>Returns details about the repository creation templates in a registry. The <code>prefixes</code> request parameter can be used to return the details for a specific repository creation template.</p>", |
| 26 | + "GetAccountSetting": "<p>Retrieves the basic scan type version name.</p>", |
26 | 27 | "GetAuthorizationToken": "<p>Retrieves an authorization token. An authorization token represents your IAM authentication credentials and can be used to access any Amazon ECR registry that your IAM principal has access to. The authorization token is valid for 12 hours.</p> <p>The <code>authorizationToken</code> returned is a base64 encoded string that can be decoded and used in a <code>docker login</code> command to authenticate to a registry. The CLI offers an <code>get-login-password</code> command that simplifies the login process. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html#registry_auth\">Registry authentication</a> in the <i>Amazon Elastic Container Registry User Guide</i>.</p>", |
27 | 28 | "GetDownloadUrlForLayer": "<p>Retrieves the pre-signed Amazon S3 download URL corresponding to an image layer. You can only get URLs for image layers that are referenced in an image.</p> <p>When an image is pulled, the GetDownloadUrlForLayer API is called once per image layer that is not already cached.</p> <note> <p>This operation is used by the Amazon ECR proxy and is not generally used by customers for pulling and pushing images. In most cases, you should use the <code>docker</code> CLI to pull, tag, and push images.</p> </note>", |
28 | 29 | "GetLifecyclePolicy": "<p>Retrieves the lifecycle policy for the specified repository.</p>", |
|
33 | 34 | "InitiateLayerUpload": "<p>Notifies Amazon ECR that you intend to upload an image layer.</p> <p>When an image is pushed, the InitiateLayerUpload API is called once per image layer that has not already been uploaded. Whether or not an image layer has been uploaded is determined by the BatchCheckLayerAvailability API action.</p> <note> <p>This operation is used by the Amazon ECR proxy and is not generally used by customers for pulling and pushing images. In most cases, you should use the <code>docker</code> CLI to pull, tag, and push images.</p> </note>", |
34 | 35 | "ListImages": "<p>Lists all the image IDs for the specified repository.</p> <p>You can filter images based on whether or not they are tagged by using the <code>tagStatus</code> filter and specifying either <code>TAGGED</code>, <code>UNTAGGED</code> or <code>ANY</code>. For example, you can filter your results to return only <code>UNTAGGED</code> images and then pipe that result to a <a>BatchDeleteImage</a> operation to delete them. Or, you can filter your results to return only <code>TAGGED</code> images to list all of the tags in your repository.</p>", |
35 | 36 | "ListTagsForResource": "<p>List the tags for an Amazon ECR resource.</p>", |
| 37 | + "PutAccountSetting": "<p>Allows you to change the basic scan type version by setting the <code>name</code> parameter to either <code>CLAIR</code> to <code>AWS_NATIVE</code>.</p>", |
36 | 38 | "PutImage": "<p>Creates or updates the image manifest and tags associated with an image.</p> <p>When an image is pushed and all new image layers have been uploaded, the PutImage API is called once to create or update the image manifest and the tags associated with the image.</p> <note> <p>This operation is used by the Amazon ECR proxy and is not generally used by customers for pulling and pushing images. In most cases, you should use the <code>docker</code> CLI to pull, tag, and push images.</p> </note>", |
37 | 39 | "PutImageScanningConfiguration": "<important> <p>The <code>PutImageScanningConfiguration</code> API is being deprecated, in favor of specifying the image scanning configuration at the registry level. For more information, see <a>PutRegistryScanningConfiguration</a>.</p> </important> <p>Updates the image scanning configuration for the specified repository.</p>", |
38 | 40 | "PutImageTagMutability": "<p>Updates the image tag mutability settings for the specified repository. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-tag-mutability.html\">Image tag mutability</a> in the <i>Amazon Elastic Container Registry User Guide</i>.</p>", |
|
51 | 53 | "ValidatePullThroughCacheRule": "<p>Validates an existing pull through cache rule for an upstream registry that requires authentication. This will retrieve the contents of the Amazon Web Services Secrets Manager secret, verify the syntax, and then validate that authentication to the upstream registry is successful.</p>" |
52 | 54 | }, |
53 | 55 | "shapes": { |
| 56 | + "AccountSettingName": { |
| 57 | + "base": null, |
| 58 | + "refs": { |
| 59 | + "GetAccountSettingRequest$name": "<p>Basic scan type version name. </p>", |
| 60 | + "GetAccountSettingResponse$name": "<p>Retrieves the basic scan type version name.</p>", |
| 61 | + "GetAccountSettingResponse$value": "<p>Retrieves the value that specifies what basic scan type is being used: <code>AWS_NATIVE</code> or <code>CLAIR</code>.</p>", |
| 62 | + "PutAccountSettingRequest$name": "<p>Basic scan type version name. </p>", |
| 63 | + "PutAccountSettingResponse$name": "<p>Retrieves the the basic scan type version name.</p>" |
| 64 | + } |
| 65 | + }, |
| 66 | + "AccountSettingValue": { |
| 67 | + "base": null, |
| 68 | + "refs": { |
| 69 | + "PutAccountSettingRequest$value": "<p>Setting value that determines what basic scan type is being used: <code>AWS_NATIVE</code> or <code>CLAIR</code>.</p>", |
| 70 | + "PutAccountSettingResponse$value": "<p>Retrieves the basic scan type value, either <code>AWS_NATIVE</code> or <code>-</code>.</p>" |
| 71 | + } |
| 72 | + }, |
54 | 73 | "Arch": { |
55 | 74 | "base": null, |
56 | 75 | "refs": { |
|
245 | 264 | "CustomRoleArn": { |
246 | 265 | "base": null, |
247 | 266 | "refs": { |
248 | | - "CreateRepositoryCreationTemplateRequest$customRoleArn": "<p>The ARN of the role to be assumed by Amazon ECR. This role must be in the same account as the registry that you are configuring.</p>", |
249 | | - "RepositoryCreationTemplate$customRoleArn": "<p>The ARN of the role to be assumed by Amazon ECR.</p>", |
250 | | - "UpdateRepositoryCreationTemplateRequest$customRoleArn": "<p>The ARN of the role to be assumed by Amazon ECR. This role must be in the same account as the registry that you are configuring.</p>" |
| 267 | + "CreateRepositoryCreationTemplateRequest$customRoleArn": "<p>The ARN of the role to be assumed by Amazon ECR. This role must be in the same account as the registry that you are configuring. Amazon ECR will assume your supplied role when the customRoleArn is specified. When this field isn't specified, Amazon ECR will use the service-linked role for the repository creation template.</p>", |
| 268 | + "RepositoryCreationTemplate$customRoleArn": "<p>The ARN of the role to be assumed by Amazon ECR. Amazon ECR will assume your supplied role when the customRoleArn is specified. When this field isn't specified, Amazon ECR will use the service-linked role for the repository creation template.</p>", |
| 269 | + "UpdateRepositoryCreationTemplateRequest$customRoleArn": "<p>The ARN of the role to be assumed by Amazon ECR. This role must be in the same account as the registry that you are configuring. Amazon ECR will assume your supplied role when the customRoleArn is specified. When this field isn't specified, Amazon ECR will use the service-linked role for the repository creation template.</p>" |
251 | 270 | } |
252 | 271 | }, |
253 | 272 | "CvssScore": { |
|
578 | 597 | "SetRepositoryPolicyRequest$force": "<p>If the policy you are attempting to set on a repository policy would prevent you from setting another policy in the future, you must force the <a>SetRepositoryPolicy</a> operation. This is intended to prevent accidental repository lock outs.</p>" |
579 | 598 | } |
580 | 599 | }, |
| 600 | + "GetAccountSettingRequest": { |
| 601 | + "base": null, |
| 602 | + "refs": { |
| 603 | + } |
| 604 | + }, |
| 605 | + "GetAccountSettingResponse": { |
| 606 | + "base": null, |
| 607 | + "refs": { |
| 608 | + } |
| 609 | + }, |
581 | 610 | "GetAuthorizationTokenRegistryIdList": { |
582 | 611 | "base": null, |
583 | 612 | "refs": { |
|
1294 | 1323 | "LifecyclePolicyPreviewResult$imagePushedAt": "<p>The date and time, expressed in standard JavaScript date format, at which the current image was pushed to the repository.</p>" |
1295 | 1324 | } |
1296 | 1325 | }, |
| 1326 | + "PutAccountSettingRequest": { |
| 1327 | + "base": null, |
| 1328 | + "refs": { |
| 1329 | + } |
| 1330 | + }, |
| 1331 | + "PutAccountSettingResponse": { |
| 1332 | + "base": null, |
| 1333 | + "refs": { |
| 1334 | + } |
| 1335 | + }, |
1297 | 1336 | "PutImageRequest": { |
1298 | 1337 | "base": null, |
1299 | 1338 | "refs": { |
|
0 commit comments