feat(client-oam): Add IncludeTags field to GetLink, GetSink and UpdateLink API

Author: awstools

clients/client-oam/README.md

@@ -6,21 +6,7 @@
 
 AWS SDK for JavaScript OAM Client for Node.js, Browser and React Native.
 
-<p>Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and
-monitoring accounts by using <i>CloudWatch cross-account observability</i>. With
-CloudWatch cross-account observability, you can monitor and troubleshoot applications that span
-multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics,
-logs, traces, Application Signals services, service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p>
-<p>Set up one or more Amazon Web Services accounts as <i>monitoring
-accounts</i> and link them with multiple <i>source accounts</i>. A
-monitoring account is a central Amazon Web Services account that can view and interact with
-observability data generated from source accounts. A source account is an individual Amazon Web Services account that generates observability data for the resources that reside in it.
-Source accounts share their observability data with the monitoring account. The shared
-observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray,  Application Signals services, service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors
-in CloudWatch Internet Monitor.</p>
-<p>When you set up a link, you can choose to share the metrics from all namespaces with the monitoring account, or filter to a subset of namespaces.
-And for CloudWatch Logs, you can choose to share all log groups with the monitoring account, or filter to a subset of log groups.
-</p>
+<p>Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and monitoring accounts by using <i>CloudWatch cross-account observability</i>. With CloudWatch cross-account observability, you can monitor and troubleshoot applications that span multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics, logs, traces, Application Signals services and service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p> <p>Set up one or more Amazon Web Services accounts as <i>monitoring accounts</i> and link them with multiple <i>source accounts</i>. A monitoring account is a central Amazon Web Services account that can view and interact with observability data generated from source accounts. A source account is an individual Amazon Web Services account that generates observability data for the resources that reside in it. Source accounts share their observability data with the monitoring account. The shared observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray, Application Signals services and service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors in CloudWatch Internet Monitor.</p> <p>When you set up a link, you can choose to share the metrics from all namespaces with the monitoring account, or filter to a subset of namespaces. And for CloudWatch Logs, you can choose to share all log groups with the monitoring account, or filter to a subset of log groups. </p>
 
 ## Installing
 

clients/client-oam/src/OAM.ts

@@ -239,21 +239,7 @@ export interface OAM {
 }
 
 /**
- * <p>Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and
- *       monitoring accounts by using <i>CloudWatch cross-account observability</i>. With
- *         CloudWatch cross-account observability, you can monitor and troubleshoot applications that span
- *       multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics,
- *       logs, traces, Application Signals services, service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p>
- *          <p>Set up one or more Amazon Web Services accounts as <i>monitoring
- *         accounts</i> and link them with multiple <i>source accounts</i>. A
- *       monitoring account is a central Amazon Web Services account that can view and interact with
- *       observability data generated from source accounts. A source account is an individual Amazon Web Services account that generates observability data for the resources that reside in it.
- *       Source accounts share their observability data with the monitoring account. The shared
- *       observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray,  Application Signals services, service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors
- *        in CloudWatch Internet Monitor.</p>
- *          <p>When you set up a link, you can choose to share the metrics from all namespaces with the monitoring account, or filter to a subset of namespaces.
- *        And for CloudWatch Logs, you can choose to share all log groups with the monitoring account, or filter to a subset of log groups.
- *      </p>
+ * <p>Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and monitoring accounts by using <i>CloudWatch cross-account observability</i>. With CloudWatch cross-account observability, you can monitor and troubleshoot applications that span multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics, logs, traces, Application Signals services and service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p> <p>Set up one or more Amazon Web Services accounts as <i>monitoring accounts</i> and link them with multiple <i>source accounts</i>. A monitoring account is a central Amazon Web Services account that can view and interact with observability data generated from source accounts. A source account is an individual Amazon Web Services account that generates observability data for the resources that reside in it. Source accounts share their observability data with the monitoring account. The shared observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray, Application Signals services and service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors in CloudWatch Internet Monitor.</p> <p>When you set up a link, you can choose to share the metrics from all namespaces with the monitoring account, or filter to a subset of namespaces. And for CloudWatch Logs, you can choose to share all log groups with the monitoring account, or filter to a subset of log groups. </p>
  * @public
  */
 export class OAM extends OAMClient implements OAM {}

clients/client-oam/src/OAMClient.ts

@@ -313,21 +313,7 @@ export type OAMClientResolvedConfigType = __SmithyResolvedConfiguration<__HttpHa
 export interface OAMClientResolvedConfig extends OAMClientResolvedConfigType {}
 
 /**
- * <p>Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and
- *       monitoring accounts by using <i>CloudWatch cross-account observability</i>. With
- *         CloudWatch cross-account observability, you can monitor and troubleshoot applications that span
- *       multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics,
- *       logs, traces, Application Signals services, service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p>
- *          <p>Set up one or more Amazon Web Services accounts as <i>monitoring
- *         accounts</i> and link them with multiple <i>source accounts</i>. A
- *       monitoring account is a central Amazon Web Services account that can view and interact with
- *       observability data generated from source accounts. A source account is an individual Amazon Web Services account that generates observability data for the resources that reside in it.
- *       Source accounts share their observability data with the monitoring account. The shared
- *       observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray,  Application Signals services, service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors
- *        in CloudWatch Internet Monitor.</p>
- *          <p>When you set up a link, you can choose to share the metrics from all namespaces with the monitoring account, or filter to a subset of namespaces.
- *        And for CloudWatch Logs, you can choose to share all log groups with the monitoring account, or filter to a subset of log groups.
- *      </p>
+ * <p>Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and monitoring accounts by using <i>CloudWatch cross-account observability</i>. With CloudWatch cross-account observability, you can monitor and troubleshoot applications that span multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics, logs, traces, Application Signals services and service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p> <p>Set up one or more Amazon Web Services accounts as <i>monitoring accounts</i> and link them with multiple <i>source accounts</i>. A monitoring account is a central Amazon Web Services account that can view and interact with observability data generated from source accounts. A source account is an individual Amazon Web Services account that generates observability data for the resources that reside in it. Source accounts share their observability data with the monitoring account. The shared observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray, Application Signals services and service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors in CloudWatch Internet Monitor.</p> <p>When you set up a link, you can choose to share the metrics from all namespaces with the monitoring account, or filter to a subset of namespaces. And for CloudWatch Logs, you can choose to share all log groups with the monitoring account, or filter to a subset of log groups. </p>
  * @public
  */
 export class OAMClient extends __Client<

clients/client-oam/src/commands/CreateLinkCommand.ts

@@ -28,18 +28,7 @@ export interface CreateLinkCommandInput extends CreateLinkInput {}
 export interface CreateLinkCommandOutput extends CreateLinkOutput, __MetadataBearer {}
 
 /**
- * <p>Creates a link between a source account and a sink that you have created in a monitoring account. After the link is created,
- *       data is sent from the source account to the monitoring account. When you create a link, you can optionally specify filters
- *       that specify which metric namespaces and which log groups are shared from the source account to the monitoring account.</p>
- *          <p>Before you create a link, you must create a sink in the monitoring account and create a
- *       sink policy in that account. The sink policy must permit the source account to link to it. You
- *       can grant permission to source accounts by granting permission to an entire organization or to
- *       individual accounts.</p>
- *          <p>For more information, see
- *        <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_CreateSink.html">CreateSink</a> and
- *        <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_PutSinkPolicy.html">PutSinkPolicy</a>.</p>
- *          <p>Each monitoring account can be linked to as many as 100,000 source accounts.</p>
- *          <p>Each source account can be linked to as many as five monitoring accounts.</p>
+ * <p>Creates a link between a source account and a sink that you have created in a monitoring account. After the link is created, data is sent from the source account to the monitoring account. When you create a link, you can optionally specify filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account.</p> <p>Before you create a link, you must create a sink in the monitoring account and create a sink policy in that account. The sink policy must permit the source account to link to it. You can grant permission to source accounts by granting permission to an entire organization or to individual accounts.</p> <p>For more information, see <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_CreateSink.html">CreateSink</a> and <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_PutSinkPolicy.html">PutSinkPolicy</a>.</p> <p>Each monitoring account can be linked to as many as 100,000 source accounts.</p> <p>Each source account can be linked to as many as five monitoring accounts.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-oam/src/commands/CreateSinkCommand.ts

@@ -28,13 +28,7 @@ export interface CreateSinkCommandInput extends CreateSinkInput {}
 export interface CreateSinkCommandOutput extends CreateSinkOutput, __MetadataBearer {}
 
 /**
- * <p>Use this to create a <i>sink</i> in the current account, so that it can be
- *         used as a monitoring account in CloudWatch cross-account observability. A sink is a resource that
- *       represents an attachment point in a monitoring account. Source accounts can link to the sink
- *       to send observability data.</p>
- *          <p>After you create a sink, you must create a sink policy that allows source accounts to attach to it.
- *        For more information, see <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_PutSinkPolicy.html">PutSinkPolicy</a>.</p>
- *          <p>Each account can contain one sink per Region. If you delete a sink, you can then create a new one in that Region.</p>
+ * <p>Use this to create a <i>sink</i> in the current account, so that it can be used as a monitoring account in CloudWatch cross-account observability. A sink is a resource that represents an attachment point in a monitoring account. Source accounts can link to the sink to send observability data.</p> <p>After you create a sink, you must create a sink policy that allows source accounts to attach to it. For more information, see <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_PutSinkPolicy.html">PutSinkPolicy</a>.</p> <p>Each account can contain one sink per Region. If you delete a sink, you can then create a new one in that Region.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-oam/src/commands/DeleteLinkCommand.ts

@@ -28,8 +28,7 @@ export interface DeleteLinkCommandInput extends DeleteLinkInput {}
 export interface DeleteLinkCommandOutput extends DeleteLinkOutput, __MetadataBearer {}
 
 /**
- * <p>Deletes a link between a monitoring account sink and a source account. You must run this operation
- *       in the source account.</p>
+ * <p>Deletes a link between a monitoring account sink and a source account. You must run this operation in the source account.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-oam/src/commands/GetLinkCommand.ts

@@ -28,8 +28,7 @@ export interface GetLinkCommandInput extends GetLinkInput {}
 export interface GetLinkCommandOutput extends GetLinkOutput, __MetadataBearer {}
 
 /**
- * <p>Returns complete information about one link.</p>
- *          <p>To use this operation, provide the link ARN. To retrieve a list of link ARNs, use <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_ListLinks.html">ListLinks</a>.</p>
+ * <p>Returns complete information about one link.</p> <p>To use this operation, provide the link ARN. To retrieve a list of link ARNs, use <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_ListLinks.html">ListLinks</a>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -38,6 +37,7 @@ export interface GetLinkCommandOutput extends GetLinkOutput, __MetadataBearer {}
  * const client = new OAMClient(config);
  * const input = { // GetLinkInput
  *   Identifier: "STRING_VALUE", // required
+ *   IncludeTags: true || false,
  * };
  * const command = new GetLinkCommand(input);
  * const response = await client.send(command);

clients/client-oam/src/commands/GetSinkCommand.ts

@@ -28,8 +28,7 @@ export interface GetSinkCommandInput extends GetSinkInput {}
 export interface GetSinkCommandOutput extends GetSinkOutput, __MetadataBearer {}
 
 /**
- * <p>Returns complete information about one monitoring account sink.</p>
- *          <p>To use this operation, provide the sink ARN. To retrieve a list of sink ARNs, use <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_ListSinks.html">ListSinks</a>.</p>
+ * <p>Returns complete information about one monitoring account sink.</p> <p>To use this operation, provide the sink ARN. To retrieve a list of sink ARNs, use <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_ListSinks.html">ListSinks</a>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -38,6 +37,7 @@ export interface GetSinkCommandOutput extends GetSinkOutput, __MetadataBearer {}
  * const client = new OAMClient(config);
  * const input = { // GetSinkInput
  *   Identifier: "STRING_VALUE", // required
+ *   IncludeTags: true || false,
  * };
  * const command = new GetSinkCommand(input);
  * const response = await client.send(command);

clients/client-oam/src/commands/GetSinkPolicyCommand.ts

@@ -28,8 +28,7 @@ export interface GetSinkPolicyCommandInput extends GetSinkPolicyInput {}
 export interface GetSinkPolicyCommandOutput extends GetSinkPolicyOutput, __MetadataBearer {}
 
 /**
- * <p>Returns the current sink policy attached to this sink. The sink policy specifies what
- *       accounts can attach to this sink as source accounts, and what types of data they can share.</p>
+ * <p>Returns the current sink policy attached to this sink. The sink policy specifies what accounts can attach to this sink as source accounts, and what types of data they can share.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-oam/src/commands/ListAttachedLinksCommand.ts

@@ -28,9 +28,7 @@ export interface ListAttachedLinksCommandInput extends ListAttachedLinksInput {}
 export interface ListAttachedLinksCommandOutput extends ListAttachedLinksOutput, __MetadataBearer {}
 
 /**
- * <p>Returns a list of source account links that are linked to this monitoring account sink.</p>
- *          <p>To use this operation, provide the sink ARN. To retrieve a list of sink ARNs, use <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_ListSinks.html">ListSinks</a>.</p>
- *          <p>To find a list of links for one source account, use <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_ListLinks.html">ListLinks</a>.</p>
+ * <p>Returns a list of source account links that are linked to this monitoring account sink.</p> <p>To use this operation, provide the sink ARN. To retrieve a list of sink ARNs, use <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_ListSinks.html">ListSinks</a>.</p> <p>To find a list of links for one source account, use <a href="https://docs.aws.amazon.com/OAM/latest/APIReference/API_ListLinks.html">ListLinks</a>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript