hubspot-api-client 9.0.0 → 9.2.0

data/lib/hubspot/codegen/cms/hubdb/models/hub_db_table_v3_input.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field. HubDB tables now support `DRAFT` and `PUBLISHED` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/hub_db_table_v3_live_input.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field. HubDB tables now support `DRAFT` and `PUBLISHED` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/import_result.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field. HubDB tables now support `DRAFT` and `PUBLISHED` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/next_page.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field. HubDB tables now support `DRAFT` and `PUBLISHED` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/option.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field. HubDB tables now support `DRAFT` and `PUBLISHED` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/simple_user.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field. HubDB tables now support `DRAFT` and `PUBLISHED` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/{collection_response_with_total_hub_db_table_row_v3.rb → standard_error.rb}

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field. HubDB tables now support `DRAFT` and `PUBLISHED` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication.
 
 The version of the OpenAPI document: v3
 
@@ -15,28 +15,48 @@ require 'date'
 module Hubspot
   module Cms
     module Hubdb
-      class CollectionResponseWithTotalHubDbTableRowV3
-        attr_accessor :total
+      class StandardError
+        attr_accessor :status
 
-        attr_accessor :results
+        attr_accessor :id
 
-        attr_accessor :paging
+        attr_accessor :category
+
+        attr_accessor :sub_category
+
+        attr_accessor :message
+
+        attr_accessor :errors
+
+        attr_accessor :context
+
+        attr_accessor :links
 
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'total' => :'total',
-            :'results' => :'results',
-            :'paging' => :'paging'
+            :'status' => :'status',
+            :'id' => :'id',
+            :'category' => :'category',
+            :'sub_category' => :'subCategory',
+            :'message' => :'message',
+            :'errors' => :'errors',
+            :'context' => :'context',
+            :'links' => :'links'
           }
         end
 
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'total' => :'Integer',
-            :'results' => :'Array<HubDbTableRowV3>',
-            :'paging' => :'Paging'
+            :'status' => :'String',
+            :'id' => :'String',
+            :'category' => :'Object',
+            :'sub_category' => :'Object',
+            :'message' => :'String',
+            :'errors' => :'Array<ErrorDetail>',
+            :'context' => :'Hash<String, Array<String>>',
+            :'links' => :'Hash<String, String>'
           }
         end
 
@@ -50,29 +70,53 @@ module Hubspot
         # @param [Hash] attributes Model attributes in the form of hash
         def initialize(attributes = {})
           if (!attributes.is_a?(Hash))
-            fail ArgumentError, "The input argument (attributes) must be a hash in `Hubspot::Cms::Hubdb::CollectionResponseWithTotalHubDbTableRowV3` initialize method"
+            fail ArgumentError, "The input argument (attributes) must be a hash in `Hubspot::Cms::Hubdb::StandardError` initialize method"
           end
 
           # check to see if the attribute exists and convert string to symbol for hash key
           attributes = attributes.each_with_object({}) { |(k, v), h|
             if (!self.class.attribute_map.key?(k.to_sym))
-              fail ArgumentError, "`#{k}` is not a valid attribute in `Hubspot::Cms::Hubdb::CollectionResponseWithTotalHubDbTableRowV3`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
+              fail ArgumentError, "`#{k}` is not a valid attribute in `Hubspot::Cms::Hubdb::StandardError`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
             end
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'total')
-            self.total = attributes[:'total']
+          if attributes.key?(:'status')
+            self.status = attributes[:'status']
+          end
+
+          if attributes.key?(:'id')
+            self.id = attributes[:'id']
+          end
+
+          if attributes.key?(:'category')
+            self.category = attributes[:'category']
+          end
+
+          if attributes.key?(:'sub_category')
+            self.sub_category = attributes[:'sub_category']
+          end
+
+          if attributes.key?(:'message')
+            self.message = attributes[:'message']
           end
 
-          if attributes.key?(:'results')
-            if (value = attributes[:'results']).is_a?(Array)
-              self.results = value
+          if attributes.key?(:'errors')
+            if (value = attributes[:'errors']).is_a?(Array)
+              self.errors = value
             end
           end
 
-          if attributes.key?(:'paging')
-            self.paging = attributes[:'paging']
+          if attributes.key?(:'context')
+            if (value = attributes[:'context']).is_a?(Hash)
+              self.context = value
+            end
+          end
+
+          if attributes.key?(:'links')
+            if (value = attributes[:'links']).is_a?(Hash)
+              self.links = value
+            end
           end
         end
 
@@ -80,12 +124,28 @@ module Hubspot
         # @return Array for valid properties with the reasons
         def list_invalid_properties
           invalid_properties = Array.new
-          if @total.nil?
-            invalid_properties.push('invalid value for "total", total cannot be nil.')
+          if @status.nil?
+            invalid_properties.push('invalid value for "status", status cannot be nil.')
+          end
+
+          if @category.nil?
+            invalid_properties.push('invalid value for "category", category cannot be nil.')
+          end
+
+          if @message.nil?
+            invalid_properties.push('invalid value for "message", message cannot be nil.')
+          end
+
+          if @errors.nil?
+            invalid_properties.push('invalid value for "errors", errors cannot be nil.')
+          end
+
+          if @context.nil?
+            invalid_properties.push('invalid value for "context", context cannot be nil.')
           end
 
-          if @results.nil?
-            invalid_properties.push('invalid value for "results", results cannot be nil.')
+          if @links.nil?
+            invalid_properties.push('invalid value for "links", links cannot be nil.')
           end
 
           invalid_properties
@@ -94,8 +154,12 @@ module Hubspot
         # Check to see if the all the properties in the model are valid
         # @return true if the model is valid
         def valid?
-          return false if @total.nil?
-          return false if @results.nil?
+          return false if @status.nil?
+          return false if @category.nil?
+          return false if @message.nil?
+          return false if @errors.nil?
+          return false if @context.nil?
+          return false if @links.nil?
           true
         end
 
@@ -104,9 +168,14 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              total == o.total &&
-              results == o.results &&
-              paging == o.paging
+              status == o.status &&
+              id == o.id &&
+              category == o.category &&
+              sub_category == o.sub_category &&
+              message == o.message &&
+              errors == o.errors &&
+              context == o.context &&
+              links == o.links
         end
 
         # @see the `==` method
@@ -118,7 +187,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [total, results, paging].hash
+          [status, id, category, sub_category, message, errors, context, links].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/performance/api_client.rb

@@ -14,7 +14,7 @@ require 'date'
 require 'json'
 require 'logger'
 require 'tempfile'
-require 'faraday'
+require 'typhoeus'
 
 module Hubspot
   module Cms
@@ -48,62 +48,26 @@ module Hubspot
         # @return [Array<(Object, Integer, Hash)>] an array of 3 elements:
         #   the data deserialized from response body (could be nil), response status code and response headers.
         def call_api(http_method, path, opts = {})
-          ssl_options = {
-            :ca_file => @config.ssl_ca_file,
-            :verify => @config.ssl_verify,
-            :verify_mode => @config.ssl_verify_mode,
-            :client_cert => @config.ssl_client_cert,
-            :client_key => @config.ssl_client_key
-          }
+          request = build_request(http_method, path, opts)
+          response = request.run
 
-          connection = Faraday.new(:url => config.base_url, :ssl => ssl_options) do |conn|
-            conn.basic_auth(config.username, config.password)
-            if opts[:header_params]["Content-Type"] == "multipart/form-data"
-              conn.request :multipart
-              conn.request :url_encoded
-            end
-            conn.adapter(Faraday.default_adapter)
-            conn.options[:params_encoder] = Faraday::FlatParamsEncoder
-
-            # Errors handler settings
-            if !config.error_handler.empty?
-              config.error_handler.each do |statuses, opts|
-                statuses = statuses.is_a?(Integer) ? [statuses] : statuses
-                retry_options = {
-                  max: opts[:max_retries],
-                  interval: opts[:seconds_delay],
-                  retry_statuses: statuses,
-                  methods: %i[post delete get head options put],
-                  retry_block: -> (env, options, retries, exc) { opts[:retry_block].call }
-                }
-                conn.request :retry, retry_options
-              end
-            end
+          if @config.debugging
+            @config.logger.debug "HTTP response body ~BEGIN~\n#{response.body}\n~END~\n"
           end
 
-          begin
-            response = connection.public_send(http_method.to_sym.downcase) do |req|
-              build_request(http_method, path, req, opts)
-            end
-
-            if @config.debugging
-              @config.logger.debug "HTTP response body ~BEGIN~\n#{response.body}\n~END~\n"
-            end
-
-            unless response.success?
-              if response.status == 0
-                # Errors from libcurl will be made visible here
-                fail ApiError.new(:code => 0,
-                                  :message => response.return_message)
-              else
-                fail ApiError.new(:code => response.status,
-                                  :response_headers => response.headers,
-                                  :response_body => response.body),
-                     response.reason_phrase
-              end
+          unless response.success?
+            if response.timed_out?
+              fail ApiError.new('Connection timed out')
+            elsif response.code == 0
+              # Errors from libcurl will be made visible here
+              fail ApiError.new(:code => 0,
+                                :message => response.return_message)
+            else
+              fail ApiError.new(:code => response.code,
+                                :response_headers => response.headers,
+                                :response_body => response.body),
+                   response.status_message
             end
-          rescue Faraday::TimeoutError
-            fail ApiError.new('Connection timed out')
           end
 
           if opts[:return_type]
@@ -111,7 +75,7 @@ module Hubspot
           else
             data = nil
           end
-          return data, response.status, response.headers
+          return data, response.code, response.headers
         end
 
         # Builds the HTTP request
@@ -123,7 +87,7 @@ module Hubspot
         # @option opts [Hash] :form_params Query parameters
         # @option opts [Object] :body HTTP body (JSON/XML)
         # @return [Typhoeus::Request] A Typhoeus Request
-        def build_request(http_method, path, request, opts = {})
+        def build_request(http_method, path, opts = {})
           url = build_request_url(path)
           http_method = http_method.to_sym.downcase
 
@@ -133,15 +97,25 @@ module Hubspot
 
           update_params_for_auth! header_params, query_params, opts[:auth_names]
 
+          # set ssl_verifyhosts option based on @config.verify_ssl_host (true/false)
+          _verify_ssl_host = @config.verify_ssl_host ? 2 : 0
+
           req_opts = {
             :method => http_method,
             :headers => header_params,
             :params => query_params,
             :params_encoding => @config.params_encoding,
             :timeout => @config.timeout,
+            :ssl_verifypeer => @config.verify_ssl,
+            :ssl_verifyhost => _verify_ssl_host,
+            :sslcert => @config.cert_file,
+            :sslkey => @config.key_file,
             :verbose => @config.debugging
           }
 
+          # set custom cert, if provided
+          req_opts[:cainfo] = @config.ssl_ca_cert if @config.ssl_ca_cert
+
           if [:post, :patch, :put, :delete].include?(http_method)
             req_body = build_request_body(header_params, form_params, opts[:body])
             req_opts.update :body => req_body
@@ -149,10 +123,8 @@ module Hubspot
               @config.logger.debug "HTTP request body param ~BEGIN~\n#{req_body}\n~END~\n"
             end
           end
-          request.headers = header_params
-          request.body = req_body
-          request.url url
-          request.params = query_params
+
+          request = Typhoeus::Request.new(url, req_opts)
           download_file(request) if opts[:return_type] == 'File'
           request
         end
@@ -165,17 +137,13 @@ module Hubspot
         # @return [String] HTTP body data in the form of string
         def build_request_body(header_params, form_params, body)
           # http form
-          if header_params['Content-Type'] == 'application/x-www-form-urlencoded'
-            data = URI.encode_www_form(form_params)
-          elsif header_params['Content-Type'] == 'multipart/form-data'
+          if header_params['Content-Type'] == 'application/x-www-form-urlencoded' ||
+              header_params['Content-Type'] == 'multipart/form-data'
             data = {}
             form_params.each do |key, value|
               case value
-              when ::File, ::Tempfile
-                # TODO hardcode to application/octet-stream, need better way to detect content type
-                data[key] = Faraday::UploadIO.new(value.path, 'application/octet-stream', value.path)
-              when ::Array, nil
-                # let Faraday handle Array and nil parameters
+              when ::File, ::Array, nil
+                # let typhoeus handle File, Array and nil parameters
                 data[key] = value
               else
                 data[key] = value.to_s

data/lib/hubspot/codegen/cms/performance/configuration.rb

@@ -88,28 +88,33 @@ module Hubspot
         # @note Do NOT set it to false in production code, otherwise you would face multiple types of cryptographic attacks.
         #
         # @return [true, false]
-        attr_accessor :ssl_verify
+        attr_accessor :verify_ssl
 
         ### TLS/SSL setting
-        # Any `OpenSSL::SSL::` constant (see https://ruby-doc.org/stdlib-2.5.1/libdoc/openssl/rdoc/OpenSSL/SSL.html)
+        # Set this to false to skip verifying SSL host name
+        # Default to true.
         #
         # @note Do NOT set it to false in production code, otherwise you would face multiple types of cryptographic attacks.
         #
-        attr_accessor :ssl_verify_mode
+        # @return [true, false]
+        attr_accessor :verify_ssl_host
 
         ### TLS/SSL setting
         # Set this to customize the certificate file to verify the peer.
         #
         # @return [String] the path to the certificate file
-        attr_accessor :ssl_ca_file
+        #
+        # @see The `cainfo` option of Typhoeus, `--cert` option of libcurl. Related source code:
+        # https://github.com/typhoeus/typhoeus/blob/master/lib/typhoeus/easy_factory.rb#L145
+        attr_accessor :ssl_ca_cert
 
         ### TLS/SSL setting
         # Client certificate file (for client certificate)
-        attr_accessor :ssl_client_cert
+        attr_accessor :cert_file
 
         ### TLS/SSL setting
         # Client private key file (for client certificate)
-        attr_accessor :ssl_client_key
+        attr_accessor :key_file
 
         # Set this to customize parameters encoding of array parameter with multi collectionFormat.
         # Default to nil.
@@ -132,11 +137,11 @@ module Hubspot
           @api_key_prefix = {}
           @timeout = 0
           @client_side_validation = true
-          @ssl_verify = true
-          @ssl_verify_mode = nil
-          @ssl_ca_file = nil
-          @ssl_client_cert = nil
-          @ssl_client_key = nil
+          @verify_ssl = true
+          @verify_ssl_host = true
+          @params_encoding = nil
+          @cert_file = nil
+          @key_file = nil
           @debugging = false
           @inject_format = false
           @force_ending_format = false