incident_io_api 2.33.0 → 2.35.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 845b36fa19dcf1a1650ccd79b5da5a234ff87e56ead4c93cc9f656f07a10e189
-  data.tar.gz: e74685531971721e27fccd8680890ffab380a30b143433dd41fbf600a81450a4
+  metadata.gz: bf122d0ff432c2d94e4b25f4ee36fb7932755a85991d29801016fbaf5c0eb645
+  data.tar.gz: e932063b915619780f735f224e57c9644888106406aa4afeb55448c1ecb2be13
 SHA512:
-  metadata.gz: cd4b1edce8e3735ab6c7cfd750db7321d23d957886656e85716d9bea3dedefa69fe10967c4971be578a8064ac324e49fc13a6699c76cb8b3bd40135d3552ddb7
-  data.tar.gz: 34bbec0f6f701ca96c0b670ed3b2666dc454118427e8bcdd907cfd29b7045bf1eba1afd741370137fedf2c7de5da734451df7c81ced606a7785ed0247a9be317
+  metadata.gz: 55f2feec8055ddea58336ce8f48de754983ffa36385389fa3634790b8bbd7d58e77d76e0aa285c2a89f0bcd509ddd82ed941fc4e91a28f7b5d48117cddf669ff
+  data.tar.gz: 377ef506a8f9ece47979b54e290c6b80a407b32b96feec4442b669c2d2b024c9d9753ab4f1a5930f153cc020627722dbaf77acf70a4c53b216118a7ac8524422

data/lib/incident_io/api/escalations_v2_api.rb

@@ -519,7 +519,7 @@ module IncidentIo
     end
 
     # ReassignEscalation Escalations V2
-    # Reassign an escalation to a different escalation path or set of users.  Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original's title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it.  You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie.  By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to.  An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response.  To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope.  If your API key's permissions are scoped to teams, the escalation you're reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
+    # Reassign an escalation to a different escalation path or set of users.  Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original's title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it.  You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie.  By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to.  An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response.  To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key.  If your API key's permissions are scoped to teams, the escalation you're reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
     # @param escalation_id [String] The ID of the escalation to reassign
     # @param escalations_reassign_escalation_payload_v2 [EscalationsReassignEscalationPayloadV2] 
     # @param [Hash] opts the optional parameters
@@ -530,7 +530,7 @@ module IncidentIo
     end
 
     # ReassignEscalation Escalations V2
-    # Reassign an escalation to a different escalation path or set of users.  Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original's title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it.  You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie.  By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to.  An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response.  To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope.  If your API key's permissions are scoped to teams, the escalation you're reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
+    # Reassign an escalation to a different escalation path or set of users.  Use this when a page reached the wrong people. Reassigning creates a new escalation aimed at the targets you give, linked back to the original, and carries over the original's title, description, priority, incident and alert so the page stays attached to the same alert and acknowledgements keep grouping under it.  You must provide either an escalation_path_id OR user_ids, but not both. Both name incident.io escalation paths and users, so an escalation cannot be reassigned to an external escalator such as PagerDuty or Opsgenie.  By default the original escalation is resolved, so the first targets stop being paged. Pass resolve_original=false to leave it running alongside the new one. Resolving the original additionally needs the \"escalations.respond\" permission, since it stops a page someone else may be responding to.  An escalation can only be reassigned once: calling this again for the same escalation is rejected. Retrying a request whose response you never saw is safe in the sense that matters — a reassignment that already happened is never repeated, so nobody is paged twice — but the retry is rejected rather than returning the escalation the first call created, so keep the ID from the original response.  To use this API, you will need an API key with the \"Create and manage escalations\" permission. The reassignment is attributed to the key; to attribute it to one of your users instead, set the X-Incident-User header, which needs the \"api_keys.act_on_behalf_of_users\" scope and no team permissions on the key.  If your API key's permissions are scoped to teams, the escalation you're reassigning must be owned by one of those teams, and you can only reassign via an escalation path one of them owns. Reassigning directly to user_ids needs the permission at the account level, because an escalation aimed at a person has no owning team.
     # @param escalation_id [String] The ID of the escalation to reassign
     # @param escalations_reassign_escalation_payload_v2 [EscalationsReassignEscalationPayloadV2] 
     # @param [Hash] opts the optional parameters

data/lib/incident_io/api/status_page_components_v2_api.rb

@@ -20,7 +20,7 @@ module IncidentIo
       @api_client = api_client
     end
     # Create Status Page Components V2
-    # Create a status page component. Placement on a page is controlled separately via status page structures.
+    # Create a status page component. Placement on a page is controlled separately via status page structures.  This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
     # @param status_page_components_create_payload_v2 [StatusPageComponentsCreatePayloadV2] 
     # @param [Hash] opts the optional parameters
     # @return [StatusPageComponentsCreateResultV2]
@@ -30,7 +30,7 @@ module IncidentIo
     end
 
     # Create Status Page Components V2
-    # Create a status page component. Placement on a page is controlled separately via status page structures.
+    # Create a status page component. Placement on a page is controlled separately via status page structures.  This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
     # @param status_page_components_create_payload_v2 [StatusPageComponentsCreatePayloadV2] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(StatusPageComponentsCreateResultV2, Integer, Hash)>] StatusPageComponentsCreateResultV2 data, response status code and response headers
@@ -88,7 +88,7 @@ module IncidentIo
     end
 
     # Destroy Status Page Components V2
-    # Archive a status page component.
+    # Archive a status page component.  This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
     # @param id [String] Unique identifier of the status page component
     # @param [Hash] opts the optional parameters
     # @return [nil]
@@ -98,7 +98,7 @@ module IncidentIo
     end
 
     # Destroy Status Page Components V2
-    # Archive a status page component.
+    # Archive a status page component.  This endpoint requires an API key with the \&quot;Manage organization settings (e.g. custom fields)\&quot; scope.
     # @param id [String] Unique identifier of the status page component
     # @param [Hash] opts the optional parameters
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
@@ -271,7 +271,7 @@ module IncidentIo
     end
 
     # Update Status Page Components V2
-    # Update a status page component's name and description.
+    # Update a status page component's name and description.  This endpoint requires an API key with the \"Manage organization settings (e.g. custom fields)\" scope.
     # @param id [String] Unique identifier of the status page component
     # @param status_page_components_update_payload_v2 [StatusPageComponentsUpdatePayloadV2] 
     # @param [Hash] opts the optional parameters
@@ -282,7 +282,7 @@ module IncidentIo
     end
 
     # Update Status Page Components V2
-    # Update a status page component&#39;s name and description.
+    # Update a status page component&#39;s name and description.  This endpoint requires an API key with the \&quot;Manage organization settings (e.g. custom fields)\&quot; scope.
     # @param id [String] Unique identifier of the status page component
     # @param status_page_components_update_payload_v2 [StatusPageComponentsUpdatePayloadV2] 
     # @param [Hash] opts the optional parameters

data/lib/incident_io/models/audit_logs_connector_config_archived_v1.rb

@@ -0,0 +1,300 @@
+=begin
+#incident.io
+
+#Ruby client for the incident.io API.
+
+The version of the OpenAPI document: 1.0.0
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.25.0
+
+=end
+
+require 'date'
+require 'time'
+
+module IncidentIo
+  class AuditLogsConnectorConfigArchivedV1 < ApiModelBase
+    # The type of log entry that this is
+    attr_accessor :action
+
+    attr_accessor :actor
+
+    attr_accessor :context
+
+    # When the entry occurred
+    attr_accessor :occurred_at
+
+    # The custom field that was created
+    attr_accessor :targets
+
+    # Which version the event is
+    attr_accessor :version
+
+    # Attribute mapping from ruby-style variable name to JSON key.
+    def self.attribute_map
+      {
+        :'action' => :'action',
+        :'actor' => :'actor',
+        :'context' => :'context',
+        :'occurred_at' => :'occurred_at',
+        :'targets' => :'targets',
+        :'version' => :'version'
+      }
+    end
+
+    # Returns attribute mapping this model knows about
+    def self.acceptable_attribute_map
+      attribute_map
+    end
+
+    # Returns all the JSON keys this model knows about
+    def self.acceptable_attributes
+      acceptable_attribute_map.values
+    end
+
+    # Attribute type mapping.
+    def self.openapi_types
+      {
+        :'action' => :'String',
+        :'actor' => :'AuditLogActorV2',
+        :'context' => :'AuditLogEntryContextV2',
+        :'occurred_at' => :'Time',
+        :'targets' => :'Array<AuditLogTargetV2>',
+        :'version' => :'Integer'
+      }
+    end
+
+    # List of attributes with nullable: true
+    def self.openapi_nullable
+      Set.new([
+      ])
+    end
+
+    # Initializes the object
+    # @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 `IncidentIo::AuditLogsConnectorConfigArchivedV1` initialize method"
+      end
+
+      # check to see if the attribute exists and convert string to symbol for hash key
+      acceptable_attribute_map = self.class.acceptable_attribute_map
+      attributes = attributes.each_with_object({}) { |(k, v), h|
+        if (!acceptable_attribute_map.key?(k.to_sym))
+          fail ArgumentError, "`#{k}` is not a valid attribute in `IncidentIo::AuditLogsConnectorConfigArchivedV1`. Please check the name to make sure it's valid. List of attributes: " + acceptable_attribute_map.keys.inspect
+        end
+        h[k.to_sym] = v
+      }
+
+      if attributes.key?(:'action')
+        self.action = attributes[:'action']
+      else
+        self.action = nil
+      end
+
+      if attributes.key?(:'actor')
+        self.actor = attributes[:'actor']
+      else
+        self.actor = nil
+      end
+
+      if attributes.key?(:'context')
+        self.context = attributes[:'context']
+      else
+        self.context = nil
+      end
+
+      if attributes.key?(:'occurred_at')
+        self.occurred_at = attributes[:'occurred_at']
+      else
+        self.occurred_at = nil
+      end
+
+      if attributes.key?(:'targets')
+        if (value = attributes[:'targets']).is_a?(Array)
+          self.targets = value
+        end
+      else
+        self.targets = nil
+      end
+
+      if attributes.key?(:'version')
+        self.version = attributes[:'version']
+      else
+        self.version = nil
+      end
+    end
+
+    # Show invalid properties with the reasons. Usually used together with valid?
+    # @return Array for valid properties with the reasons
+    def list_invalid_properties
+      warn '[DEPRECATED] the `list_invalid_properties` method is obsolete'
+      invalid_properties = Array.new
+      if @action.nil?
+        invalid_properties.push('invalid value for "action", action cannot be nil.')
+      end
+
+      if @actor.nil?
+        invalid_properties.push('invalid value for "actor", actor cannot be nil.')
+      end
+
+      if @context.nil?
+        invalid_properties.push('invalid value for "context", context cannot be nil.')
+      end
+
+      if @occurred_at.nil?
+        invalid_properties.push('invalid value for "occurred_at", occurred_at cannot be nil.')
+      end
+
+      if @targets.nil?
+        invalid_properties.push('invalid value for "targets", targets cannot be nil.')
+      end
+
+      if @version.nil?
+        invalid_properties.push('invalid value for "version", version cannot be nil.')
+      end
+
+      invalid_properties
+    end
+
+    # Check to see if the all the properties in the model are valid
+    # @return true if the model is valid
+    def valid?
+      warn '[DEPRECATED] the `valid?` method is obsolete'
+      return false if @action.nil?
+      return false if @actor.nil?
+      return false if @context.nil?
+      return false if @occurred_at.nil?
+      return false if @targets.nil?
+      return false if @version.nil?
+      true
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] action Value to be assigned
+    def action=(action)
+      if action.nil?
+        fail ArgumentError, 'action cannot be nil'
+      end
+
+      @action = action
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] actor Value to be assigned
+    def actor=(actor)
+      if actor.nil?
+        fail ArgumentError, 'actor cannot be nil'
+      end
+
+      @actor = actor
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] context Value to be assigned
+    def context=(context)
+      if context.nil?
+        fail ArgumentError, 'context cannot be nil'
+      end
+
+      @context = context
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] occurred_at Value to be assigned
+    def occurred_at=(occurred_at)
+      if occurred_at.nil?
+        fail ArgumentError, 'occurred_at cannot be nil'
+      end
+
+      @occurred_at = occurred_at
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] targets Value to be assigned
+    def targets=(targets)
+      if targets.nil?
+        fail ArgumentError, 'targets cannot be nil'
+      end
+
+      @targets = targets
+    end
+
+    # Custom attribute writer method with validation
+    # @param [Object] version Value to be assigned
+    def version=(version)
+      if version.nil?
+        fail ArgumentError, 'version cannot be nil'
+      end
+
+      @version = version
+    end
+
+    # Checks equality by comparing each attribute.
+    # @param [Object] Object to be compared
+    def ==(o)
+      return true if self.equal?(o)
+      self.class == o.class &&
+          action == o.action &&
+          actor == o.actor &&
+          context == o.context &&
+          occurred_at == o.occurred_at &&
+          targets == o.targets &&
+          version == o.version
+    end
+
+    # @see the `==` method
+    # @param [Object] Object to be compared
+    def eql?(o)
+      self == o
+    end
+
+    # Calculates hash code according to all attributes.
+    # @return [Integer] Hash code
+    def hash
+      [action, actor, context, occurred_at, targets, version].hash
+    end
+
+    # Builds the object from hash
+    # @param [Hash] attributes Model attributes in the form of hash
+    # @return [Object] Returns the model itself
+    def self.build_from_hash(attributes)
+      return nil unless attributes.is_a?(Hash)
+      attributes = attributes.transform_keys(&:to_sym)
+      transformed_hash = {}
+      openapi_types.each_pair do |key, type|
+        if attributes.key?(attribute_map[key]) && attributes[attribute_map[key]].nil?
+          transformed_hash["#{key}"] = nil
+        elsif type =~ /\AArray<(.*)>/i
+          # check to ensure the input is an array given that the attribute
+          # is documented as an array but the input is not
+          if attributes[attribute_map[key]].is_a?(Array)
+            transformed_hash["#{key}"] = attributes[attribute_map[key]].map { |v| _deserialize($1, v) }
+          end
+        elsif !attributes[attribute_map[key]].nil?
+          transformed_hash["#{key}"] = _deserialize(type, attributes[attribute_map[key]])
+        end
+      end
+      new(transformed_hash)
+    end
+
+    # Returns the object in the form of hash
+    # @return [Hash] Returns the object in the form of hash
+    def to_hash
+      hash = {}
+      self.class.attribute_map.each_pair do |attr, param|
+        value = self.send(attr)
+        if value.nil?
+          is_nullable = self.class.openapi_nullable.include?(attr)
+          next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
+        end
+
+        hash[param] = _to_hash(value)
+      end
+      hash
+    end
+
+  end
+
+end

data/lib/incident_io/version.rb

@@ -4,5 +4,5 @@ module IncidentIo
   # The release workflow sets this before building, so it tracks whatever we
   # last published. Listed in .openapi-generator-ignore so regeneration can't
   # reset it.
-  VERSION = "2.33.0"
+  VERSION = "2.35.0"
 end

data/lib/incident_io.rb

@@ -344,6 +344,7 @@ IncidentIo.autoload :AuditLogsCatalogTypeDeletedV2, 'incident_io/models/audit_lo
 IncidentIo.autoload :AuditLogsCatalogTypeUpdatedV1, 'incident_io/models/audit_logs_catalog_type_updated_v1'
 IncidentIo.autoload :AuditLogsCatalogTypeUpdatedV2, 'incident_io/models/audit_logs_catalog_type_updated_v2'
 IncidentIo.autoload :AuditLogsCodeRepositoryAccessedV1, 'incident_io/models/audit_logs_code_repository_accessed_v1'
+IncidentIo.autoload :AuditLogsConnectorConfigArchivedV1, 'incident_io/models/audit_logs_connector_config_archived_v1'
 IncidentIo.autoload :AuditLogsConnectorConfigCreatedV1, 'incident_io/models/audit_logs_connector_config_created_v1'
 IncidentIo.autoload :AuditLogsConnectorConfigCreatedV2, 'incident_io/models/audit_logs_connector_config_created_v2'
 IncidentIo.autoload :AuditLogsConnectorConfigTokenGeneratedV1, 'incident_io/models/audit_logs_connector_config_token_generated_v1'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: incident_io_api
 version: !ruby/object:Gem::Version
-  version: 2.33.0
+  version: 2.35.0
 platform: ruby
 authors:
 - incident.io
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-10-27 00:00:00.000000000 Z
+date: 2026-10-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday
@@ -472,6 +472,7 @@ files:
 - lib/incident_io/models/audit_logs_catalog_type_updated_v1.rb
 - lib/incident_io/models/audit_logs_catalog_type_updated_v2.rb
 - lib/incident_io/models/audit_logs_code_repository_accessed_v1.rb
+- lib/incident_io/models/audit_logs_connector_config_archived_v1.rb
 - lib/incident_io/models/audit_logs_connector_config_created_v1.rb
 - lib/incident_io/models/audit_logs_connector_config_created_v2.rb
 - lib/incident_io/models/audit_logs_connector_config_token_generated_v1.rb