svix 0.84.0 → 0.84.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ed9c9d859e17d5d5c9959d79fd8228e2a2012bdba0c0987a31cec3231554cae3
-  data.tar.gz: 6c6ddd4957b750913299dfba5ba4360084955411d105f74edd63f4dfce3d8b3b
+  metadata.gz: 8eead298961cd2df35494446c3135b8ed242129eb4e7b19148392509aee5ece2
+  data.tar.gz: 7112abc7d05750ae9252a8b22416cf03b046f3e0f8fb35d75779118b1c29156f
 SHA512:
-  metadata.gz: 174d5c27daea11288a2ef9d6da00cfdf77a344ab671319c972e6c815349a3cb37fffc97731b52dfb33797ce3bba549e197fd0c03fd2f4efb3c3a0efed24ec59c
-  data.tar.gz: 37f95254ab41f1884bf0c1a25c254c04c95c79466f92b3a6e7967b9bef91724d76c3a98c1c98e2310136ab444f1a9f5fde13d4d255da5552f644ecbf999bb21b
+  metadata.gz: 11cd816097c5b0335e29c463c0c820fd232353d6491b68eeb3b7fe9c3536791c32c7b722741034a5b5c67e74d3cc9cb2ab5194fc327c54f59404cc73f86d5492
+  data.tar.gz: a47f0fd5275858c4a1c82767d73d7b6b4ee1f84abc9307bd6d2d0e65bf2fe9a94b812830ee1e7dff9df385109cbf50cbdb44f6a7be059f0ec01803a5c0b9a4ec

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    svix (0.84.0)
+    svix (0.84.1)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM

data/lib/svix/api/application_api.rb

@@ -3,7 +3,7 @@
 
 #Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`.  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
 
-The version of the OpenAPI document: 1.4
+The version of the OpenAPI document: 1.4.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0
@@ -25,7 +25,7 @@ module Svix
     # @param _until [Time] 
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :limit  (default to 50)
-    # @option opts [String] :iterator 
+    # @option opts [String] :iterator The app&#39;s ID
     # @return [ListResponseApplicationStats]
     def get_app_usage_stats_api_v1_app_stats_usage_get(since, _until, opts = {})
       data, _status_code, _headers = get_app_usage_stats_api_v1_app_stats_usage_get_with_http_info(since, _until, opts)
@@ -38,7 +38,7 @@ module Svix
     # @param _until [Time] 
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :limit 
-    # @option opts [String] :iterator 
+    # @option opts [String] :iterator The app&#39;s ID
     # @return [Array<(ListResponseApplicationStats, Integer, Hash)>] ListResponseApplicationStats data, response status code and response headers
     def get_app_usage_stats_api_v1_app_stats_usage_get_with_http_info(since, _until, opts = {})
       if @api_client.config.debugging
@@ -81,7 +81,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'ListResponseApplicationStats'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"ApplicationApi.get_app_usage_stats_api_v1_app_stats_usage_get",
@@ -102,7 +102,7 @@ module Svix
 
     # Patch Application
     # Partially update an application.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param application_patch [ApplicationPatch] 
     # @param [Hash] opts the optional parameters
     # @return [ApplicationOut]
@@ -113,7 +113,7 @@ module Svix
 
     # Patch Application
     # Partially update an application.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param application_patch [ApplicationPatch] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(ApplicationOut, Integer, Hash)>] ApplicationOut data, response status code and response headers
@@ -165,7 +165,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'ApplicationOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"ApplicationApi.patch_application",
@@ -236,7 +236,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'ApplicationOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"ApplicationApi.v1_application_create",
@@ -257,7 +257,7 @@ module Svix
 
     # Delete Application
     # Delete an application.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param [Hash] opts the optional parameters
     # @return [nil]
     def v1_application_delete(app_id, opts = {})
@@ -267,7 +267,7 @@ module Svix
 
     # Delete Application
     # Delete an application.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param [Hash] opts the optional parameters
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
     def v1_application_delete_with_http_info(app_id, opts = {})
@@ -312,7 +312,7 @@ module Svix
       return_type = opts[:debug_return_type]
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"ApplicationApi.v1_application_delete",
@@ -333,7 +333,7 @@ module Svix
 
     # Get Application
     # Get an application.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param [Hash] opts the optional parameters
     # @return [ApplicationOut]
     def v1_application_get(app_id, opts = {})
@@ -343,7 +343,7 @@ module Svix
 
     # Get Application
     # Get an application.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param [Hash] opts the optional parameters
     # @return [Array<(ApplicationOut, Integer, Hash)>] ApplicationOut data, response status code and response headers
     def v1_application_get_with_http_info(app_id, opts = {})
@@ -388,7 +388,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'ApplicationOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"ApplicationApi.v1_application_get",
@@ -411,7 +411,7 @@ module Svix
     # Get basic statistics for the application
     # @param since [Time] 
     # @param _until [Time] 
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param [Hash] opts the optional parameters
     # @return [ApplicationStats]
     def v1_application_get_stats(since, _until, app_id, opts = {})
@@ -423,7 +423,7 @@ module Svix
     # Get basic statistics for the application
     # @param since [Time] 
     # @param _until [Time] 
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param [Hash] opts the optional parameters
     # @return [Array<(ApplicationStats, Integer, Hash)>] ApplicationStats data, response status code and response headers
     def v1_application_get_stats_with_http_info(since, _until, app_id, opts = {})
@@ -478,7 +478,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'ApplicationStats'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"ApplicationApi.v1_application_get_stats",
@@ -501,7 +501,7 @@ module Svix
     # List of all the organization's applications.
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :limit 
-    # @option opts [String] :iterator 
+    # @option opts [String] :iterator The app&#39;s ID
     # @option opts [Ordering] :order 
     # @return [ListResponseApplicationOut]
     def v1_application_list(opts = {})
@@ -513,15 +513,19 @@ module Svix
     # List of all the organization&#39;s applications.
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :limit 
-    # @option opts [String] :iterator 
+    # @option opts [String] :iterator The app&#39;s ID
     # @option opts [Ordering] :order 
     # @return [Array<(ListResponseApplicationOut, Integer, Hash)>] ListResponseApplicationOut data, response status code and response headers
     def v1_application_list_with_http_info(opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: ApplicationApi.v1_application_list ...'
       end
-      if @api_client.config.client_side_validation && !opts[:'limit'].nil? && opts[:'limit'] < 0
-        fail ArgumentError, 'invalid value for "opts[:"limit"]" when calling ApplicationApi.v1_application_list, must be greater than or equal to 0.'
+      if @api_client.config.client_side_validation && !opts[:'limit'].nil? && opts[:'limit'] > 250
+        fail ArgumentError, 'invalid value for "opts[:"limit"]" when calling ApplicationApi.v1_application_list, must be smaller than or equal to 250.'
+      end
+
+      if @api_client.config.client_side_validation && !opts[:'limit'].nil? && opts[:'limit'] < 1
+        fail ArgumentError, 'invalid value for "opts[:"limit"]" when calling ApplicationApi.v1_application_list, must be greater than or equal to 1.'
       end
 
       # resource path
@@ -548,7 +552,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'ListResponseApplicationOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"ApplicationApi.v1_application_list",
@@ -569,7 +573,7 @@ module Svix
 
     # Update Application
     # Update an application.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param application_in [ApplicationIn] 
     # @param [Hash] opts the optional parameters
     # @return [ApplicationOut]
@@ -580,7 +584,7 @@ module Svix
 
     # Update Application
     # Update an application.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param application_in [ApplicationIn] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(ApplicationOut, Integer, Hash)>] ApplicationOut data, response status code and response headers
@@ -632,7 +636,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'ApplicationOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"ApplicationApi.v1_application_update",

data/lib/svix/api/authentication_api.rb

@@ -3,7 +3,7 @@
 
 #Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`.  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
 
-The version of the OpenAPI document: 1.4
+The version of the OpenAPI document: 1.4.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0
@@ -19,9 +19,9 @@ module Svix
     def initialize(api_client = ApiClient.default)
       @api_client = api_client
     end
-    # App Portal Access
+    # Get Consumer App Portal Access
     # Use this function to get magic links (and authentication codes) for connecting your users to the Consumer Application Portal.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param app_portal_access_in [AppPortalAccessIn] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key The request&#39;s idempotency key
@@ -31,9 +31,9 @@ module Svix
       data
     end
 
-    # App Portal Access
+    # Get Consumer App Portal Access
     # Use this function to get magic links (and authentication codes) for connecting your users to the Consumer Application Portal.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param app_portal_access_in [AppPortalAccessIn] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key The request&#39;s idempotency key
@@ -87,7 +87,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'AppPortalAccessOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"AuthenticationApi.v1_authentication_app_portal_access",
@@ -108,7 +108,7 @@ module Svix
 
     # Dashboard Access
     # DEPRECATED: Please use `app-portal-access` instead.  Use this function to get magic links (and authentication codes) for connecting your users to the Consumer Application Portal.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key The request&#39;s idempotency key
     # @return [DashboardAccessOut]
@@ -119,7 +119,7 @@ module Svix
 
     # Dashboard Access
     # DEPRECATED: Please use &#x60;app-portal-access&#x60; instead.  Use this function to get magic links (and authentication codes) for connecting your users to the Consumer Application Portal.
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key The request&#39;s idempotency key
     # @return [Array<(DashboardAccessOut, Integer, Hash)>] DashboardAccessOut data, response status code and response headers
@@ -166,7 +166,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'DashboardAccessOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"AuthenticationApi.v1_authentication_dashboard_access",
@@ -187,7 +187,7 @@ module Svix
 
     # Expire All
     # Expire all of the tokens associated with a specific Application
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param application_token_expire_in [ApplicationTokenExpireIn] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key The request&#39;s idempotency key
@@ -199,7 +199,7 @@ module Svix
 
     # Expire All
     # Expire all of the tokens associated with a specific Application
-    # @param app_id [String] 
+    # @param app_id [String] The app&#39;s ID or UID
     # @param application_token_expire_in [ApplicationTokenExpireIn] 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :idempotency_key The request&#39;s idempotency key
@@ -253,7 +253,7 @@ module Svix
       return_type = opts[:debug_return_type]
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"AuthenticationApi.v1_authentication_expire_all",
@@ -313,7 +313,7 @@ module Svix
       return_type = opts[:debug_return_type]
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"AuthenticationApi.v1_authentication_logout",

data/lib/svix/api/background_tasks_api.rb

@@ -3,7 +3,7 @@
 
 #Welcome to the Svix API documentation!  Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)  # Introduction  This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).  ## Main concepts  In Svix you have four important entities you will be interacting with:  - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint.   ## Authentication  Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`.  <SecurityDefinitions />   ## Code samples  The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/).   ## Idempotency  Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response.  To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions.  Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result.  Please note that idempotency is only supported for `POST` requests.   ## Cross-Origin Resource Sharing  This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site. 
 
-The version of the OpenAPI document: 1.4
+The version of the OpenAPI document: 1.4.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.0
@@ -63,7 +63,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'BackgroundTaskOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"BackgroundTasksApi.get_background_task",
@@ -109,8 +109,12 @@ module Svix
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: BackgroundTasksApi.list_background_tasks ...'
       end
-      if @api_client.config.client_side_validation && !opts[:'limit'].nil? && opts[:'limit'] < 0
-        fail ArgumentError, 'invalid value for "opts[:"limit"]" when calling BackgroundTasksApi.list_background_tasks, must be greater than or equal to 0.'
+      if @api_client.config.client_side_validation && !opts[:'limit'].nil? && opts[:'limit'] > 250
+        fail ArgumentError, 'invalid value for "opts[:"limit"]" when calling BackgroundTasksApi.list_background_tasks, must be smaller than or equal to 250.'
+      end
+
+      if @api_client.config.client_side_validation && !opts[:'limit'].nil? && opts[:'limit'] < 1
+        fail ArgumentError, 'invalid value for "opts[:"limit"]" when calling BackgroundTasksApi.list_background_tasks, must be greater than or equal to 1.'
       end
 
       # resource path
@@ -139,7 +143,7 @@ module Svix
       return_type = opts[:debug_return_type] || 'ListResponseBackgroundTaskOut'
 
       # auth_names
-      auth_names = opts[:debug_auth_names] || []
+      auth_names = opts[:debug_auth_names] || ['HTTPBearer']
 
       new_options = opts.merge(
         :operation => :"BackgroundTasksApi.list_background_tasks",