Skip to content

Commit

Permalink
Update API model
Browse files Browse the repository at this point in the history
  • Loading branch information
aws-sdk-cpp-automation committed Dec 9, 2024
1 parent a9910a0 commit 881ca7b
Show file tree
Hide file tree
Showing 7 changed files with 980 additions and 730 deletions.
2 changes: 1 addition & 1 deletion tools/code-generation/smithy/api-descriptions/appsync.json
Original file line number Diff line number Diff line change
Expand Up @@ -3545,7 +3545,7 @@
"type": {
"target": "com.amazonaws.appsync#DataSourceType",
"traits": {
"smithy.api#documentation": "<p>The type of the data source.</p>\n <ul>\n <li>\n <p>\n <b>AWS_LAMBDA</b>: The data source is an Lambda function.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_DYNAMODB</b>: The data source is an Amazon DynamoDB table.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_ELASTICSEARCH</b>: The data source is an\n Amazon OpenSearch Service domain.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_OPENSEARCH_SERVICE</b>: The data source is\n an Amazon OpenSearch Service domain.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_EVENTBRIDGE</b>: The data source is an\n Amazon EventBridge configuration.</p>\n </li>\n <li>\n <p>\n <b>NONE</b>: There is no data source. Use this type\n when you want to invoke a GraphQL operation without connecting to a data source, such\n as when you're performing data transformation with resolvers or invoking a\n subscription from a mutation.</p>\n </li>\n <li>\n <p>\n <b>HTTP</b>: The data source is an HTTP\n endpoint.</p>\n </li>\n <li>\n <p>\n <b>RELATIONAL_DATABASE</b>: The data source is a\n relational database.</p>\n </li>\n </ul>"
"smithy.api#documentation": "<p>The type of the data source.</p>\n <ul>\n <li>\n <p>\n <b>AWS_LAMBDA</b>: The data source is an Lambda function.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_DYNAMODB</b>: The data source is an Amazon DynamoDB table.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_ELASTICSEARCH</b>: The data source is an\n Amazon OpenSearch Service domain.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_OPENSEARCH_SERVICE</b>: The data source is\n an Amazon OpenSearch Service domain.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_EVENTBRIDGE</b>: The data source is an\n Amazon EventBridge configuration.</p>\n </li>\n <li>\n <p>\n <b>AMAZON_BEDROCK_RUNTIME</b>: The data source is the Amazon Bedrock runtime.</p>\n </li>\n <li>\n <p>\n <b>NONE</b>: There is no data source. Use this type\n when you want to invoke a GraphQL operation without connecting to a data source, such\n as when you're performing data transformation with resolvers or invoking a\n subscription from a mutation.</p>\n </li>\n <li>\n <p>\n <b>HTTP</b>: The data source is an HTTP\n endpoint.</p>\n </li>\n <li>\n <p>\n <b>RELATIONAL_DATABASE</b>: The data source is a\n relational database.</p>\n </li>\n </ul>"
}
},
"serviceRoleArn": {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16268,8 +16268,7 @@
"CustomDomainConfig": {
"target": "com.amazonaws.cognitoidentityprovider#CustomDomainConfigType",
"traits": {
"smithy.api#documentation": "<p>The configuration for a custom domain that hosts the sign-up and sign-in pages for\n your application. Use this object to specify an SSL certificate that is managed by\n ACM.</p>\n <p>When you create a custom domain, the passkey RP ID defaults to the custom domain. If\n you had a prefix domain active, this will cause passkey integration for your prefix\n domain to stop working due to a mismatch in RP ID. To keep the prefix domain passkey\n integration working, you can explicitly set RP ID to the prefix domain. Update the RP ID\n in a <a href=\"https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_SetUserPoolMfaConfig.html\">SetUserPoolMfaConfig</a> request.</p>",
"smithy.api#required": {}
"smithy.api#documentation": "<p>The configuration for a custom domain that hosts the sign-up and sign-in pages for\n your application. Use this object to specify an SSL certificate that is managed by\n ACM.</p>\n <p>When you create a custom domain, the passkey RP ID defaults to the custom domain. If\n you had a prefix domain active, this will cause passkey integration for your prefix\n domain to stop working due to a mismatch in RP ID. To keep the prefix domain passkey\n integration working, you can explicitly set RP ID to the prefix domain. Update the RP ID\n in a <a href=\"https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_SetUserPoolMfaConfig.html\">SetUserPoolMfaConfig</a> request.</p>"
}
}
},
Expand Down
228 changes: 224 additions & 4 deletions tools/code-generation/smithy/api-descriptions/ec2.json

Large diffs are not rendered by default.

Loading

0 comments on commit 881ca7b

Please sign in to comment.