Prepare for a release (#790) (84b60985) · Commits · Public Repositories / Smithy Rust

CHANGELOG.md

+3 −0

Original line number	Diff line number	Diff line
		vNext (Month Day, Year)
		=======================

		v0.27 (October 20th, 2021)
		==========================

		Breaking Changes

		- :warning: All Smithy runtime crates have been renamed to have an `aws-` prefix. This may require code changes:

aws/SDK_CHANGELOG.md

+5 −1

Original line number	Diff line number	Diff line
		vNext (Month Day, Year)
		=======================

		v0.0.22-alpha (October 20th, 2021)
		==================================

		Breaking Changes

		- `CredentialsError` variants became non-exhaustive. This makes them impossible to construct directly outside of the `aws_types` crate. In order to construct credentials errors, new methods have been added for each variant. Instead of `CredentialsError::Unhandled(...)`, you should instead use `CredentialsError::unhandled`. Matching methods exist for all variants. (#781)
		@@ -34,6 +37,7 @@ vNext (Month Day, Year)
		- Moved the contents of `aws-auth` into the `aws-http` runtime crate (smithy-rs#783)
		- Fix instances where docs were missing in generated services and add `#[warn_missing_docs]` (smithy-rs#779)
		- Add tracing output for resolved AWS endpoint (smithy-rs#784)
		- Update AWS service models (smithy-rs#790)
		- Add support for the following Glacier customizations:
		- Set the ApiVersion header (smithy-rs#138, #787)

aws/sdk/aws-models/chime-sdk-messaging.json

+1398 −54

File changed.

Preview size limit exceeded, changes collapsed.

aws/sdk/aws-models/dataexchange.json

+229 −34

File changed.

Preview size limit exceeded, changes collapsed.

aws/sdk/aws-models/elasticfilesystem.json

+8 −8

Original line number	Diff line number	Diff line
		@@ -2004,18 +2004,18 @@
		"TransitionToIA": {
		"target": "com.amazonaws.efs#TransitionToIARules",
		"traits": {
		"smithy.api#documentation": "<p>\n Describes the period of time that a file is not accessed, after which it transitions to the IA storage class. Metadata\n operations such as listing the contents of a directory don't count as file access\n events.</p>"
		"smithy.api#documentation": "<p>\n Describes the period of time that a file is not accessed, after which it transitions to IA storage. Metadata\n operations such as listing the contents of a directory don't count as file access\n events.</p>"
		}
		},
		"TransitionToPrimaryStorageClass": {
		"target": "com.amazonaws.efs#TransitionToPrimaryStorageClassRules",
		"traits": {
		"smithy.api#documentation": "<p>Describes the policy used to transition a file from infequent access storage to primary storage.</p>"
		"smithy.api#documentation": "<p>Describes when to transition a file from IA storage to primary storage. Metadata\n operations such as listing the contents of a directory don't count as file access\n events.</p>"
		}
		}
		},
		"traits": {
		"smithy.api#documentation": "<p>Describes a policy used by EFS lifecycle management to transition files to the Infrequent\n Access (IA) storage class.</p>"
		"smithy.api#documentation": "<p>Describes a policy used by EFS lifecycle management and EFS intelligent tiering that specifies when to transition \n files into and out of the file system's Infrequent Access (IA) storage class. For more information, see \n <a href=\"https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html\">EFS Intelligent‐Tiering and EFS Lifecycle Management</a>.</p>\n <note>\n <p>When using the <code>put-lifecycle-configuration</code> CLI command or the <code>PutLifecycleConfiguration</code> API action, \n Amazon EFS requires that each <code>LifecyclePolicy</code> \n object have only a single transition. This means that in a request body, <code>LifecyclePolicies</code> needs to be structured as\n an array of <code>LifecyclePolicy</code> objects, one object for each transition, <code>TransitionToIA</code>, \n <code>TransitionToPrimaryStorageClass</code>. For more information, see the request examples in <a>PutLifecycleConfiguration</a>.</p>\n </note>"
		}
		},
		"com.amazonaws.efs#ListTagsForResource": {
		@@ -2598,7 +2598,7 @@
		}
		],
		"traits": {
		"smithy.api#documentation": "<p>Use this operation to set the account preference in the current Amazon Web Services Region to use either long 17 character (63 bit) or short 8 character (32 bit) IDs for \n new EFS file systems and mount targets created. All existing resource IDs are not affected by any changes you make. You can set the ID preference during the\n opt-in period as EFS transitions to long resource IDs. For more information, \n see <a href=\"efs/latest/ug/manage-efs-resource-ids.html\">Managing Amazon EFS resource IDs</a>.</p>",
		"smithy.api#documentation": "<p>Use this operation to set the account preference in the current Amazon Web Services Region to use long 17 character (63 bit) or short 8 character (32 bit) resource IDs for \n new EFS file system and mount target resources. All existing resource IDs are not affected by any changes you make. You can set the ID preference during the\n opt-in period as EFS transitions to long resource IDs. For more information, \n see <a href=\"https://docs.aws.amazon.com/efs/latest/ug/manage-efs-resource-ids.html\">Managing Amazon EFS resource IDs</a>.</p>\n <note>\n <p>Starting in October, 2021, you will receive an error if you try to set the account preference to use the short 8 character format resource ID. \n Contact Amazon Web Services support if you receive an error and need to use short IDs for file system and mount target resources.</p>\n </note>",
		"smithy.api#http": {
		"method": "PUT",
		"uri": "/2015-02-01/account-preferences",
		@@ -2612,7 +2612,7 @@
		"ResourceIdType": {
		"target": "com.amazonaws.efs#ResourceIdType",
		"traits": {
		"smithy.api#documentation": "<p>Specifies the EFS resource ID preference to set for the user's Amazon Web Services account, in the current Amazon Web Services Region, \n either <code>LONG_ID</code> (17 characters), or <code>SHORT_ID</code> (8 characters).</p>",
		"smithy.api#documentation": "<p>Specifies the EFS resource ID preference to set for the user's Amazon Web Services account, in the current Amazon Web Services Region, \n either <code>LONG_ID</code> (17 characters), or <code>SHORT_ID</code> (8 characters).</p>\n <note>\n <p>Starting in October, 2021, you will receive an error when setting the account preference to <code>SHORT_ID</code>. \n Contact Amazon Web Services support if you receive an error and need to use short IDs for file system and mount target resources.</p>\n </note>",
		"smithy.api#required": {}
		}
		}
		@@ -2703,7 +2703,7 @@
		}
		],
		"traits": {
		"smithy.api#documentation": "<p>Applies an Amazon EFS <code>FileSystemPolicy</code> to an Amazon EFS file system. \n A file system policy is an IAM resource-based policy and can contain multiple policy statements. \n A file system always has exactly one file system policy, which can be the default policy or \n an explicit policy set or updated using this API operation.\n EFS file system policies have a 20,000 character limit.\n When an explicit policy is set, it overrides the default policy. For more information about the default file system policy, see \n <a href=\"https://docs.aws.amazon.com/efs/latest/ug/iam-access-control-nfs-efs.html#default-filesystempolicy\">Default EFS File System Policy</a>.\n </p>\n <p>EFS file system policies have a 20,000 character limit.</p>\n <p>This operation requires permissions for the <code>elasticfilesystem:PutFileSystemPolicy</code> action.</p>",
		"smithy.api#documentation": "<p>Applies an Amazon EFS <code>FileSystemPolicy</code> to an Amazon EFS file system. \n A file system policy is an IAM resource-based policy and can contain multiple policy statements. \n A file system always has exactly one file system policy, which can be the default policy or \n an explicit policy set or updated using this API operation.\n EFS file system policies have a 20,000 character limit.\n When an explicit policy is set, it overrides the default policy. For more information about the default file system policy, see \n <a href=\"https://docs.aws.amazon.com/efs/latest/ug/iam-access-control-nfs-efs.html#default-filesystempolicy\">Default EFS File System Policy</a>.\n </p>\n <note>\n <p>EFS file system policies have a 20,000 character limit.</p>\n </note>\n <p>This operation requires permissions for the <code>elasticfilesystem:PutFileSystemPolicy</code> action.</p>",
		"smithy.api#http": {
		"method": "PUT",
		"uri": "/2015-02-01/file-systems/{FileSystemId}/policy",
		@@ -2760,7 +2760,7 @@
		}
		],
		"traits": {
		"smithy.api#documentation": "<p>Enables lifecycle management by creating a new <code>LifecycleConfiguration</code>\n object. A <code>LifecycleConfiguration</code> object defines when files in an Amazon EFS file\n system are automatically transitioned to the lower-cost EFS Infrequent Access (IA) storage class.\n To enable EFS Intelligent Tiering, set the value of <code>TransitionToPrimaryStorageClass</code> to <code>AFTER_1_ACCESS</code>.\n For more information, see <a href=\"https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html\">EFS Lifecycle Management</a>.</p>\n <p>A <code>LifecycleConfiguration</code> applies to all files in a file system.</p>\n <p>Each Amazon EFS file system supports one lifecycle configuration, which applies to all files in the file system. If a\n <code>LifecycleConfiguration</code> object already exists for the specified file system, a\n <code>PutLifecycleConfiguration</code> call modifies the existing configuration. A\n <code>PutLifecycleConfiguration</code> call with an empty <code>LifecyclePolicies</code>\n array in the request body deletes any existing <code>LifecycleConfiguration</code> and\n disables lifecycle management.</p>\n\n \n <p>In the request, specify the following: </p>\n <ul>\n <li>\n <p>The ID for the file system for which you are enabling, disabling, or modifying lifecycle management.</p>\n </li>\n <li>\n <p>A <code>LifecyclePolicies</code> array of <code>LifecyclePolicy</code> objects that\n define when files are moved to the IA storage class. The array can contain only one\n <code>LifecyclePolicy</code> item.</p>\n </li>\n </ul>\n\n <p>This operation requires permissions for the\n <code>elasticfilesystem:PutLifecycleConfiguration</code> operation.</p>\n <p>To apply a <code>LifecycleConfiguration</code> object to an encrypted file system, you\n need the same Key Management Service permissions as when you created the encrypted\n file system. </p>",
		"smithy.api#documentation": "<p>Enables lifecycle management by creating a new <code>LifecycleConfiguration</code>\n object. A <code>LifecycleConfiguration</code> object defines when files in an Amazon EFS file\n system are automatically transitioned to the lower-cost EFS Infrequent Access (IA) storage class.\n To enable EFS Intelligent Tiering, set the value of <code>TransitionToPrimaryStorageClass</code> to <code>AFTER_1_ACCESS</code>.\n For more information, see <a href=\"https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html\">EFS Lifecycle Management</a>.</p>\n \n <p>Each Amazon EFS file system supports one lifecycle configuration, which applies to all files in the file system. If a\n <code>LifecycleConfiguration</code> object already exists for the specified file system, a\n <code>PutLifecycleConfiguration</code> call modifies the existing configuration. A\n <code>PutLifecycleConfiguration</code> call with an empty <code>LifecyclePolicies</code>\n array in the request body deletes any existing <code>LifecycleConfiguration</code> and\n turns off lifecycle management for the file system.</p>\n\n \n <p>In the request, specify the following: </p>\n <ul>\n <li>\n <p>The ID for the file system for which you are enabling, disabling, or modifying lifecycle management.</p>\n </li>\n <li>\n <p>A <code>LifecyclePolicies</code> array of <code>LifecyclePolicy</code> objects that\n define when files are moved to the IA storage class. Amazon EFS requires that each <code>LifecyclePolicy</code> \n object have only have a single transition, so the <code>LifecyclePolicies</code> array needs to be structured with separate \n <code>LifecyclePolicy</code> objects. See the example requests in the following section for more information.</p>\n </li>\n </ul>\n\n <p>This operation requires permissions for the\n <code>elasticfilesystem:PutLifecycleConfiguration</code> operation.</p>\n <p>To apply a <code>LifecycleConfiguration</code> object to an encrypted file system, you\n need the same Key Management Service permissions as when you created the encrypted\n file system. </p>",
		"smithy.api#http": {
		"method": "PUT",
		"uri": "/2015-02-01/file-systems/{FileSystemId}/lifecycle-configuration",
		@@ -2782,7 +2782,7 @@
		"LifecyclePolicies": {
		"target": "com.amazonaws.efs#LifecyclePolicies",
		"traits": {
		"smithy.api#documentation": "<p>An array of <code>LifecyclePolicy</code> objects that define the file system's\n <code>LifecycleConfiguration</code> object. A <code>LifecycleConfiguration</code> object\n tells lifecycle management when to transition files from the Standard storage class to the\n Infrequent Access storage class.</p>",
		"smithy.api#documentation": "<p>An array of <code>LifecyclePolicy</code> objects that define the file system's\n <code>LifecycleConfiguration</code> object. A <code>LifecycleConfiguration</code> object\n informs EFS lifecycle management and intelligent tiering of the following:</p>\n <ul>\n <li>\n <p>When to move files in the file system from primary storage to the IA storage class.</p>\n </li>\n <li>\n <p>When to move files that are in IA storage to primary storage.</p>\n </li>\n </ul>\n <note>\n <p>When using the <code>put-lifecycle-configuration</code> CLI command or the <code>PutLifecycleConfiguration</code> API action, \n Amazon EFS requires that each <code>LifecyclePolicy</code> \n object have only a single transition. This means that in a request body, <code>LifecyclePolicies</code> needs to be structured as\n an array of <code>LifecyclePolicy</code> objects, one object for each transition, <code>TransitionToIA</code>, <code>TransitionToPrimaryStorageClass</code>. \n See the example requests in the following section for more information.</p>\n </note>",
		"smithy.api#required": {}
		}
		}