Skip to content

Commit

Permalink
Merge branch 'v1-main' into bump-cfnspec-v1-main/v102.0.0
Browse files Browse the repository at this point in the history
  • Loading branch information
@mergify
mergify[bot] authored Dec 16, 2022
2 parents 4917bec + ac63316 commit 08a1e44
Showing 1 changed file with 11 additions and 11 deletions.
22 changes: 11 additions & 11 deletions packages/@aws-cdk/cfnspec/spec-source/cfn-docs/cfn-docs.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4175,7 +4175,7 @@
"attributes": {},
"description": "An object that represents the specification of a virtual router.",
"properties": {
"Listeners": "The listeners that the virtual router is expected to receive inbound traffic from. You can specify one listener."
"Listeners": "The listeners that the virtual router is expected to receive inbound traffic from."
}
},
"AWS::AppMesh::VirtualService": {
Expand Down Expand Up @@ -7184,7 +7184,7 @@
"ResourceTags": "",
"Subscribers": "A list of subscribers to notify.",
"SubscriptionName": "The name for the subscription.",
"Threshold": "The dollar value that triggers a notification if the threshold is exceeded."
"Threshold": "(deprecated)\n\nThe dollar value that triggers a notification if the threshold is exceeded.\n\nThis field has been deprecated. To specify a threshold, use ThresholdExpression. Continued use of Threshold will be treated as shorthand syntax for a ThresholdExpression.\n\nOne of Threshold or ThresholdExpression is required for this resource."
}
},
"AWS::CE::AnomalySubscription.ResourceTag": {
Expand Down Expand Up @@ -10051,7 +10051,7 @@
"attributes": {},
"description": "The settings for updates to user attributes. These settings include the property `AttributesRequireVerificationBeforeUpdate` ,\na user-pool setting that tells Amazon Cognito how to handle changes to the value of your users' email address and phone number attributes. For\nmore information, see [Verifying updates to email addresses and phone numbers](https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-email-phone-verification.html#user-pool-settings-verifications-verify-attribute-updates) .",
"properties": {
"AttributesRequireVerificationBeforeUpdate": "Requires that your user verifies their email address, phone number, or both before Amazon Cognito updates the value of that attribute. When you update a user attribute that has this option activated, Amazon Cognito sends a verification message to the new phone number or email address. Amazon Cognito doesn\u2019t change the value of the attribute until your user responds to the verification message and confirms the new value.\n\nYou can verify an updated email address or phone number with a [VerifyUserAttribute](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_VerifyUserAttribute.html) API request. You can also call the [UpdateUserAttributes](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_UpdateUserAttributes.html) or [AdminUpdateUserAttributes](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_AdminUpdateUserAttributes.html) API and set `email_verified` or `phone_number_verified` to true.\n\nWhen `AttributesRequireVerificationBeforeUpdate` is false, your user pool doesn't require that your users verify attribute changes before Amazon Cognito updates them. In a user pool where `AttributesRequireVerificationBeforeUpdate` is false, API operations that change attribute values can immediately update a user\u2019s `email` or `phone_number` attribute."
"AttributesRequireVerificationBeforeUpdate": "Requires that your user verifies their email address, phone number, or both before Amazon Cognito updates the value of that attribute. When you update a user attribute that has this option activated, Amazon Cognito sends a verification message to the new phone number or email address. Amazon Cognito doesn\u2019t change the value of the attribute until your user responds to the verification message and confirms the new value.\n\nYou can verify an updated email address or phone number with a [VerifyUserAttribute](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_VerifyUserAttribute.html) API request. You can also call the [AdminUpdateUserAttributes](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_AdminUpdateUserAttributes.html) API and set `email_verified` or `phone_number_verified` to true.\n\nWhen `AttributesRequireVerificationBeforeUpdate` is false, your user pool doesn't require that your users verify attribute changes before Amazon Cognito updates them. In a user pool where `AttributesRequireVerificationBeforeUpdate` is false, API operations that change attribute values can immediately update a user\u2019s `email` or `phone_number` attribute."
}
},
"AWS::Cognito::UserPool.UserPoolAddOns": {
Expand All @@ -10065,7 +10065,7 @@
"attributes": {},
"description": "The `UsernameConfiguration` property type specifies case sensitivity on the username input for the selected sign-in option.",
"properties": {
"CaseSensitive": "Specifies whether user name case sensitivity will be applied for all users in the user pool through Amazon Cognito APIs.\n\nValid values include:\n\n- **True** - Enables case sensitivity for all username input. When this option is set to `True` , users must sign in using the exact capitalization of their given username, such as \u201cUserName\u201d. This is the default value.\n- **False** - Enables case insensitivity for all username input. For example, when this option is set to `False` , users can sign in using either \"username\" or \"Username\". This option also enables both `preferred_username` and `email` alias to be case insensitive, in addition to the `username` attribute."
"CaseSensitive": "Specifies whether user name case sensitivity will be applied for all users in the user pool through Amazon Cognito APIs. For most use cases, set case sensitivity to `False` (case insensitive) as a best practice. When usernames and email addresses are case insensitive, Amazon Cognito marks otherwise-identical attribute values with a capitalization difference as duplicates and in conflict.\n\nValid values include:\n\n- **True** - Enables case sensitivity for all username input. When this option is set to `True` , users must sign in using the exact capitalization of their given username, such as \u201cUserName\u201d. This is the default value.\n- **False** - Enables case insensitivity for all username input. For example, when this option is set to `False` , users can sign in using `username` , `USERNAME` , or `UserName` . This option also enables both `preferred_username` and `email` alias to be case insensitive, in addition to the `username` attribute."
}
},
"AWS::Cognito::UserPool.VerificationMessageTemplate": {
Expand Down Expand Up @@ -19019,7 +19019,7 @@
"SessionCookieName": "The name of the cookie used to maintain session information. The default is AWSELBAuthSessionCookie.",
"SessionTimeout": "The maximum duration of the authentication session, in seconds. The default is 604800 seconds (7 days).",
"TokenEndpoint": "The token endpoint of the IdP. This must be a full URL, including the HTTPS protocol, the domain, and the path.",
"UseExistingClientSecret": "",
"UseExistingClientSecret": "Indicates whether to use the existing client secret when modifying a rule. If you are creating a rule, you can omit this parameter or set it to false.",
"UserInfoEndpoint": "The user info endpoint of the IdP. This must be a full URL, including the HTTPS protocol, the domain, and the path."
}
},
Expand Down Expand Up @@ -20416,7 +20416,7 @@
"Ref": "",
"ResourceARN": ""
},
"description": "The configuration of a data repository association that links an Amazon FSx for Lustre file system to an Amazon S3 bucket or an Amazon File Cache resource to an Amazon S3 bucket or an NFS file system. The data repository association configuration object is returned in the response of the following operations:\n\n- `CreateDataRepositoryAssociation`\n- `UpdateDataRepositoryAssociation`\n- `DescribeDataRepositoryAssociations`\n\nData repository associations are supported only for an Amazon FSx for Lustre file system with the `Persistent_2` deployment type and for an Amazon File Cache resource.",
"description": "Creates an Amazon FSx for Lustre data repository association (DRA). A data repository association is a link between a directory on the file system and an Amazon S3 bucket or prefix. You can have a maximum of 8 data repository associations on a file system. Data repository associations are supported only for file systems with the `Persistent_2` deployment type.\n\nEach data repository association must have a unique Amazon FSx file system directory and a unique S3 bucket or prefix associated with it. You can configure a data repository association for automatic import only, for automatic export only, or for both. To learn more about linking a data repository to your file system, see [Linking your file system to an S3 bucket](https://docs.aws.amazon.com/fsx/latest/LustreGuide/create-dra-linked-data-repo.html) .\n\n> `CreateDataRepositoryAssociation` isn't supported on Amazon File Cache resources. To create a DRA on Amazon File Cache, use the `CreateFileCache` operation.",
"properties": {
"BatchImportMetaDataOnCreate": "A boolean flag indicating whether an import data repository task to import metadata should run after the data repository association is created. The task runs if this flag is set to `true` .\n\n> `BatchImportMetaDataOnCreate` is not supported for data repositories linked to an Amazon File Cache resource.",
"DataRepositoryPath": "The path to the data repository that will be linked to the cache or file system.\n\n- For Amazon File Cache, the path can be an NFS data repository that will be linked to the cache. The path can be in one of two formats:\n\n- If you are not using the `DataRepositorySubdirectories` parameter, the path is to an NFS Export directory (or one of its subdirectories) in the format `nsf://nfs-domain-name/exportpath` . You can therefore link a single NFS Export to a single data repository association.\n- If you are using the `DataRepositorySubdirectories` parameter, the path is the domain name of the NFS file system in the format `nfs://filer-domain-name` , which indicates the root of the subdirectories specified with the `DataRepositorySubdirectories` parameter.\n- For Amazon File Cache, the path can be an S3 bucket or prefix in the format `s3://myBucket/myPrefix/` .\n- For Amazon FSx for Lustre, the path can be an S3 bucket or prefix in the format `s3://myBucket/myPrefix/` .",
Expand Down Expand Up @@ -23531,10 +23531,10 @@
"description": "The `AWS::GuardDuty::Filter` resource specifies a new filter defined by the provided `findingCriteria` .",
"properties": {
"Action": "Specifies the action that is to be applied to the findings that match the filter.",
"Description": "The description of the filter.",
"Description": "The description of the filter. Valid special characters include period (.), underscore (_), dash (-), and whitespace. The new line character is considered to be an invalid input for description.",
"DetectorId": "The ID of the detector belonging to the GuardDuty account that you want to create a filter for.",
"FindingCriteria": "Represents the criteria to be used in the filter for querying findings.",
"Name": "The name of the filter. Minimum length of 3. Maximum length of 64. Valid characters include alphanumeric characters, dot (.), underscore (_), and dash (-). Spaces are not allowed.",
"Name": "The name of the filter. Valid characters include period (.), underscore (_), dash (-), and alphanumeric characters. A whitespace is considered to be an invalid character.",
"Rank": "Specifies the position of the filter in the list of current filters. Also specifies the order in which this filter is applied to the findings.\n\n> By default, filters may not be created in the same order as they are ranked. To ensure filters are created in the correct order, you can use the optional `DependsOn` attribute with the following syntax: `\"DependsOn\":[ \"ObjectName\" ]` . You can find more information on using this attribute [here](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-dependson.html) .",
"Tags": "The tags to be added to a new filter resource. Each tag consists of a key and an optional value, both of which you define.\n\nFor more information, see [Tag](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html) ."
}
Expand Down Expand Up @@ -38790,7 +38790,7 @@
"attributes": {},
"description": "The parameters for using a Lambda function as a target.",
"properties": {
"InvocationType": "Choose from the following options.\n\n- `REQUEST_RESPONSE` (default) - Invoke synchronously.\n- `FIRE_AND_FORGET` - Invoke asynchronously.\n\nFor more information, see [Invocation types](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-pipes.html#pipes-invocation) in the *Amazon EventBridge User Guide* ."
"InvocationType": "Specify whether to invoke the function synchronously or asynchronously.\n\n- `REQUEST_RESPONSE` (default) - Invoke synchronously. This corresponds to the `RequestResponse` option in the `InvocationType` parameter for the Lambda [Invoke](https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html#API_Invoke_RequestSyntax) API.\n- `FIRE_AND_FORGET` - Invoke asynchronously. This corresponds to the `Event` option in the `InvocationType` parameter for the Lambda [Invoke](https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html#API_Invoke_RequestSyntax) API.\n\nFor more information, see [Invocation types](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-pipes.html#pipes-invocation) in the *Amazon EventBridge User Guide* ."
}
},
"AWS::Pipes::Pipe.PipeTargetParameters": {
Expand Down Expand Up @@ -38842,7 +38842,7 @@
"attributes": {},
"description": "The parameters for using a Step Functions state machine as a target.",
"properties": {
"InvocationType": "Specify whether to wait for the state machine to finish or not.\n\nChoose from the following options.\n\n- `REQUEST_RESPONSE` (default) - Invoke synchronously.\n- `FIRE_AND_FORGET` - Invoke asynchronously.\n\nFor more information, see [Invocation types](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-pipes.html#pipes-invocation) in the *Amazon EventBridge User Guide* ."
"InvocationType": "Specify whether to invoke the Step Functions state machine synchronously or asynchronously.\n\n- `REQUEST_RESPONSE` (default) - Invoke synchronously. For more information, see [StartSyncExecution](https://docs.aws.amazon.com/step-functions/latest/apireference/API_StartSyncExecution.html) in the *AWS Step Functions API Reference* .\n\n> `REQUEST_RESPONSE` is not supported for `STANDARD` state machine workflows.\n- `FIRE_AND_FORGET` - Invoke asynchronously. For more information, see [StartExecution](https://docs.aws.amazon.com/step-functions/latest/apireference/API_StartExecution.html) in the *AWS Step Functions API Reference* .\n\nFor more information, see [Invocation types](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-pipes.html#pipes-invocation) in the *Amazon EventBridge User Guide* ."
}
},
"AWS::Pipes::Pipe.PlacementConstraint": {
Expand Down Expand Up @@ -41027,7 +41027,7 @@
"attributes": {},
"description": "The input for the AWS Lambda endpoint type.",
"properties": {
"Arn": "The Amazon Resource Name (ARN) of the Lambda endpoint."
"Arn": "The Amazon Resource Name (ARN) of the Lambda function or alias."
}
},
"AWS::RefactorSpaces::Service.UrlEndpointInput": {
Expand Down

0 comments on commit 08a1e44

Please sign in to comment.