launchdarkly_api 8.0.0 → 10.0.0

data/docs/ScheduleConditionInputRep.md

@@ -6,9 +6,9 @@
 | ---- | ---- | ----------- | ----- |
 | **schedule_kind** | **String** |  | [optional] |
 | **execution_date** | **Integer** |  | [optional] |
-| **wait_duration** | **Integer** |  | [optional] |
+| **wait_duration** | **Integer** | For workflow stages whose scheduled execution is relative, how far in the future the stage should start. | [optional] |
 | **wait_duration_unit** | **String** |  | [optional] |
-| **execute_now** | **Boolean** |  | [optional] |
+| **execute_now** | **Boolean** | Whether the workflow stage should be executed immediately | [optional] |
 
 ## Example
 
@@ -18,9 +18,9 @@ require 'launchdarkly_api'
 instance = LaunchDarklyApi::ScheduleConditionInputRep.new(
   schedule_kind: null,
   execution_date: null,
-  wait_duration: null,
+  wait_duration: 2,
   wait_duration_unit: null,
-  execute_now: null
+  execute_now: false
 )
 ```
 

data/docs/ScheduledChangesApi.md

@@ -17,7 +17,7 @@ All URIs are relative to *https://app.launchdarkly.com*
 
 Delete scheduled changes workflow
 
-Delete a scheduled changes workflow
+Delete a scheduled changes workflow.
 
 ### Examples
 
@@ -93,7 +93,7 @@ nil (empty response body)
 
 Get a scheduled change
 
-Get a scheduled change that will be applied to the feature flag by ID
+Get a scheduled change that will be applied to the feature flag by ID.
 
 ### Examples
 
@@ -245,7 +245,7 @@ end
 
 Update scheduled changes workflow
 
-Update a scheduled change, overriding existing instructions with the new ones.<br /><br />Requires a semantic patch representation of the desired changes to the resource. To learn more about semantic patches, read [Updates](/reference#updates-via-semantic-patches).
+ Update a scheduled change, overriding existing instructions with the new ones. Updating a scheduled change uses the semantic patch format.  To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch).  ### Instructions  Semantic patch requests support the following `kind` instructions for updating scheduled changes.  #### deleteScheduledChange  Removes the scheduled change.  #### replaceScheduledChangesInstructions  Removes the existing scheduled changes and replaces them with the new instructions.  ##### Parameters  - `value`: An array of the new actions to perform when the execution date for these scheduled changes arrives. Supported scheduled actions are `turnFlagOn` and `turnFlagOff`.  For example, to replace the scheduled changes, use this request body:  ```json {   \"comment\": \"optional comment\",   \"instructions\": [     {       \"kind\": \"replaceScheduledChangesInstructions\",       \"value\": [ {\"kind\": \"turnFlagOff\"} ]     }   ] } ```  #### updateScheduledChangesExecutionDate  Updates the execution date for the scheduled changes.  ##### Parameters  - `value`: the new execution date, in Unix milliseconds. 
 
 ### Examples
 
@@ -267,7 +267,7 @@ environment_key = 'environment_key_example' # String | The environment key
 id = 'id_example' # String | The scheduled change ID
 flag_scheduled_changes_input = LaunchDarklyApi::FlagScheduledChangesInput.new({instructions: [{ key: 3.56}]}) # FlagScheduledChangesInput | 
 opts = {
-  ignore_conflicts: true # Boolean | Whether or not to succeed or fail when the new instructions conflict with existing scheduled changes
+  ignore_conflicts: true # Boolean | Whether to succeed (`true`) or fail (`false`) when these new instructions conflict with existing scheduled changes
 }
 
 begin
@@ -306,7 +306,7 @@ end
 | **environment_key** | **String** | The environment key |  |
 | **id** | **String** | The scheduled change ID |  |
 | **flag_scheduled_changes_input** | [**FlagScheduledChangesInput**](FlagScheduledChangesInput.md) |  |  |
-| **ignore_conflicts** | **Boolean** | Whether or not to succeed or fail when the new instructions conflict with existing scheduled changes | [optional] |
+| **ignore_conflicts** | **Boolean** | Whether to succeed (&#x60;true&#x60;) or fail (&#x60;false&#x60;) when these new instructions conflict with existing scheduled changes | [optional] |
 
 ### Return type
 
@@ -328,7 +328,7 @@ end
 
 Create scheduled changes workflow
 
-Create scheduled changes for a feature flag. If the ignoreConficts query parameter is false and the new instructions would conflict with the current state of the feature flag or any existing scheduled changes, the request will fail. If the parameter is true and there are conflicts, the request will succeed as normal.
+Create scheduled changes for a feature flag. If the `ignoreConficts` query parameter is false and there are conflicts between these instructions and existing scheduled changes, the request will fail. If the parameter is true and there are conflicts, the request will succeed.
 
 ### Examples
 
@@ -349,7 +349,7 @@ feature_flag_key = 'feature_flag_key_example' # String | The feature flag key
 environment_key = 'environment_key_example' # String | The environment key
 post_flag_scheduled_changes_input = LaunchDarklyApi::PostFlagScheduledChangesInput.new({execution_date: 3.56, instructions: [{ key: 3.56}]}) # PostFlagScheduledChangesInput | 
 opts = {
-  ignore_conflicts: true # Boolean | Whether or not to succeed or fail when the new instructions conflict with existing scheduled changes
+  ignore_conflicts: true # Boolean | Whether to succeed (`true`) or fail (`false`) when these instructions conflict with existing scheduled changes
 }
 
 begin
@@ -387,7 +387,7 @@ end
 | **feature_flag_key** | **String** | The feature flag key |  |
 | **environment_key** | **String** | The environment key |  |
 | **post_flag_scheduled_changes_input** | [**PostFlagScheduledChangesInput**](PostFlagScheduledChangesInput.md) |  |  |
-| **ignore_conflicts** | **Boolean** | Whether or not to succeed or fail when the new instructions conflict with existing scheduled changes | [optional] |
+| **ignore_conflicts** | **Boolean** | Whether to succeed (&#x60;true&#x60;) or fail (&#x60;false&#x60;) when these instructions conflict with existing scheduled changes | [optional] |
 
 ### Return type
 

data/docs/SegmentBody.md

@@ -8,7 +8,7 @@
 | **key** | **String** | A unique key used to reference the segment |  |
 | **description** | **String** | A description of the segment's purpose | [optional] |
 | **tags** | **Array<String>** | Tags for the segment | [optional] |
-| **unbounded** | **Boolean** |  | [optional] |
+| **unbounded** | **Boolean** | Whether to create a standard segment (false) or a Big Segment (true). Only use a Big Segment if you need to add more than 15,000 users. | [optional] |
 
 ## Example
 
@@ -16,11 +16,11 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::SegmentBody.new(
-  name: null,
-  key: null,
-  description: null,
-  tags: ["ops"],
-  unbounded: null
+  name: Example segment,
+  key: example-segment,
+  description: Bundle our sample users together,
+  tags: ["testing"],
+  unbounded: false
 )
 ```
 

data/docs/SegmentsApi.md

@@ -95,7 +95,7 @@ nil (empty response body)
 
 Get expiring user targets for segment
 
-Get a list of a segment's user targets that are scheduled for removal
+Get a list of a segment's user targets that are scheduled for removal.
 
 ### Examples
 
@@ -170,7 +170,7 @@ end
 
 Get segment
 
-Get a single user segment by key
+Get a single user segment by key.
 
 ### Examples
 
@@ -245,7 +245,7 @@ end
 
 Get Big Segment membership for user
 
-Returns the membership status (included/excluded) for a given user in this segment. This operation does not support basic Segments.
+Get the membership status (included/excluded) for a given user in this Big Segment. This operation does not support standard segments.
 
 ### Examples
 
@@ -322,7 +322,7 @@ end
 
 List segments
 
-Get a list of all user segments in the given project
+Get a list of all user segments in the given project.
 
 ### Examples
 
@@ -395,7 +395,7 @@ end
 
 Update expiring user targets for segment
 
-Update the list of a segment's user targets that are scheduled for removal<br /><br />Requires a semantic patch representation of the desired changes to the resource. To learn more about semantic patches, read [Updates](/reference#updates-via-semantic-patches).<br /><br />If the request is well-formed but any of its instructions failed to process, this operation returns status code `200`. In this case, the response `errors` array will be non-empty.
+ Update expiring user targets for a segment. Updating a user target expiration uses the semantic patch format.  To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch).  If the request is well-formed but any of its instructions failed to process, this operation returns status code `200`. In this case, the response `errors` array will be non-empty.  ### Instructions  Semantic patch requests support the following `kind` instructions for updating user targets.  #### addExpireUserTargetDate  Schedules a date and time when LaunchDarkly will remove a user from segment targeting.  ##### Parameters  - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key. - `value`: The date when the user should expire from the segment targeting, in Unix milliseconds.  #### updateExpireUserTargetDate  Updates the date and time when LaunchDarkly will remove a user from segment targeting.  ##### Parameters  - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key. - `value`: The new date when the user should expire from the segment targeting, in Unix milliseconds. - `version`: The segment version.  #### removeExpireUserTargetDate  Removes the scheduled expiration for the user in the segment.  ##### Parameters  - `targetType`: A segment's target type, must be either `included` or `excluded`. - `userKey`: The user key. 
 
 ### Examples
 
@@ -472,7 +472,7 @@ end
 
 Patch segment
 
-Update a user segment. The request body must be a valid JSON patch, JSON merge patch, or semantic patch.  ## Using semantic patches on a segment  To use a [semantic patch](/reference#updates-via-semantic-patches) on a segment resource, you must include a header in the request. If you call a semantic patch resource without this header, you will receive a `400` response because your semantic patch will be interpreted as a JSON patch.  Use this header:  ``` Content-Type: application/json; domain-model=launchdarkly.semanticpatch ```  The body of a semantic patch request takes the following three properties:  1. `comment` (string): (Optional) A description of the update. 1. `environmentKey` (string): (Required) The key of the LaunchDarkly environment. 1. `instructions` (array): (Required) The list of actions to be performed by the update. Each action in the list must be an object/hash table with a `kind` property that indicates the instruction. Depending on the `kind`, the API may require other parameters. When this is the case, add the parameters as additional fields to the instruction object. Read below for more information on the specific supported semantic patch instructions.  If any instruction in the patch encounters an error, the error will be returned and the segment will not be changed. In general, instructions will silently do nothing if the segment is already in the state requested by the patch instruction. For example, `addIncludedUsers` does nothing when the targets have already been included. Specific error conditions are noted in the instruction descriptions.  ### Instructions  #### `addIncludedUsers`  Adds the user keys in `values` to the individual user targets included in the segment. Returns an error if this causes the same user key to be both included and excluded.  ##### Parameters  - `values`: list of user keys  #### `addExcludedUsers`  Adds the user keys in `values` to the individual user targets excluded from the segment. Returns an error if this causes the same user key to be both included and excluded.  ##### Parameters  - `values`: list of user keys  #### `removeIncludedUsers`  Removes the user keys in `values` from the individual user targets included in the segment.  ##### Parameters  - `values`: list of user keys  #### `removeExcludedUsers`  Removes the user keys in `values` from the individual user targets excluded from the segment.  ##### Parameters  - `values`: list of user keys  #### `updateName`  Updates the name of the segment to the string provided in `value`.  ##### Parameters  - `value`: string  ## Using JSON patches on a segment  If you do not include the header described above, you can use [JSON patch](/reference#updates-via-json-patch).  For example, to update the description for a segment, use the following request body:  ```json {   \"patch\": [     {       \"op\": \"replace\",       \"path\": \"/description\",       \"value\": \"new description\"     }   ] } ```  To update fields in the segment that are arrays, set the `path` to the name of the field and then append `/<array index>`. Using `/0` adds the new entry to the beginning of the array.  For example, to add a rule to a segment, use the following request body:  ```json {   \"patch\":[     {       \"op\": \"add\",       \"path\": \"/rules/0\",       \"value\": {         \"clauses\": [{ \"attribute\": \"email\", \"op\": \"endsWith\", \"values\": [\".edu\"], \"negate\": false }]       }     }   ] } ```  To add or remove users from segments, we recommend using semantic patch. Semantic patch for segments includes specific `instructions` for adding and removing both included and excluded users. 
+Update a user segment. The request body must be a valid semantic patch, JSON patch, or JSON merge patch.  ## Using semantic patches on a segment  To make a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch` to your `Content-Type` header. To learn more, read [Updates using semantic patch](/reference#updates-using-semantic-patch).  The body of a semantic patch request for updating segments requires an `environmentKey` in addition to `instructions` and an optional `comment`. The body of the request takes the following properties:  * `comment` (string): (Optional) A description of the update. * `environmentKey` (string): (Required) The key of the LaunchDarkly environment. * `instructions` (array): (Required) A list of actions the update should perform. Each action in the list must be an object with a `kind` property that indicates the instruction. If the action requires parameters, you must include those parameters as additional fields in the object.  ### Instructions  Semantic patch requests support the following `kind` instructions for updating segments.  #### addIncludedUsers  Adds user keys to the individual user targets included in the segment. Returns an error if this causes the same user key to be both included and excluded.  ##### Parameters  - `values`: List of user keys.  #### addExcludedUsers  Adds user keys to the individual user targets excluded from the segment. Returns an error if this causes the same user key to be both included and excluded.  ##### Parameters  - `values`: List of user keys.  #### removeIncludedUsers  Removes user keys from the individual user targets included in the segment.  ##### Parameters  - `values`: List of user keys.  #### removeExcludedUsers  Removes user keys from the individual user targets excluded from the segment.  ##### Parameters  - `values`: List of user keys.  #### updateName  Updates the name of the segment.  ##### Parameters  - `value`: Name of the segment.  ## Using JSON patches on a segment  You can also use JSON patch. To learn more, read [Updates using JSON patches](/reference#updates-using-json-patch).  For example, to update the description for a segment, use the following request body:  ```json {   \"patch\": [     {       \"op\": \"replace\",       \"path\": \"/description\",       \"value\": \"new description\"     }   ] } ```  To update fields in the segment that are arrays, set the `path` to the name of the field and then append `/<array index>`. Using `/0` adds the new entry to the beginning of the array.  For example, to add a rule to a segment, use the following request body:  ```json {   \"patch\":[     {       \"op\": \"add\",       \"path\": \"/rules/0\",       \"value\": {         \"clauses\": [{ \"attribute\": \"email\", \"op\": \"endsWith\", \"values\": [\".edu\"], \"negate\": false }]       }     }   ] } ```  To add or remove users from segments, we recommend using semantic patch. Semantic patch for segments includes specific `instructions` for adding and removing both included and excluded users. 
 
 ### Examples
 
@@ -549,7 +549,7 @@ end
 
 Create segment
 
-Create a new user segment
+Create a new user segment.
 
 ### Examples
 
@@ -567,7 +567,7 @@ end
 api_instance = LaunchDarklyApi::SegmentsApi.new
 project_key = 'project_key_example' # String | The project key
 environment_key = 'environment_key_example' # String | The environment key
-segment_body = LaunchDarklyApi::SegmentBody.new({name: 'name_example', key: 'key_example'}) # SegmentBody | 
+segment_body = LaunchDarklyApi::SegmentBody.new({name: 'Example segment', key: 'example-segment'}) # SegmentBody | 
 
 begin
   # Create segment
@@ -624,7 +624,7 @@ end
 
 Update targets on a Big Segment
 
-Update targets included or excluded in a Big Segment
+Update targets included or excluded in a Big Segment.
 
 ### Examples
 

data/docs/SegmentsBetaApi.md

@@ -86,11 +86,11 @@ nil (empty response body)
 
 ## create_big_segment_import
 
-> create_big_segment_import(project_key, environment_key, segment_key)
+> create_big_segment_import(project_key, environment_key, segment_key, opts)
 
 Create Big Segment import
 
-Starts a new import process for a Big Segment
+Start a new import process for a Big Segment.
 
 ### Examples
 
@@ -109,10 +109,14 @@ api_instance = LaunchDarklyApi::SegmentsBetaApi.new
 project_key = 'project_key_example' # String | The project key
 environment_key = 'environment_key_example' # String | The environment key
 segment_key = 'segment_key_example' # String | The segment key
+opts = {
+  file: File.new('/path/to/some/file'), # File | CSV file containing keys
+  mode: 'mode_example' # String | Import mode. Use either `merge` or `replace`
+}
 
 begin
   # Create Big Segment import
-  api_instance.create_big_segment_import(project_key, environment_key, segment_key)
+  api_instance.create_big_segment_import(project_key, environment_key, segment_key, opts)
 rescue LaunchDarklyApi::ApiError => e
   puts "Error when calling SegmentsBetaApi->create_big_segment_import: #{e}"
 end
@@ -122,12 +126,12 @@ end
 
 This returns an Array which contains the response data (`nil` in this case), status code and headers.
 
-> <Array(nil, Integer, Hash)> create_big_segment_import_with_http_info(project_key, environment_key, segment_key)
+> <Array(nil, Integer, Hash)> create_big_segment_import_with_http_info(project_key, environment_key, segment_key, opts)
 
 ```ruby
 begin
   # Create Big Segment import
-  data, status_code, headers = api_instance.create_big_segment_import_with_http_info(project_key, environment_key, segment_key)
+  data, status_code, headers = api_instance.create_big_segment_import_with_http_info(project_key, environment_key, segment_key, opts)
   p status_code # => 2xx
   p headers # => { ... }
   p data # => nil
@@ -143,6 +147,8 @@ end
 | **project_key** | **String** | The project key |  |
 | **environment_key** | **String** | The environment key |  |
 | **segment_key** | **String** | The segment key |  |
+| **file** | **File** | CSV file containing keys | [optional] |
+| **mode** | **String** | Import mode. Use either &#x60;merge&#x60; or &#x60;replace&#x60; | [optional] |
 
 ### Return type
 
@@ -154,7 +160,7 @@ nil (empty response body)
 
 ### HTTP request headers
 
-- **Content-Type**: Not defined
+- **Content-Type**: multipart/form-data
 - **Accept**: application/json
 
 

data/docs/SourceFlag.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **key** | **String** | Flag key to copy |  |
-| **version** | **Integer** |  | [optional] |
+| **key** | **String** | The environment key for the source environment |  |
+| **version** | **Integer** | The version of the source flag from which to copy | [optional] |
 
 ## Example
 
@@ -13,8 +13,8 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::SourceFlag.new(
-  key: null,
-  version: null
+  key: example-environment-key,
+  version: 1
 )
 ```
 

data/docs/StageInputRep.md

@@ -4,8 +4,9 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **name** | **String** |  | [optional] |
-| **conditions** | [**Array<ConditionInputRep>**](ConditionInputRep.md) |  | [optional] |
+| **name** | **String** | The stage name | [optional] |
+| **execute_conditions_in_sequence** | **Boolean** | Whether to execute the conditions in sequence for the given stage | [optional] |
+| **conditions** | [**Array<ConditionInputRep>**](ConditionInputRep.md) | An array of conditions for the stage. | [optional] |
 | **action** | [**ActionInputRep**](ActionInputRep.md) |  | [optional] |
 
 ## Example
@@ -14,8 +15,9 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::StageInputRep.new(
-  name: null,
-  conditions: null,
+  name: 10% rollout on day 1,
+  execute_conditions_in_sequence: true,
+  conditions: [{"kind":"schedule","scheduleKind":"relative","waitDuration":2,"waitDurationUnit":"calendarDay"}],
   action: null
 )
 ```

data/docs/StatementPost.md

@@ -5,9 +5,9 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **resources** | **Array<String>** | Resource specifier strings | [optional] |
-| **not_resources** | **Array<String>** | Targeted resources are the resources NOT in this list. The \"resources\" field must be empty to use this field. | [optional] |
+| **not_resources** | **Array<String>** | Targeted resources are the resources NOT in this list. The <code>resources</code> field must be empty to use this field. | [optional] |
 | **actions** | **Array<String>** | Actions to perform on a resource | [optional] |
-| **not_actions** | **Array<String>** | Targeted actions are the actions NOT in this list. The \"actions\" field must be empty to use this field. | [optional] |
+| **not_actions** | **Array<String>** | Targeted actions are the actions NOT in this list. The <code>actions</code> field must be empty to use this field. | [optional] |
 | **effect** | **String** |  |  |
 
 ## Example
@@ -16,9 +16,9 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::StatementPost.new(
-  resources: null,
+  resources: ["proj/*:env/*:flag/*;testing-tag"],
   not_resources: null,
-  actions: null,
+  actions: ["*"],
   not_actions: null,
   effect: null
 )

data/docs/StatementPostData.md

@@ -5,9 +5,9 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **resources** | **Array<String>** | Resource specifier strings | [optional] |
-| **not_resources** | **Array<String>** | Targeted resources are the resources NOT in this list. The \"resources\" field must be empty to use this field. | [optional] |
+| **not_resources** | **Array<String>** | Targeted resources are the resources NOT in this list. The <code>resources</code> field must be empty to use this field. | [optional] |
 | **actions** | **Array<String>** | Actions to perform on a resource | [optional] |
-| **not_actions** | **Array<String>** | Targeted actions are the actions NOT in this list. The \"actions\" field must be empty to use this field. | [optional] |
+| **not_actions** | **Array<String>** | Targeted actions are the actions NOT in this list. The <code>actions</code> field must be empty to use this field. | [optional] |
 | **effect** | **String** |  |  |
 
 ## Example
@@ -16,9 +16,9 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::StatementPostData.new(
-  resources: null,
+  resources: ["proj/*:env/*:flag/*;testing-tag"],
   not_resources: null,
-  actions: null,
+  actions: ["*"],
   not_actions: null,
   effect: null
 )

data/docs/StatisticCollectionRep.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **flags** | **Hash<String, Array<StatisticRep>>** |  |  |
-| **_links** | [**Hash<String, Link>**](Link.md) |  |  |
+| **flags** | **Hash<String, Array<StatisticRep>>** | A map of flag keys to a list of code reference statistics for each code repository in which the flag key appears |  |
+| **_links** | [**Hash<String, Link>**](Link.md) | The location and content type of related resources |  |
 
 ## Example
 

data/docs/StatisticRep.md

@@ -4,13 +4,14 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **name** | **String** |  |  |
-| **source_link** | **String** |  |  |
-| **default_branch** | **String** |  |  |
-| **enabled** | **Boolean** |  |  |
-| **version** | **Integer** |  |  |
-| **hunk_count** | **Integer** |  |  |
-| **_links** | [**Hash<String, Link>**](Link.md) |  |  |
+| **name** | **String** | The repository name |  |
+| **source_link** | **String** | A URL to access the repository |  |
+| **default_branch** | **String** | The repository's default branch |  |
+| **enabled** | **Boolean** | Whether or not a repository is enabled for code reference scanning |  |
+| **version** | **Integer** | The version of the repository's saved information |  |
+| **hunk_count** | **Integer** | The number of code reference hunks in which the flag appears in this repository |  |
+| **file_count** | **Integer** | The number of files in which the flag appears in this repository |  |
+| **_links** | [**Hash<String, Link>**](Link.md) | The location and content type of related resources |  |
 
 ## Example
 
@@ -18,12 +19,13 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::StatisticRep.new(
-  name: null,
-  source_link: null,
-  default_branch: null,
-  enabled: null,
-  version: null,
+  name: LaunchDarkly-Docs,
+  source_link: https://github.com/launchdarkly/LaunchDarkly-Docs,
+  default_branch: main,
+  enabled: true,
+  version: 3,
   hunk_count: null,
+  file_count: null,
   _links: null
 )
 ```

data/docs/StatisticsRep.md

@@ -0,0 +1,20 @@
+# LaunchDarklyApi::StatisticsRep
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **items** | [**Array<StatisticRep>**](StatisticRep.md) | A list of code reference statistics for each code repository | [optional] |
+| **_links** | [**Hash<String, Link>**](Link.md) | The location and content type of related resources | [optional] |
+
+## Example
+
+```ruby
+require 'launchdarkly_api'
+
+instance = LaunchDarklyApi::StatisticsRep.new(
+  items: null,
+  _links: null
+)
+```
+

data/docs/StatusConflictErrorRep.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **code** | **String** |  | [optional] |
-| **message** | **String** |  | [optional] |
+| **code** | **String** | Specific error code encountered | [optional] |
+| **message** | **String** | Description of the error | [optional] |
 
 ## Example
 
@@ -14,7 +14,7 @@ require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::StatusConflictErrorRep.new(
   code: optimistic_locking_error,
-  message: Optimistic lock error. Please try again later.
+  message: Conflict. Optimistic lock error. Try again later.
 )
 ```
 

data/docs/SubscriptionPost.md

@@ -7,10 +7,10 @@
 | **name** | **String** | A human-friendly name for your audit log subscription. |  |
 | **statements** | [**Array<StatementPost>**](StatementPost.md) |  | [optional] |
 | **on** | **Boolean** | Whether or not you want your subscription to actively send events. | [optional] |
-| **tags** | **Array<String>** |  | [optional] |
-| **config** | **Hash<String, Object>** | The unique set of fields required to configure an audit log subscription integration of this type. Refer to the \"formVariables\" field in the corresponding manifest.json  at https://github.com/launchdarkly/integration-framework/tree/master/integrations for a full list of fields for the integration you wish to configure. |  |
+| **tags** | **Array<String>** | An array of tags for this subscription. | [optional] |
+| **config** | **Hash<String, Object>** | The unique set of fields required to configure an audit log subscription integration of this type. Refer to the <code>formVariables</code> field in the corresponding <code>manifest.json</code> at https://github.com/launchdarkly/integration-framework/tree/main/integrations for a full list of fields for the integration you wish to configure. |  |
 | **url** | **String** | Slack webhook receiver URL. Only necessary for legacy Slack webhook integrations. | [optional] |
-| **api_key** | **String** | Datadog API key. Only necessary for legacy Datadog webhook subscriptions. | [optional] |
+| **api_key** | **String** | Datadog API key. Only necessary for legacy Datadog webhook integrations. | [optional] |
 
 ## Example
 
@@ -18,11 +18,11 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::SubscriptionPost.new(
-  name: null,
+  name: Example audit log subscription.,
   statements: null,
-  on: null,
-  tags: null,
-  config: null,
+  on: false,
+  tags: ["testing-tag"],
+  config: {"optional":"an optional property","required":"the required property","url":"https://example.com"},
   url: null,
   api_key: null
 )

data/docs/TargetResourceRep.md

@@ -6,7 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **_links** | [**Hash<String, Link>**](Link.md) |  | [optional] |
 | **name** | **String** |  | [optional] |
-| **resources** | **Array<Object>** |  | [optional] |
+| **resources** | **Array<Hash>** |  | [optional] |
 
 ## Example
 

data/docs/Team.md

@@ -12,6 +12,10 @@
 | **_links** | [**Hash<String, Link>**](Link.md) |  | [optional] |
 | **_last_modified** | **Integer** |  | [optional] |
 | **_version** | **Integer** |  | [optional] |
+| **roles** | [**TeamCustomRoles**](TeamCustomRoles.md) |  | [optional] |
+| **members** | [**TeamMembers**](TeamMembers.md) |  | [optional] |
+| **projects** | [**TeamProjects**](TeamProjects.md) |  | [optional] |
+| **maintainers** | [**TeamMaintainers**](TeamMaintainers.md) |  | [optional] |
 
 ## Example
 
@@ -19,14 +23,18 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::Team.new(
-  description: null,
-  key: null,
-  name: null,
+  description: Description for this team.,
+  key: example-team,
+  name: Example team,
   _access: null,
   _creation_date: null,
-  _links: null,
+  _links: {"parent":{"href":"/api/v2/teams","type":"application/json"},"roles":{"href":"/api/v2/teams/example-team/roles","type":"application/json"},"self":{"href":"/api/v2/teams/example-team","type":"application/json"}},
   _last_modified: null,
-  _version: null
+  _version: 3,
+  roles: null,
+  members: null,
+  projects: null,
+  maintainers: null
 )
 ```
 

data/docs/TeamCustomRole.md

@@ -15,8 +15,8 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::TeamCustomRole.new(
-  key: null,
-  name: null,
+  key: example-role,
+  name: Example role,
   projects: null,
   applied_on: null
 )

data/docs/TeamCustomRoles.md

@@ -14,9 +14,9 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::TeamCustomRoles.new(
-  total_count: null,
+  total_count: 1,
   items: null,
-  _links: null
+  _links: {"self":{"href":"/api/v2/teams/example-team/roles?limit=25","type":"application/json"}}
 )
 ```
 

data/docs/TeamMaintainers.md

@@ -14,9 +14,9 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::TeamMaintainers.new(
-  total_count: null,
-  items: null,
-  _links: null
+  total_count: 1,
+  items: [{"_id":"569f183514f4432160000007","_links":{"self":{"href":"/api/v2/members/569f183514f4432160000007","type":"application/json"}},"email":"foobar@example.com","firstName":"Foo","lastName":"Bar","role":"reader"}],
+  _links: {"self":{"href":"/api/v2/teams/example-team/maintainers?limit=5","type":"application/json"}}
 )
 ```
 

data/docs/TeamMembers.md

@@ -0,0 +1,18 @@
+# LaunchDarklyApi::TeamMembers
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **total_count** | **Integer** |  | [optional] |
+
+## Example
+
+```ruby
+require 'launchdarkly_api'
+
+instance = LaunchDarklyApi::TeamMembers.new(
+  total_count: 15
+)
+```
+

data/docs/TeamPatchInput.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **comment** | **String** |  | [optional] |
-| **instructions** | **Array<Hash>** |  | [optional] |
+| **comment** | **String** | Optional comment describing the update | [optional] |
+| **instructions** | **Array<Hash>** |  |  |
 
 ## Example
 
@@ -13,7 +13,7 @@
 require 'launchdarkly_api'
 
 instance = LaunchDarklyApi::TeamPatchInput.new(
-  comment: null,
+  comment: Optional comment about the update,
   instructions: null
 )
 ```