@aws-sdk/client-mediapackagev2 3.883.0 → 3.885.0

package/dist-types/commands/UpdateOriginEndpointCommand.d.ts

@@ -27,8 +27,7 @@ declare const UpdateOriginEndpointCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Update the specified origin endpoint. Edit the packaging preferences on an endpoint to optimize the viewing experience. You can't edit the name of the endpoint.</p>
- *          <p>Any edits you make that impact the video output may not be reflected for a few minutes.</p>
+ * <p>Update the specified origin endpoint. Edit the packaging preferences on an endpoint to optimize the viewing experience. You can't edit the name of the endpoint.</p> <p>Any edits you make that impact the video output may not be reflected for a few minutes.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -81,7 +80,7 @@ declare const UpdateOriginEndpointCommand_base: {
  *       ManifestName: "STRING_VALUE", // required
  *       ChildManifestName: "STRING_VALUE",
  *       ScteHls: { // ScteHls
- *         AdMarkerHls: "DATERANGE",
+ *         AdMarkerHls: "DATERANGE" || "SCTE35_ENHANCED",
  *       },
  *       StartTag: { // StartTag
  *         TimeOffset: Number("float"), // required
@@ -104,7 +103,7 @@ declare const UpdateOriginEndpointCommand_base: {
  *       ManifestName: "STRING_VALUE", // required
  *       ChildManifestName: "STRING_VALUE",
  *       ScteHls: {
- *         AdMarkerHls: "DATERANGE",
+ *         AdMarkerHls: "DATERANGE" || "SCTE35_ENHANCED",
  *       },
  *       StartTag: {
  *         TimeOffset: Number("float"), // required
@@ -262,7 +261,7 @@ declare const UpdateOriginEndpointCommand_base: {
  * //       ManifestWindowSeconds: Number("int"),
  * //       ProgramDateTimeIntervalSeconds: Number("int"),
  * //       ScteHls: { // ScteHls
- * //         AdMarkerHls: "DATERANGE",
+ * //         AdMarkerHls: "DATERANGE" || "SCTE35_ENHANCED",
  * //       },
  * //       FilterConfiguration: { // FilterConfiguration
  * //         ManifestFilter: "STRING_VALUE",
@@ -286,7 +285,7 @@ declare const UpdateOriginEndpointCommand_base: {
  * //       ManifestWindowSeconds: Number("int"),
  * //       ProgramDateTimeIntervalSeconds: Number("int"),
  * //       ScteHls: {
- * //         AdMarkerHls: "DATERANGE",
+ * //         AdMarkerHls: "DATERANGE" || "SCTE35_ENHANCED",
  * //       },
  * //       FilterConfiguration: {
  * //         ManifestFilter: "STRING_VALUE",
@@ -403,9 +402,7 @@ declare const UpdateOriginEndpointCommand_base: {
  * @see {@link MediaPackageV2ClientResolvedConfig | config} for MediaPackageV2Client's `config` shape.
  *
  * @throws {@link AccessDeniedException} (client fault)
- *  <p>Access is denied because either you don't have permissions to perform the requested operation or MediaPackage is getting throttling errors with CDN authorization. The user or role that is making the request must have at least
- *          one IAM permissions policy attached that grants the required permissions. For more information, see Access Management in the IAM User Guide. Or, if you're using CDN authorization, you will receive this exception
- *          if MediaPackage receives a throttling error from Secrets Manager.</p>
+ *  <p>Access is denied because either you don't have permissions to perform the requested operation or MediaPackage is getting throttling errors with CDN authorization. The user or role that is making the request must have at least one IAM permissions policy attached that grants the required permissions. For more information, see Access Management in the IAM User Guide. Or, if you're using CDN authorization, you will receive this exception if MediaPackage receives a throttling error from Secrets Manager.</p>
  *
  * @throws {@link ConflictException} (client fault)
  *  <p>Updating or deleting this resource can cause an inconsistent state.</p>

package/dist-types/index.d.ts

@@ -1,16 +1,5 @@
 /**
- * <note>
- *             <p>This guide is intended for creating AWS Elemental MediaPackage resources in MediaPackage Version 2 (v2) starting from May 2023.
- *         To get started with MediaPackage v2, create your MediaPackage resources. There isn't an automated process to
- *         migrate your resources from MediaPackage v1 to MediaPackage v2. </p>
- *             <p>The names of the entities that you use to access this API, like URLs and ARNs, all have the versioning information
- *            added, like "v2", to distinguish from the prior version. If you used MediaPackage prior to this release, you can't use
- *            the MediaPackage v2 CLI or the MediaPackage v2 API to access any MediaPackage v1 resources.</p>
- *             <p>If you created resources in MediaPackage v1, use video on demand (VOD) workflows, and aren't looking to migrate to MediaPackage v2 yet,
- *            see the <a href="https://docs.aws.amazon.com/mediapackage/latest/apireference/what-is.html">MediaPackage v1 Live API Reference</a>.</p>
- *          </note>
- *          <p>This is the AWS Elemental MediaPackage v2 Live REST API Reference. It describes all the MediaPackage API operations for live content in detail, and provides sample requests, responses, and errors for the supported web services protocols.</p>
- *          <p>We assume that you have the IAM permissions that you need to use MediaPackage via the REST API. We also assume that you are familiar with the features and operations of MediaPackage, as described in the AWS Elemental MediaPackage User Guide.</p>
+ * <note> <p>This guide is intended for creating AWS Elemental MediaPackage resources in MediaPackage Version 2 (v2) starting from May 2023. To get started with MediaPackage v2, create your MediaPackage resources. There isn't an automated process to migrate your resources from MediaPackage v1 to MediaPackage v2. </p> <p>The names of the entities that you use to access this API, like URLs and ARNs, all have the versioning information added, like "v2", to distinguish from the prior version. If you used MediaPackage prior to this release, you can't use the MediaPackage v2 CLI or the MediaPackage v2 API to access any MediaPackage v1 resources.</p> <p>If you created resources in MediaPackage v1, use video on demand (VOD) workflows, and aren't looking to migrate to MediaPackage v2 yet, see the <a href="https://docs.aws.amazon.com/mediapackage/latest/apireference/what-is.html">MediaPackage v1 Live API Reference</a>.</p> </note> <p>This is the AWS Elemental MediaPackage v2 Live REST API Reference. It describes all the MediaPackage API operations for live content in detail, and provides sample requests, responses, and errors for the supported web services protocols.</p> <p>We assume that you have the IAM permissions that you need to use MediaPackage via the REST API. We also assume that you are familiar with the features and operations of MediaPackage, as described in the AWS Elemental MediaPackage User Guide.</p>
  *
  * @packageDocumentation
  */