Skip to content

Commit

Permalink
Update API model
Browse files Browse the repository at this point in the history
  • Loading branch information
AWS SDK for Go v2 automation user committed Mar 20, 2024
1 parent 91a5e15 commit 635970a
Show file tree
Hide file tree
Showing 6 changed files with 576 additions and 137 deletions.
60 changes: 59 additions & 1 deletion codegen/sdk-codegen/aws-models/accessanalyzer.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2351,6 +2351,18 @@
"traits": {
"smithy.api#documentation": "<p>The access control configuration is for an Amazon S3 directory bucket.</p>"
}
},
"dynamodbStream": {
"target": "com.amazonaws.accessanalyzer#DynamodbStreamConfiguration",
"traits": {
"smithy.api#documentation": "<p>The access control configuration is for a DynamoDB stream.</p>"
}
},
"dynamodbTable": {
"target": "com.amazonaws.accessanalyzer#DynamodbTableConfiguration",
"traits": {
"smithy.api#documentation": "<p>The access control configuration is for a DynamoDB table or index.</p>"
}
}
},
"traits": {
Expand Down Expand Up @@ -2529,7 +2541,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>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#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 @@ -2813,6 +2825,40 @@
"smithy.api#documentation": "<p>Deletes an archive rule.</p>"
}
},
"com.amazonaws.accessanalyzer#DynamodbStreamConfiguration": {
"type": "structure",
"members": {
"streamPolicy": {
"target": "com.amazonaws.accessanalyzer#DynamodbStreamPolicy",
"traits": {
"smithy.api#documentation": "<p>The proposed resource policy defining who can access or manage the DynamoDB stream.</p>"
}
}
},
"traits": {
"smithy.api#documentation": "<p>The proposed access control configuration for a DynamoDB stream. You can propose a\n configuration for a new DynamoDB stream or an existing DynamoDB stream that you own by specifying\n the policy for the DynamoDB stream. For more information, see <a href=\"https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutResourcePolicy.html\">PutResourcePolicy</a>.</p>\n <ul>\n <li>\n <p>If the configuration is for an existing DynamoDB stream and you do not specify the\n DynamoDB policy, then the access preview uses the existing DynamoDB policy for the\n stream.</p>\n </li>\n <li>\n <p>If the access preview is for a new resource and you do not specify the policy,\n then the access preview assumes a DynamoDB stream without a policy.</p>\n </li>\n <li>\n <p>To propose deletion of an existing DynamoDB stream policy, you can specify an empty\n string for the DynamoDB policy.</p>\n </li>\n </ul>"
}
},
"com.amazonaws.accessanalyzer#DynamodbStreamPolicy": {
"type": "string"
},
"com.amazonaws.accessanalyzer#DynamodbTableConfiguration": {
"type": "structure",
"members": {
"tablePolicy": {
"target": "com.amazonaws.accessanalyzer#DynamodbTablePolicy",
"traits": {
"smithy.api#documentation": "<p>The proposed resource policy defining who can access or manage the DynamoDB table.</p>"
}
}
},
"traits": {
"smithy.api#documentation": "<p>The proposed access control configuration for a DynamoDB table or index. You can propose a\n configuration for a new DynamoDB table or index or an existing DynamoDB table or index that you\n own by specifying the policy for the DynamoDB table or index. For more information, see <a href=\"https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_PutResourcePolicy.html\">PutResourcePolicy</a>.</p>\n <ul>\n <li>\n <p>If the configuration is for an existing DynamoDB table or index and you do not\n specify the DynamoDB policy, then the access preview uses the existing DynamoDB policy for\n the table or index.</p>\n </li>\n <li>\n <p>If the access preview is for a new resource and you do not specify the policy,\n then the access preview assumes a DynamoDB table without a policy.</p>\n </li>\n <li>\n <p>To propose deletion of an existing DynamoDB table or index policy, you can specify an\n empty string for the DynamoDB policy.</p>\n </li>\n </ul>"
}
},
"com.amazonaws.accessanalyzer#DynamodbTablePolicy": {
"type": "string"
},
"com.amazonaws.accessanalyzer#EbsGroup": {
"type": "string"
},
Expand Down Expand Up @@ -5848,6 +5894,14 @@
{
"value": "AWS::S3Express::DirectoryBucket",
"name": "AWS_S3EXPRESS_DIRECTORYBUCKET"
},
{
"value": "AWS::DynamoDB::Table",
"name": "AWS_DYNAMODB_TABLE"
},
{
"value": "AWS::DynamoDB::Stream",
"name": "AWS_DYNAMODB_STREAM"
}
]
}
Expand Down Expand Up @@ -7044,6 +7098,10 @@
{
"value": "AWS::IAM::AssumeRolePolicyDocument",
"name": "ROLE_TRUST"
},
{
"value": "AWS::DynamoDB::Table",
"name": "DYNAMODB_TABLE"
}
]
}
Expand Down
2 changes: 1 addition & 1 deletion codegen/sdk-codegen/aws-models/codebuild.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8908,7 +8908,7 @@
"type": {
"target": "com.amazonaws.codebuild#WebhookFilterType",
"traits": {
"smithy.api#documentation": "<p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>,\n <code>ACTOR_ACCOUNT_ID</code>, <code>HEAD_REF</code>, <code>BASE_REF</code>,\n <code>FILE_PATH</code>, and <code>COMMIT_MESSAGE</code>. </p>\n <ul>\n <li>\n <p>\n EVENT\n </p>\n <ul>\n <li>\n <p> A webhook event triggers a build when the provided <code>pattern</code>\n matches one of six event types: <code>PUSH</code>,\n <code>PULL_REQUEST_CREATED</code>, <code>PULL_REQUEST_UPDATED</code>, \n <code>PULL_REQUEST_CLOSED</code>, \n <code>PULL_REQUEST_REOPENED</code>, and\n <code>PULL_REQUEST_MERGED</code>. The <code>EVENT</code> patterns are\n specified as a comma-separated string. For example, <code>PUSH,\n PULL_REQUEST_CREATED, PULL_REQUEST_UPDATED</code> filters all push, pull\n request created, and pull request updated events. </p>\n <note>\n <p> The <code>PULL_REQUEST_REOPENED</code> works with GitHub and GitHub\n Enterprise only. </p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>ACTOR_ACCOUNT_ID</p>\n <ul>\n <li>\n <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or\n Bitbucket account ID matches the regular expression <code>pattern</code>.\n </p>\n </li>\n </ul>\n </li>\n <li>\n <p>HEAD_REF</p>\n <ul>\n <li>\n <p> A webhook event triggers a build when the head reference matches the\n regular expression <code>pattern</code>. For example,\n <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p>\n <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub\n Enterprise pull request, Bitbucket push, and Bitbucket pull request events.\n </p>\n </li>\n </ul>\n </li>\n <li>\n <p>BASE_REF</p>\n <ul>\n <li>\n <p> A webhook event triggers a build when the base reference matches the\n regular expression <code>pattern</code>. For example,\n <code>refs/heads/branch-name</code>. </p>\n <note>\n <p> Works with pull request events only. </p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>FILE_PATH</p>\n <ul>\n <li>\n <p> A webhook triggers a build when the path of a changed file matches the\n regular expression <code>pattern</code>. </p>\n <note>\n <p> Works with GitHub and Bitbucket events push and pull requests events.\n Also works with GitHub Enterprise push events, but does not work with\n GitHub Enterprise pull request events. </p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>COMMIT_MESSAGE</p>\n <ul>\n <li>\n <p>A webhook triggers a build when the head commit message matches the\n regular expression <code>pattern</code>.</p>\n <note>\n <p> Works with GitHub and Bitbucket events push and pull requests events.\n Also works with GitHub Enterprise push events, but does not work with\n GitHub Enterprise pull request events. </p>\n </note>\n </li>\n </ul>\n </li>\n </ul>",
"smithy.api#documentation": "<p> The type of webhook filter. There are eight webhook filter types: <code>EVENT</code>,\n <code>ACTOR_ACCOUNT_ID</code>, <code>HEAD_REF</code>, <code>BASE_REF</code>,\n <code>FILE_PATH</code>, <code>COMMIT_MESSAGE</code>, <code>TAG_NAME</code>, and <code>RELEASE_NAME</code>. </p>\n <ul>\n <li>\n <p>\n EVENT\n </p>\n <ul>\n <li>\n <p> A webhook event triggers a build when the provided <code>pattern</code>\n matches one of eight event types: <code>PUSH</code>,\n <code>PULL_REQUEST_CREATED</code>, <code>PULL_REQUEST_UPDATED</code>, \n <code>PULL_REQUEST_CLOSED</code>, <code>PULL_REQUEST_REOPENED</code>, \n <code>PULL_REQUEST_MERGED</code>, <code>RELEASED</code>, and <code>PRERELEASED</code>. The <code>EVENT</code> patterns are\n specified as a comma-separated string. For example, <code>PUSH,\n PULL_REQUEST_CREATED, PULL_REQUEST_UPDATED</code> filters all push, pull\n request created, and pull request updated events. </p>\n <note>\n <p> The <code>PULL_REQUEST_REOPENED</code> works with GitHub and GitHub\n Enterprise only. The <code>RELEASED</code> and <code>PRERELEASED</code> work \n with GitHub only.</p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>ACTOR_ACCOUNT_ID</p>\n <ul>\n <li>\n <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or\n Bitbucket account ID matches the regular expression <code>pattern</code>.\n </p>\n </li>\n </ul>\n </li>\n <li>\n <p>HEAD_REF</p>\n <ul>\n <li>\n <p> A webhook event triggers a build when the head reference matches the\n regular expression <code>pattern</code>. For example,\n <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p>\n <note>\n <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub\n Enterprise pull request, Bitbucket push, and Bitbucket pull request events.</p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>BASE_REF</p>\n <ul>\n <li>\n <p> A webhook event triggers a build when the base reference matches the\n regular expression <code>pattern</code>. For example,\n <code>refs/heads/branch-name</code>. </p>\n <note>\n <p> Works with pull request events only. </p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>FILE_PATH</p>\n <ul>\n <li>\n <p> A webhook triggers a build when the path of a changed file matches the\n regular expression <code>pattern</code>. </p>\n <note>\n <p> Works with GitHub and Bitbucket events push and pull requests events.\n Also works with GitHub Enterprise push events, but does not work with\n GitHub Enterprise pull request events. </p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>COMMIT_MESSAGE</p>\n <ul>\n <li>\n <p>A webhook triggers a build when the head commit message matches the\n regular expression <code>pattern</code>.</p>\n <note>\n <p> Works with GitHub and Bitbucket events push and pull requests events.\n Also works with GitHub Enterprise push events, but does not work with\n GitHub Enterprise pull request events. </p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>TAG_NAME</p>\n <ul>\n <li>\n <p>A webhook triggers a build when the tag name of the release matches the \n regular expression <code>pattern</code>.</p>\n <note>\n <p> Works with <code>RELEASED</code> and <code>PRERELEASED</code> events only. </p>\n </note>\n </li>\n </ul>\n </li>\n <li>\n <p>RELEASE_NAME</p>\n <ul>\n <li>\n <p>A webhook triggers a build when the release name matches the \n regular expression <code>pattern</code>.</p>\n <note>\n <p> Works with <code>RELEASED</code> and <code>PRERELEASED</code> events only. </p>\n </note>\n </li>\n </ul>\n </li>\n </ul>",
"smithy.api#required": {}
}
},
Expand Down
Loading

0 comments on commit 635970a

Please sign in to comment.