feat(client-ivs): Corrects the HTTP response code in the generated do…

…cs for PutMetadata and DeleteRecordingConfiguration APIs.

clients/client-ivs/src/protocols/Aws_restJson1.ts

@@ -1440,7 +1440,7 @@ export const de_DeleteRecordingConfigurationCommand = async (
   output: __HttpResponse,
   context: __SerdeContext
 ): Promise<DeleteRecordingConfigurationCommandOutput> => {
-  if (output.statusCode !== 200 && output.statusCode >= 300) {
+  if (output.statusCode !== 204 && output.statusCode >= 300) {
     return de_DeleteRecordingConfigurationCommandError(output, context);
   }
   const contents: any = map({
@@ -2301,7 +2301,7 @@ export const de_PutMetadataCommand = async (
   output: __HttpResponse,
   context: __SerdeContext
 ): Promise<PutMetadataCommandOutput> => {
-  if (output.statusCode !== 200 && output.statusCode >= 300) {
+  if (output.statusCode !== 204 && output.statusCode >= 300) {
     return de_PutMetadataCommandError(output, context);
   }
   const contents: any = map({

codegen/sdk-codegen/aws-models/ivs.json

@@ -1821,7 +1821,8 @@
         "smithy.api#documentation": "<p>Deletes the recording configuration for the specified ARN.</p>\n         <p>If you try to delete a recording configuration that is associated with a channel, you will\n      get an error (409 ConflictException). To avoid this, for all channels that reference the\n      recording configuration, first use <a>UpdateChannel</a> to set the\n        <code>recordingConfigurationArn</code> field to an empty string, then use\n      DeleteRecordingConfiguration.</p>",
         "smithy.api#http": {
           "method": "POST",
-          "uri": "/DeleteRecordingConfiguration"
+          "uri": "/DeleteRecordingConfiguration",
+          "code": 204
         }
       }
     },
@@ -3028,7 +3029,8 @@
         "smithy.api#documentation": "<p>Inserts metadata into the active stream of the specified channel. At most 5 requests per\n      second per channel are allowed, each with a maximum 1 KB payload. (If 5 TPS is not sufficient\n      for your needs, we recommend batching your data into a single PutMetadata call.) At most 155\n      requests per second per account are allowed. Also see <a href=\"https://docs.aws.amazon.com/ivs/latest/userguide/metadata.html\">Embedding Metadata within a Video Stream</a> in\n      the <i>Amazon IVS User Guide</i>.</p>",
         "smithy.api#http": {
           "method": "POST",
-          "uri": "/PutMetadata"
+          "uri": "/PutMetadata",
+          "code": 204
         }
       }
     },