event_destinations_client.rb in ngrok-api-0.21.0

- old
+ new

@@ -1,7 +1,9 @@
 # frozen_string_literal: true
 
+# Code generated for API Clients. DO NOT EDIT.
+
 module NgrokAPI
   module Services
     ##
     # https://ngrok.com/docs/api#api-event-destinations
     class EventDestinationsClient
@@ -16,12 +18,11 @@
         @client = client
       end
 
       ##
       # Create a new Event Destination. It will not apply to anything until it is
-      # associated with an Event Stream, and that Event Stream is associated with an
-      # Endpoint Config.
+      # associated with an Event Subscription.
       #
       # @param [string] metadata Arbitrary user-defined machine-readable data of this Event Destination. Optional, max 4096 bytes.
       # @param [string] description Human-readable description of the Event Destination. Optional, max 255 bytes.
       # @param [string] format The output format you would like to serialize events into when sending to their target. Currently the only accepted value is ``JSON``.
       # @param [EventTarget] target An object that encapsulates where and how to send your events. An event destination must contain exactly one of the following objects, leaving the rest null: ``kinesis``, ``firehose``, ``cloudwatch_logs``, or ``s3``.
@@ -41,11 +42,10 @@
         NgrokAPI::Models::EventDestination.new(client: self, attrs: result)
       end
 
       ##
       # Create a new Event Destination. It will not apply to anything until it is
-      # associated with an Event Stream, and that Event Stream is associated with an
-      # Endpoint Config.
+      # associated with an Event Subscription.
       # Throws an exception if API error.
       #
       # @param [string] metadata Arbitrary user-defined machine-readable data of this Event Destination. Optional, max 4096 bytes.
       # @param [string] description Human-readable description of the Event Destination. Optional, max 255 bytes.
       # @param [string] format The output format you would like to serialize events into when sending to their target. Currently the only accepted value is ``JSON``.