@aws-sdk/client-proton 3.58.0 → 3.72.0

package/CHANGELOG.md

@@ -3,6 +3,33 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [3.72.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.71.0...v3.72.0) (2022-04-15)
+
+**Note:** Version bump only for package @aws-sdk/client-proton
+
+
+
+
+
+# [3.67.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.66.0...v3.67.0) (2022-04-08)
+
+**Note:** Version bump only for package @aws-sdk/client-proton
+
+
+
+
+
+# [3.63.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.62.0...v3.63.0) (2022-04-04)
+
+
+### Features
+
+* **client-proton:** SDK release to support tagging for AWS Proton Repository resource ([19e9f72](https://github.com/aws/aws-sdk-js-v3/commit/19e9f72ab60539b87624019ba16921ce495a5d4f))
+
+
+
+
+
 # [3.58.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.57.0...v3.58.0) (2022-03-28)
 
 **Note:** Version bump only for package @aws-sdk/client-proton

package/README.md

@@ -7,55 +7,48 @@
 
 AWS SDK for JavaScript Proton Client for Node.js, Browser and React Native.
 
-<p>This is the Proton Service API Reference. It provides descriptions, syntax and usage examples for each of the
-<a href="https://docs.aws.amazon.com/proton/latest/APIReference/API_Operations.html">actions</a> and <a href="https://docs.aws.amazon.com/proton/latest/APIReference/API_Types.html">data types</a> for the Proton
-service.</p>
+<p>This is the Proton Service API Reference. It provides descriptions, syntax and usage examples for each of the <a href="https://docs.aws.amazon.com/proton/latest/APIReference/API_Operations.html">actions</a> and <a href="https://docs.aws.amazon.com/proton/latest/APIReference/API_Types.html">data types</a> for the Proton service.</p>
 <p>The documentation for each action shows the Query API request parameters and the XML response.</p>
-<p>Alternatively, you can use the Amazon Web Services CLI to access an API. For more information, see the <a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html">Amazon Web Services Command Line Interface User
-Guide</a>.</p>
-<p>The Proton service is a two-pronged automation framework. Administrators create service templates to provide
-standardized infrastructure and deployment tooling for serverless and container based applications. Developers, in
-turn, select from the available service templates to automate their application or service deployments.</p>
-<p>Because administrators define the infrastructure and tooling that Proton deploys and manages, they need
-permissions to use all of the listed API operations.</p>
-<p>When developers select a specific infrastructure and tooling set, Proton deploys their applications. To
-monitor their applications that are running on Proton, developers need permissions to the service
-<i>create</i>, <i>list</i>, <i>update</i> and <i>delete</i>
-API operations and the service instance <i>list</i> and <i>update</i> API
-operations.</p>
-<p>To learn more about Proton administration, see the <a href="https://docs.aws.amazon.com/proton/latest/adminguide/Welcome.html">Proton Administrator Guide</a>.</p>
+<p>Alternatively, you can use the Amazon Web Services CLI to access an API. For more information, see the <a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html">Amazon Web Services Command Line Interface User Guide</a>.</p>
+<p>The Proton service is a two-pronged automation framework. Administrators create service templates to provide standardized infrastructure
+and deployment tooling for serverless and container based applications. Developers, in turn, select from the available service templates to
+automate their application or service deployments.</p>
+<p>Because administrators define the infrastructure and tooling that Proton deploys and manages, they need permissions to use all of the
+listed API operations.</p>
+<p>When developers select a specific infrastructure and tooling set, Proton deploys their applications. To monitor their applications that are
+running on Proton, developers need permissions to the service <i>create</i>, <i>list</i>,
+<i>update</i> and <i>delete</i> API operations and the service instance <i>list</i> and
+<i>update</i> API operations.</p>
+<p>To learn more about Proton administration, see the <a href="https://docs.aws.amazon.com/proton/latest/adminguide/Welcome.html">Proton
+Administrator Guide</a>.</p>
 <p>To learn more about deploying serverless and containerized applications on Proton, see the <a href="https://docs.aws.amazon.com/proton/latest/userguide/Welcome.html">Proton User Guide</a>.</p>
 <p>
 <b>Ensuring Idempotency</b>
 </p>
-<p>When you make a mutating API request, the request typically returns a result before the asynchronous workflows
-of the operation are complete. Operations might also time out or encounter other server issues before they're
-complete, even if the request already returned a result. This might make it difficult to determine whether the
-request succeeded. Moreover, you might need to retry the request multiple times to ensure that the operation
-completes successfully. However, if the original request and the subsequent retries are successful, the operation
-occurs multiple times. This means that you might create more resources than you intended.</p>
+<p>When you make a mutating API request, the request typically returns a result before the asynchronous workflows of the operation are complete.
+Operations might also time out or encounter other server issues before they're complete, even if the request already returned a result. This might
+make it difficult to determine whether the request succeeded. Moreover, you might need to retry the request multiple times to ensure that the
+operation completes successfully. However, if the original request and the subsequent retries are successful, the operation occurs multiple times.
+This means that you might create more resources than you intended.</p>
 <p>
-<i>Idempotency</i> ensures that an API request action completes no more than one time. With an
-idempotent request, if the original request action completes successfully, any subsequent retries complete
-successfully without performing any further actions. However, the result might contain updated information, such as
-the current creation status.</p>
+<i>Idempotency</i> ensures that an API request action completes no more than one time. With an idempotent request, if the
+original request action completes successfully, any subsequent retries complete successfully without performing any further actions. However, the
+result might contain updated information, such as the current creation status.</p>
 <p>The following lists of APIs are grouped according to methods that ensure idempotency.</p>
 <p>
 <b>Idempotent create APIs with a client token</b>
 </p>
-<p>The API actions in this list support idempotency with the use of a <i>client token</i>. The
-corresponding Amazon Web Services CLI commands also support idempotency using a client token. A client token is a unique,
-case-sensitive string of up to 64 ASCII characters. To make an idempotent API request using one of these actions,
-specify a client token in the request. We recommend that you <i>don't</i> reuse the same client token
-for other API requests. If you don’t provide a client token for these APIs, a default client token is automatically
-provided by SDKs.</p>
+<p>The API actions in this list support idempotency with the use of a <i>client token</i>. The corresponding Amazon Web Services CLI commands
+also support idempotency using a client token. A client token is a unique, case-sensitive string of up to 64 ASCII characters. To make an
+idempotent API request using one of these actions, specify a client token in the request. We recommend that you <i>don't</i> reuse
+the same client token for other API requests. If you don’t provide a client token for these APIs, a default client token is automatically provided
+by SDKs.</p>
 <p>Given a request action that has succeeded:</p>
-<p>If you retry the request using the same client token and the same parameters, the retry succeeds without
-performing any further actions other than returning the original resource detail data in the response.</p>
-<p>If you retry the request using the same client token, but one or more of the parameters are different, the retry
-throws a <code>ValidationException</code> with an <code>IdempotentParameterMismatch</code> error.</p>
-<p>Client tokens expire eight hours after a request is made. If you retry the request with the expired token, a new
-resource is created.</p>
+<p>If you retry the request using the same client token and the same parameters, the retry succeeds without performing any further actions other
+than returning the original resource detail data in the response.</p>
+<p>If you retry the request using the same client token, but one or more of the parameters are different, the retry throws a
+<code>ValidationException</code> with an <code>IdempotentParameterMismatch</code> error.</p>
+<p>Client tokens expire eight hours after a request is made. If you retry the request with the expired token, a new resource is created.</p>
 <p>If the original resource is deleted and you retry the request, a new resource is created.</p>
 <p>Idempotent create APIs with a client token:</p>
 <ul>
@@ -73,9 +66,8 @@ resource is created.</p>
 <b>Idempotent create APIs</b>
 </p>
 <p>Given a request action that has succeeded:</p>
-<p>If you retry the request with an API from this group, and the original resource <i>hasn't</i> been
-modified, the retry succeeds without performing any further actions other than returning the original resource detail
-data in the response.</p>
+<p>If you retry the request with an API from this group, and the original resource <i>hasn't</i> been modified, the retry succeeds
+without performing any further actions other than returning the original resource detail data in the response.</p>
 <p>If the original resource has been modified, the retry throws a <code>ConflictException</code>.</p>
 <p>If you retry with different input parameters, the retry throws a <code>ValidationException</code> with an
 <code>IdempotentParameterMismatch</code> error.</p>
@@ -98,8 +90,7 @@ data in the response.</p>
 <b>Idempotent delete APIs</b>
 </p>
 <p>Given a request action that has succeeded:</p>
-<p>When you retry the request with an API from this group and the resource was deleted, its metadata is returned in
-the response.</p>
+<p>When you retry the request with an API from this group and the resource was deleted, its metadata is returned in the response.</p>
 <p>If you retry and the resource doesn't exist, the response is empty.</p>
 <p>In both cases, the retry succeeds.</p>
 <p>Idempotent delete APIs:</p>
@@ -124,9 +115,8 @@ the response.</p>
 <b>Asynchronous idempotent delete APIs</b>
 </p>
 <p>Given a request action that has succeeded:</p>
-<p>If you retry the request with an API from this group, if the original request delete operation status is
-<code>DELETE_IN_PROGRESS</code>, the retry returns the resource detail data in the response without performing any
-further actions.</p>
+<p>If you retry the request with an API from this group, if the original request delete operation status is <code>DELETE_IN_PROGRESS</code>, the
+retry returns the resource detail data in the response without performing any further actions.</p>
 <p>If the original request delete operation is complete, a retry returns an empty response.</p>
 <p>Asynchronous idempotent delete APIs:</p>
 <ul>
@@ -244,7 +234,7 @@ but they are supported by the send operation.
 ```js
 // callbacks.
 client.send(command, (err, data) => {
-  // proccess err and data.
+  // process err and data.
 });
 ```
 
@@ -278,7 +268,7 @@ client
 
 // callbacks.
 client.acceptEnvironmentAccountConnection(params, (err, data) => {
-  // proccess err and data.
+  // process err and data.
 });
 ```
 

package/dist-cjs/protocols/Aws_json1_0.js

@@ -4170,6 +4170,7 @@ const serializeAws_json1_0CreateRepositoryInput = (input, context) => {
         ...(input.encryptionKey !== undefined && input.encryptionKey !== null && { encryptionKey: input.encryptionKey }),
         ...(input.name !== undefined && input.name !== null && { name: input.name }),
         ...(input.provider !== undefined && input.provider !== null && { provider: input.provider }),
+        ...(input.tags !== undefined && input.tags !== null && { tags: serializeAws_json1_0TagList(input.tags, context) }),
     };
 };
 const serializeAws_json1_0CreateServiceInput = (input, context) => {

package/dist-es/protocols/Aws_json1_0.js

@@ -5428,7 +5428,7 @@ var serializeAws_json1_0CreateEnvironmentTemplateVersionInput = function (input,
         input.source !== null && { source: serializeAws_json1_0TemplateVersionSourceInput(input.source, context) })), (input.tags !== undefined && input.tags !== null && { tags: serializeAws_json1_0TagList(input.tags, context) })), (input.templateName !== undefined && input.templateName !== null && { templateName: input.templateName }));
 };
 var serializeAws_json1_0CreateRepositoryInput = function (input, context) {
-    return __assign(__assign(__assign(__assign({}, (input.connectionArn !== undefined && input.connectionArn !== null && { connectionArn: input.connectionArn })), (input.encryptionKey !== undefined && input.encryptionKey !== null && { encryptionKey: input.encryptionKey })), (input.name !== undefined && input.name !== null && { name: input.name })), (input.provider !== undefined && input.provider !== null && { provider: input.provider }));
+    return __assign(__assign(__assign(__assign(__assign({}, (input.connectionArn !== undefined && input.connectionArn !== null && { connectionArn: input.connectionArn })), (input.encryptionKey !== undefined && input.encryptionKey !== null && { encryptionKey: input.encryptionKey })), (input.name !== undefined && input.name !== null && { name: input.name })), (input.provider !== undefined && input.provider !== null && { provider: input.provider })), (input.tags !== undefined && input.tags !== null && { tags: serializeAws_json1_0TagList(input.tags, context) }));
 };
 var serializeAws_json1_0CreateServiceInput = function (input, context) {
     return __assign(__assign(__assign(__assign(__assign(__assign(__assign(__assign(__assign(__assign({}, (input.branchName !== undefined && input.branchName !== null && { branchName: input.branchName })), (input.description !== undefined && input.description !== null && { description: input.description })), (input.name !== undefined && input.name !== null && { name: input.name })), (input.repositoryConnectionArn !== undefined &&