Skip to content

Commit

Permalink
chore: bump models. (#1403)
Browse files Browse the repository at this point in the history 
Co-authored-by: Sichan Yoo <[email protected]>
  • Loading branch information
@sichanyoo
sichanyoo and Sichan Yoo authored Mar 12, 2024
1 parent d21fc1f commit b301970
Show file tree
Hide file tree
Showing 39 changed files with 3,647 additions and 1,247 deletions.
16 changes: 8 additions & 8 deletions codegen/sdk-codegen/aws-models/accessanalyzer.2019-11-01.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
"actions": {
"target": "com.amazonaws.accessanalyzer#ActionsList",
"traits": {
"smithy.api#documentation": "<p>A list of actions for the access permissions.</p>",
"smithy.api#documentation": "<p>A list of actions for the access permissions. Any strings that can be used as an action\n in an IAM policy can be used in the list of actions to check.</p>",
"smithy.api#length": {
"max": 100
},
Expand Down Expand Up @@ -2529,7 +2529,7 @@
"type": {
"target": "com.amazonaws.accessanalyzer#Type",
"traits": {
"smithy.api#documentation": "<p>The type of analyzer to create. Only <code>ACCOUNT</code>, <code>ORGANIZATION</code>,\n <code>ACCOUNT_UNUSED_ACCESS</code>, and <code>ORGANIZTAION_UNUSED_ACCESS</code>\n analyzers are supported. You can create only one analyzer per account per Region. You can\n create up to 5 analyzers per organization per Region.</p>",
"smithy.api#documentation": "<p>The type of analyzer to create. Only <code>ACCOUNT</code>, <code>ORGANIZATION</code>,\n <code>ACCOUNT_UNUSED_ACCESS</code>, and <code>ORGANIZATION_UNUSED_ACCESS</code>\n analyzers are supported. You can create only one analyzer per account per Region. You can\n create up to 5 analyzers per organization per Region.</p>",
"smithy.api#required": {}
}
},
Expand Down Expand Up @@ -3807,7 +3807,7 @@
}
],
"traits": {
"smithy.api#documentation": "<p>Retrieves information about the specified finding.</p>",
"smithy.api#documentation": "<p>Retrieves information about the specified finding. GetFinding and GetFindingV2 both use\n <code>access-analyzer:GetFinding</code> in the <code>Action</code> element of an IAM\n policy statement. You must have permission to perform the\n <code>access-analyzer:GetFinding</code> action.</p>",
"smithy.api#http": {
"uri": "/finding/{id}",
"method": "GET",
Expand Down Expand Up @@ -3880,7 +3880,7 @@
}
],
"traits": {
"smithy.api#documentation": "<p>Retrieves information about the specified finding.</p>",
"smithy.api#documentation": "<p>Retrieves information about the specified finding. GetFinding and GetFindingV2 both use\n <code>access-analyzer:GetFinding</code> in the <code>Action</code> element of an IAM\n policy statement. You must have permission to perform the\n <code>access-analyzer:GetFinding</code> action.</p>",
"smithy.api#http": {
"uri": "/findingv2/{id}",
"method": "GET",
Expand Down Expand Up @@ -4704,7 +4704,7 @@
}
],
"traits": {
"smithy.api#documentation": "<p>Retrieves a list of resources of the specified type that have been analyzed by the\n specified analyzer..</p>",
"smithy.api#documentation": "<p>Retrieves a list of resources of the specified type that have been analyzed by the\n specified external access analyzer. This action is not supported for unused access\n analyzers.</p>",
"smithy.api#http": {
"uri": "/analyzed-resource",
"method": "POST",
Expand Down Expand Up @@ -4970,7 +4970,7 @@
}
],
"traits": {
"smithy.api#documentation": "<p>Retrieves a list of findings generated by the specified analyzer.</p>\n <p>To learn about filter keys that you can use to retrieve a list of findings, see <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-reference-filter-keys.html\">IAM Access Analyzer filter keys</a> in the <b>IAM User Guide</b>.</p>",
"smithy.api#documentation": "<p>Retrieves a list of findings generated by the specified analyzer. ListFindings and\n ListFindingsV2 both use <code>access-analyzer:ListFindings</code> in the\n <code>Action</code> element of an IAM policy statement. You must have permission to\n perform the <code>access-analyzer:ListFindings</code> action.</p>\n <p>To learn about filter keys that you can use to retrieve a list of findings, see <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-reference-filter-keys.html\">IAM Access Analyzer filter keys</a> in the <b>IAM User Guide</b>.</p>",
"smithy.api#http": {
"uri": "/finding",
"method": "POST",
Expand Down Expand Up @@ -5071,7 +5071,7 @@
}
],
"traits": {
"smithy.api#documentation": "<p>Retrieves a list of findings generated by the specified analyzer.</p>\n <p>To learn about filter keys that you can use to retrieve a list of findings, see <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-reference-filter-keys.html\">IAM Access Analyzer filter keys</a> in the <b>IAM User Guide</b>.</p>",
"smithy.api#documentation": "<p>Retrieves a list of findings generated by the specified analyzer. ListFindings and\n ListFindingsV2 both use <code>access-analyzer:ListFindings</code> in the\n <code>Action</code> element of an IAM policy statement. You must have permission to\n perform the <code>access-analyzer:ListFindings</code> action.</p>\n <p>To learn about filter keys that you can use to retrieve a list of findings, see <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-reference-filter-keys.html\">IAM Access Analyzer filter keys</a> in the <b>IAM User Guide</b>.</p>",
"smithy.api#http": {
"uri": "/findingv2",
"method": "POST",
Expand Down Expand Up @@ -5970,7 +5970,7 @@
}
},
"traits": {
"smithy.api#documentation": "<p>Proposed access control configuration for an Amazon S3 directory bucket. You can propose a\n configuration for a new Amazon S3 directory bucket or an existing Amazon S3 directory bucket that you\n own by specifying the Amazon S3 bucket policy. If the configuration is for an existing Amazon S3\n directory bucket and you do not specify the Amazon S3 bucket policy, the access preview uses the\n existing policy attached to the directory bucket. If the access preview is for a new\n resource and you do not specify the Amazon S3 bucket policy, the access preview assumes an\n directory bucket without a policy. To propose deletion of an existing bucket policy, you\n can specify an empty string. For more information about bucket policy limits, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-example-bucket-policies.html\">Example bucket policies</a>.</p>"
"smithy.api#documentation": "<p>Proposed access control configuration for an Amazon S3 directory bucket. You can propose a\n configuration for a new Amazon S3 directory bucket or an existing Amazon S3 directory bucket that you\n own by specifying the Amazon S3 bucket policy. If the configuration is for an existing Amazon S3\n directory bucket and you do not specify the Amazon S3 bucket policy, the access preview uses the\n existing policy attached to the directory bucket. If the access preview is for a new\n resource and you do not specify the Amazon S3 bucket policy, the access preview assumes an\n directory bucket without a policy. To propose deletion of an existing bucket policy, you\n can specify an empty string. For more information about Amazon S3 directory bucket policies, see\n <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-example-bucket-policies.html\">Example directory bucket policies for S3 Express One Zone</a>.</p>"
}
},
"com.amazonaws.accessanalyzer#S3ExpressDirectoryBucketPolicy": {
Expand Down
2 changes: 1 addition & 1 deletion codegen/sdk-codegen/aws-models/api-gateway.2015-07-09.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9144,7 +9144,7 @@
"target": "com.amazonaws.apigateway#Boolean",
"traits": {
"smithy.api#default": false,
"smithy.api#documentation": "<p>Specifies whether data trace logging is enabled for this method, which affects the log entries pushed to Amazon CloudWatch Logs.</p>"
"smithy.api#documentation": "<p>Specifies whether data trace logging is enabled for this method, which affects the log entries pushed to Amazon CloudWatch Logs. This can be useful to troubleshoot APIs, but can result in logging sensitive data. We recommend that you don't enable this option for production APIs.</p>"
}
},
"throttlingBurstLimit": {
Expand Down
Loading

0 comments on commit b301970

Please sign in to comment.