launchdarkly_api 15.0.0 → 15.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 80b3a499ef911ee35909ba11e10825aaaa4f79d9630b62e5578091f9dfa11083
-  data.tar.gz: 890306d0b547c1a76decc509a2619e758fb863d1cfbaee10653e1d5ed613e5b7
+  metadata.gz: e77a0e6e34b970eb62aad201c32e34644aefb1ccaef60c4880ecef99f32e1b68
+  data.tar.gz: 20ddc6ed8005af56aba34475718cb10d13a712514cd3ca6af088612304b1dfe4
 SHA512:
-  metadata.gz: b34873e1577f6367ea11654bc3c3ea96354d9c438e41ed5207f943f2e9dd95e1d461d8d3157a2cf279d188df8c9ab5458967a6cb6f873078e5b13cd319b9f0f9
-  data.tar.gz: 931b7d01a84e9f98b2cb0ba704d05fb2fe57968b4f12ae83013e54e59e1d5f0e78fc20e75cd83ed7f5e9068e00e353647ffb1f80ed19f3a2846f07ff84ecbe68
+  metadata.gz: 9a12e0ce914c7f41d5276080c93c7b6d2a0dd4a4743e38e739f267acc5c38c5fbcf3cc67f7e997f96ee9c4d2af0b3faa937ab43ad5fdb1e26632a5891a954c74
+  data.tar.gz: 8f6035355cb0b5951f37b057980e60f18acf7dced0a8a722084c81e75ac7d4fbd646da4d1a4ba96e58b5c37effb2406c4983fdbd59ed40256cb490812871c265

data/README.md

@@ -396,7 +396,7 @@ If you would like to upgrade your integration to use a new API version, you can
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
 - API version: 2.0
-- Package version: 15.0.0
+- Package version: 15.1.0
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 For more information, please visit [https://support.launchdarkly.com](https://support.launchdarkly.com)
 
@@ -413,16 +413,16 @@ gem build launchdarkly_api.gemspec
 Then either install the gem locally:
 
 ```shell
-gem install ./launchdarkly_api-15.0.0.gem
+gem install ./launchdarkly_api-15.1.0.gem
 ```
 
-(for development, run `gem install --dev ./launchdarkly_api-15.0.0.gem` to install the development dependencies)
+(for development, run `gem install --dev ./launchdarkly_api-15.1.0.gem` to install the development dependencies)
 
 or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
 
 Finally add this to the Gemfile:
 
-    gem 'launchdarkly_api', '~> 15.0.0'
+    gem 'launchdarkly_api', '~> 15.1.0'
 
 ### Install from Git
 
@@ -485,6 +485,7 @@ Class | Method | HTTP request | Description
 *LaunchDarklyApi::AccountMembersApi* | [**post_member_teams**](docs/AccountMembersApi.md#post_member_teams) | **POST** /api/v2/members/{id}/teams | Add a member to teams
 *LaunchDarklyApi::AccountMembersApi* | [**post_members**](docs/AccountMembersApi.md#post_members) | **POST** /api/v2/members | Invite new members
 *LaunchDarklyApi::AccountMembersBetaApi* | [**patch_members**](docs/AccountMembersBetaApi.md#patch_members) | **PATCH** /api/v2/members | Modify account members
+*LaunchDarklyApi::AccountUsageBetaApi* | [**get_data_export_events_usage**](docs/AccountUsageBetaApi.md#get_data_export_events_usage) | **GET** /api/v2/usage/data-export-events | Get data export events usage
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_evaluations_usage**](docs/AccountUsageBetaApi.md#get_evaluations_usage) | **GET** /api/v2/usage/evaluations/{projectKey}/{environmentKey}/{featureFlagKey} | Get evaluations usage
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_events_usage**](docs/AccountUsageBetaApi.md#get_events_usage) | **GET** /api/v2/usage/events/{type} | Get events usage
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_experimentation_keys_usage**](docs/AccountUsageBetaApi.md#get_experimentation_keys_usage) | **GET** /api/v2/usage/experimentation-keys | Get experimentation keys usage
@@ -492,6 +493,7 @@ Class | Method | HTTP request | Description
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_mau_sdks_by_type**](docs/AccountUsageBetaApi.md#get_mau_sdks_by_type) | **GET** /api/v2/usage/mau/sdks | Get MAU SDKs by type
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_mau_usage**](docs/AccountUsageBetaApi.md#get_mau_usage) | **GET** /api/v2/usage/mau | Get MAU usage
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_mau_usage_by_category**](docs/AccountUsageBetaApi.md#get_mau_usage_by_category) | **GET** /api/v2/usage/mau/bycategory | Get MAU usage by category
+*LaunchDarklyApi::AccountUsageBetaApi* | [**get_service_connection_usage**](docs/AccountUsageBetaApi.md#get_service_connection_usage) | **GET** /api/v2/usage/service-connections | Get service connection usage
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_stream_usage**](docs/AccountUsageBetaApi.md#get_stream_usage) | **GET** /api/v2/usage/streams/{source} | Get stream usage
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_stream_usage_by_sdk_version**](docs/AccountUsageBetaApi.md#get_stream_usage_by_sdk_version) | **GET** /api/v2/usage/streams/{source}/bysdkversion | Get stream usage by SDK version
 *LaunchDarklyApi::AccountUsageBetaApi* | [**get_stream_usage_sdkversion**](docs/AccountUsageBetaApi.md#get_stream_usage_sdkversion) | **GET** /api/v2/usage/streams/{source}/sdkversions | Get stream usage SDK versions
@@ -600,7 +602,7 @@ Class | Method | HTTP request | Description
 *LaunchDarklyApi::InsightsChartsBetaApi* | [**get_deployment_frequency_chart**](docs/InsightsChartsBetaApi.md#get_deployment_frequency_chart) | **GET** /api/v2/engineering-insights/charts/deployments/frequency | Get deployment frequency chart data
 *LaunchDarklyApi::InsightsChartsBetaApi* | [**get_flag_status_chart**](docs/InsightsChartsBetaApi.md#get_flag_status_chart) | **GET** /api/v2/engineering-insights/charts/flags/status | Get flag status chart data
 *LaunchDarklyApi::InsightsChartsBetaApi* | [**get_lead_time_chart**](docs/InsightsChartsBetaApi.md#get_lead_time_chart) | **GET** /api/v2/engineering-insights/charts/lead-time | Get lead time chart data
-*LaunchDarklyApi::InsightsChartsBetaApi* | [**get_release_frequency_chart**](docs/InsightsChartsBetaApi.md#get_release_frequency_chart) | **GET** /api/v2/engineering-insights/charts/releases/frequency | Get replease frequency chart data
+*LaunchDarklyApi::InsightsChartsBetaApi* | [**get_release_frequency_chart**](docs/InsightsChartsBetaApi.md#get_release_frequency_chart) | **GET** /api/v2/engineering-insights/charts/releases/frequency | Get release frequency chart data
 *LaunchDarklyApi::InsightsChartsBetaApi* | [**get_stale_flags_chart**](docs/InsightsChartsBetaApi.md#get_stale_flags_chart) | **GET** /api/v2/engineering-insights/charts/flags/stale | Get stale flags chart data
 *LaunchDarklyApi::InsightsDeploymentsBetaApi* | [**create_deployment_event**](docs/InsightsDeploymentsBetaApi.md#create_deployment_event) | **POST** /api/v2/engineering-insights/deployment-events | Create deployment event
 *LaunchDarklyApi::InsightsDeploymentsBetaApi* | [**get_deployment**](docs/InsightsDeploymentsBetaApi.md#get_deployment) | **GET** /api/v2/engineering-insights/deployments/{deploymentID} | Get deployment
@@ -1034,6 +1036,7 @@ Class | Method | HTTP request | Description
  - [LaunchDarklyApi::RelayAutoConfigPost](docs/RelayAutoConfigPost.md)
  - [LaunchDarklyApi::RelayAutoConfigRep](docs/RelayAutoConfigRep.md)
  - [LaunchDarklyApi::Release](docs/Release.md)
+ - [LaunchDarklyApi::ReleaseAudience](docs/ReleaseAudience.md)
  - [LaunchDarklyApi::ReleasePhase](docs/ReleasePhase.md)
  - [LaunchDarklyApi::ReleasePipeline](docs/ReleasePipeline.md)
  - [LaunchDarklyApi::ReleasePipelineCollection](docs/ReleasePipelineCollection.md)

data/docs/AccountUsageBetaApi.md

@@ -4,6 +4,7 @@ All URIs are relative to *https://app.launchdarkly.com*
 
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
+| [**get_data_export_events_usage**](AccountUsageBetaApi.md#get_data_export_events_usage) | **GET** /api/v2/usage/data-export-events | Get data export events usage |
 | [**get_evaluations_usage**](AccountUsageBetaApi.md#get_evaluations_usage) | **GET** /api/v2/usage/evaluations/{projectKey}/{environmentKey}/{featureFlagKey} | Get evaluations usage |
 | [**get_events_usage**](AccountUsageBetaApi.md#get_events_usage) | **GET** /api/v2/usage/events/{type} | Get events usage |
 | [**get_experimentation_keys_usage**](AccountUsageBetaApi.md#get_experimentation_keys_usage) | **GET** /api/v2/usage/experimentation-keys | Get experimentation keys usage |
@@ -11,11 +12,87 @@ All URIs are relative to *https://app.launchdarkly.com*
 | [**get_mau_sdks_by_type**](AccountUsageBetaApi.md#get_mau_sdks_by_type) | **GET** /api/v2/usage/mau/sdks | Get MAU SDKs by type |
 | [**get_mau_usage**](AccountUsageBetaApi.md#get_mau_usage) | **GET** /api/v2/usage/mau | Get MAU usage |
 | [**get_mau_usage_by_category**](AccountUsageBetaApi.md#get_mau_usage_by_category) | **GET** /api/v2/usage/mau/bycategory | Get MAU usage by category |
+| [**get_service_connection_usage**](AccountUsageBetaApi.md#get_service_connection_usage) | **GET** /api/v2/usage/service-connections | Get service connection usage |
 | [**get_stream_usage**](AccountUsageBetaApi.md#get_stream_usage) | **GET** /api/v2/usage/streams/{source} | Get stream usage |
 | [**get_stream_usage_by_sdk_version**](AccountUsageBetaApi.md#get_stream_usage_by_sdk_version) | **GET** /api/v2/usage/streams/{source}/bysdkversion | Get stream usage by SDK version |
 | [**get_stream_usage_sdkversion**](AccountUsageBetaApi.md#get_stream_usage_sdkversion) | **GET** /api/v2/usage/streams/{source}/sdkversions | Get stream usage SDK versions |
 
 
+## get_data_export_events_usage
+
+> <SeriesIntervalsRep> get_data_export_events_usage(opts)
+
+Get data export events usage
+
+Get a time-series array of the number of monthly data export events from your account. The granularity is always daily, with a maximum of 31 days.
+
+### Examples
+
+```ruby
+require 'time'
+require 'launchdarkly_api'
+# setup authorization
+LaunchDarklyApi.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = LaunchDarklyApi::AccountUsageBetaApi.new
+opts = {
+  from: 'from_example', # String | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month.
+  to: 'to_example' # String | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time.
+}
+
+begin
+  # Get data export events usage
+  result = api_instance.get_data_export_events_usage(opts)
+  p result
+rescue LaunchDarklyApi::ApiError => e
+  puts "Error when calling AccountUsageBetaApi->get_data_export_events_usage: #{e}"
+end
+```
+
+#### Using the get_data_export_events_usage_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<SeriesIntervalsRep>, Integer, Hash)> get_data_export_events_usage_with_http_info(opts)
+
+```ruby
+begin
+  # Get data export events usage
+  data, status_code, headers = api_instance.get_data_export_events_usage_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <SeriesIntervalsRep>
+rescue LaunchDarklyApi::ApiError => e
+  puts "Error when calling AccountUsageBetaApi->get_data_export_events_usage_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **from** | **String** | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month. | [optional] |
+| **to** | **String** | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time. | [optional] |
+
+### Return type
+
+[**SeriesIntervalsRep**](SeriesIntervalsRep.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
 ## get_evaluations_usage
 
 > <SeriesListRep> get_evaluations_usage(project_key, environment_key, feature_flag_key, opts)
@@ -565,6 +642,81 @@ end
 - **Accept**: application/json
 
 
+## get_service_connection_usage
+
+> <SeriesIntervalsRep> get_service_connection_usage(opts)
+
+Get service connection usage
+
+Get a time-series array of the number of monthly service connections from your account. The granularity is always daily, with a maximum of 31 days.
+
+### Examples
+
+```ruby
+require 'time'
+require 'launchdarkly_api'
+# setup authorization
+LaunchDarklyApi.configure do |config|
+  # Configure API key authorization: ApiKey
+  config.api_key['ApiKey'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['ApiKey'] = 'Bearer'
+end
+
+api_instance = LaunchDarklyApi::AccountUsageBetaApi.new
+opts = {
+  from: 'from_example', # String | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month.
+  to: 'to_example' # String | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time.
+}
+
+begin
+  # Get service connection usage
+  result = api_instance.get_service_connection_usage(opts)
+  p result
+rescue LaunchDarklyApi::ApiError => e
+  puts "Error when calling AccountUsageBetaApi->get_service_connection_usage: #{e}"
+end
+```
+
+#### Using the get_service_connection_usage_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<SeriesIntervalsRep>, Integer, Hash)> get_service_connection_usage_with_http_info(opts)
+
+```ruby
+begin
+  # Get service connection usage
+  data, status_code, headers = api_instance.get_service_connection_usage_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <SeriesIntervalsRep>
+rescue LaunchDarklyApi::ApiError => e
+  puts "Error when calling AccountUsageBetaApi->get_service_connection_usage_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **from** | **String** | The series of data returned starts from this timestamp (Unix seconds). Defaults to the beginning of the current month. | [optional] |
+| **to** | **String** | The series of data returned ends at this timestamp (Unix seconds). Defaults to the current time. | [optional] |
+
+### Return type
+
+[**SeriesIntervalsRep**](SeriesIntervalsRep.md)
+
+### Authorization
+
+[ApiKey](../README.md#ApiKey)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
 ## get_stream_usage
 
 > <SeriesListRep> get_stream_usage(source, opts)

data/docs/FeatureFlagBody.md

@@ -16,6 +16,8 @@
 | **defaults** | [**Defaults**](Defaults.md) |  | [optional] |
 | **purpose** | **String** | Purpose of the flag | [optional] |
 | **migration_settings** | [**MigrationSettingsPost**](MigrationSettingsPost.md) |  | [optional] |
+| **maintainer_id** | **String** | The ID of the member who maintains this feature flag | [optional] |
+| **maintainer_team_key** | **String** | The key of the team that maintains this feature flag | [optional] |
 
 ## Example
 
@@ -34,7 +36,9 @@ instance = LaunchDarklyApi::FeatureFlagBody.new(
   custom_properties: null,
   defaults: null,
   purpose: migration,
-  migration_settings: null
+  migration_settings: null,
+  maintainer_id: 12ab3c45de678910fgh12345,
+  maintainer_team_key: team-1
 )
 ```
 

data/docs/FeatureFlagsApi.md

@@ -626,7 +626,7 @@ end
 
 List feature flags
 
-Get a list of all feature flags in the given project. By default, each flag includes configurations for each environment. You can filter environments with the `env` query parameter. For example, setting `env=production` restricts the returned configurations to just your production environment. You can also filter feature flags by tag with the `tag` query parameter.  > #### Recommended use > > This endpoint can return a large amount of information. We recommend using some or all of these query parameters to decrease response time and overall payload size: `limit`, `env`, `query`, and `filter=creationDate`.  ### Filtering flags  You can filter on certain fields using the `filter` query parameter. For example, setting `filter=query:dark-mode,tags:beta+test` matches flags with the string `dark-mode` in their key or name, ignoring case, which also have the tags `beta` and `test`.  The `filter` query parameter supports the following arguments:  | Filter argument       | Description | Example              | |-----------------------|-------------|----------------------| | `archived`              | A boolean value. It filters the list to archived flags. Setting the value to `true` returns only archived flags. When this is absent, only unarchived flags are returned. | `filter=archived:true` | | `contextKindsEvaluated` | A `+`-separated list of context kind keys. It filters the list to flags which have been evaluated in the past 30 days for all of the context kinds in the list. | `filter=contextKindsEvaluated:user+application` | | `contextKindTargeted`   | A string. It filters the list to flags that are targeting the given context kind key. | `filter=contextKindTargeted:user` | | `codeReferences.max`    | An integer value. Use `0` to return flags that do not have code references. | `filter=codeReferences.max:0` | | `codeReferences.min`    | An integer value. Use `1` to return flags that do have code references. | `filter=codeReferences.min:1` | | `creationDate`          | An object with an optional `before` field whose value is Unix time in milliseconds. It filters the list to flags created before the date. | `filter=creationDate:{\"before\":1690527600000}` | | `evaluated`             | An object that contains a key of `after` and a value in Unix time in milliseconds. It filters the list to all flags that have been evaluated since the time you specify, in the environment provided. This filter requires the `filterEnv` filter. | `filter=evaluation:{\"after\":1690527600000}` | | `filterEnv`             | A string with the key of a valid environment. You must use this field for filters that are environment-specific. If there are multiple environment-specific filters, you only need to include this field once. | `filter=evaluated:{\"after\": 1590768455282},filterEnv:production,status:active` | | `followerId`            | A valid member ID. It filters the list to flags that are being followed by this member. |  `filter=followerId:12ab3c45de678910abc12345` | | `hasDataExport`         | A boolean value. It filters the list to flags that are exporting data in the specified environment. This includes flags that are exporting data from Experimentation. This filter requires the `filterEnv` filter. | `filter=hasDataExport:true,filterEnv:production` | | `hasExperiment`         | A boolean value. It filters the list to flags that are used in an experiment. | `filter=hasExperiment:true` | | `maintainerId`          | A valid member ID. It filters the list to flags that are maintained by this member. | `filter=maintainerId:12ab3c45de678910abc12345` | | `maintainerTeamKey`     | A string. It filters the list to flags that are maintained by the team with this key. | `filter=maintainerTeamKey:example-team-key` | | `query`                 | A string. It filters the list to flags that include the specified string in their key or name. It is not case sensitive. | `filter=query:example` | | `sdkAvailability`       | A string, one of `client`, `mobile`, `anyClient`, `server`. Using `client` filters the list to flags whose client-side SDK availability is set to use the client-side ID. Using `mobile` filters to flags set to use the mobile key. Using `anyClient` filters to flags set to use either the client-side ID or the mobile key. Using `server` filters to flags set to use neither, that is, to flags only available in server-side SDKs.  | `filter=sdkAvailability:client` | | `segmentTargeted`       | A string. It filters the list to flags that target the segment with this key. This filter requires the `filterEnv` filter. | `filter=segmentTargeted:example-segment-key,filterEnv:production` | | `status`                | A string, either `new`, `inactive`, `active`, or `launched`. It filters the list to flags with the specified status in the specified environment. This filter requires the `filterEnv` filter. | `filter=status:active,filterEnv:production` | | `tags`                  | A `+`-separated list of tags. It filters the list to flags that have all of the tags in the list. | `filter=tags:beta+test` | | `type`                  | A string, either `temporary` or `permanent`. It filters the list to flags with the specified type. | `filter=type:permanent` |  The documented values for the `filter` query are prior to URL encoding. For example, the `+` in `filter=tags:beta+test` must be encoded to `%2B`.  By default, this endpoint returns all flags. You can page through the list with the `limit` parameter and by following the `first`, `prev`, `next`, and `last` links in the returned `_links` field. These links will not be present if the pages they refer to don't exist. For example, the `first` and `prev` links will be missing from the response on the first page.  ### Sorting flags  You can sort flags based on the following fields:  - `creationDate` sorts by the creation date of the flag. - `key` sorts by the key of the flag. - `maintainerId` sorts by the flag maintainer. - `name` sorts by flag name. - `tags` sorts by tags. - `targetingModifiedDate` sorts by the date that the flag's targeting rules were last modified in a given environment. It must be used with `env` parameter and it can not be combined with any other sort. If multiple `env` values are provided, it will perform sort using the first one. For example, `sort=-targetingModifiedDate&env=production&env=staging` returns results sorted by `targetingModifiedDate` for the `production` environment. - `type` sorts by flag type  All fields are sorted in ascending order by default. To sort in descending order, prefix the field with a dash ( - ). For example, `sort=-name` sorts the response by flag name in descending order.  ### Expanding response  LaunchDarkly supports the `expand` query param to include additional fields in the response, with the following fields:  - `codeReferences` includes code references for the feature flag - `evaluation` includes evaluation information within returned environments, including which context kinds the flag has been evaluated for in the past 30 days - `migrationSettings` includes migration settings information within the flag and within returned environments. These settings are only included for migration flags, that is, where `purpose` is `migration`.  For example, `expand=evaluation` includes the `evaluation` field in the response.  ### Migration flags For migration flags, the cohort information is included in the `rules` property of a flag's response, and default cohort information is included in the `fallthrough` property of a flag's response. To learn more, read [Migration Flags](https://docs.launchdarkly.com/home/flag-types/migration-flags). 
+Get a list of all feature flags in the given project. By default, each flag includes configurations for each environment. You can filter environments with the `env` query parameter. For example, setting `env=production` restricts the returned configurations to just your production environment. You can also filter feature flags by tag with the `tag` query parameter.  > #### Recommended use > > This endpoint can return a large amount of information. We recommend using some or all of these query parameters to decrease response time and overall payload size: `limit`, `env`, `query`, and `filter=creationDate`.  ### Filtering flags  You can filter on certain fields using the `filter` query parameter. For example, setting `filter=query:dark-mode,tags:beta+test` matches flags with the string `dark-mode` in their key or name, ignoring case, which also have the tags `beta` and `test`.  The `filter` query parameter supports the following arguments:  | Filter argument       | Description | Example              | |-----------------------|-------------|----------------------| | `applicationEvaluated`  | A string. It filters the list to flags that are evaluated in the application with the given key. | `filter=applicationEvaluated:com.launchdarkly.cafe` | | `archived`              | (deprecated) A boolean value. It filters the list to archived flags. | Use `filter=state:archived` instead | | `contextKindsEvaluated` | A `+`-separated list of context kind keys. It filters the list to flags which have been evaluated in the past 30 days for all of the context kinds in the list. | `filter=contextKindsEvaluated:user+application` | | `contextKindTargeted`   | A string. It filters the list to flags that are targeting the given context kind key. | `filter=contextKindTargeted:user` | | `codeReferences.max`    | An integer value. Use `0` to return flags that do not have code references. | `filter=codeReferences.max:0` | | `codeReferences.min`    | An integer value. Use `1` to return flags that do have code references. | `filter=codeReferences.min:1` | | `creationDate`          | An object with an optional `before` field whose value is Unix time in milliseconds. It filters the list to flags created before the date. | `filter=creationDate:{\"before\":1690527600000}` | | `evaluated`             | An object that contains a key of `after` and a value in Unix time in milliseconds. It filters the list to all flags that have been evaluated since the time you specify, in the environment provided. This filter requires the `filterEnv` filter. | `filter=evaluation:{\"after\":1690527600000}` | | `filterEnv`             | A string with the key of a valid environment. You must use this field for filters that are environment-specific. If there are multiple environment-specific filters, you only need to include this field once. | `filter=evaluated:{\"after\": 1590768455282},filterEnv:production,status:active` | | `followerId`            | A valid member ID. It filters the list to flags that are being followed by this member. |  `filter=followerId:12ab3c45de678910abc12345` | | `hasDataExport`         | A boolean value. It filters the list to flags that are exporting data in the specified environment. This includes flags that are exporting data from Experimentation. This filter requires the `filterEnv` filter. | `filter=hasDataExport:true,filterEnv:production` | | `hasExperiment`         | A boolean value. It filters the list to flags that are used in an experiment. | `filter=hasExperiment:true` | | `maintainerId`          | A valid member ID. It filters the list to flags that are maintained by this member. | `filter=maintainerId:12ab3c45de678910abc12345` | | `maintainerTeamKey`     | A string. It filters the list to flags that are maintained by the team with this key. | `filter=maintainerTeamKey:example-team-key` | | `query`                 | A string. It filters the list to flags that include the specified string in their key or name. It is not case sensitive. | `filter=query:example` | | `state`                 | A string, either `live`, `deprecated`, or `archived`. It filters the list to flags in this state. | `filter=state:archived` | | `sdkAvailability`       | A string, one of `client`, `mobile`, `anyClient`, `server`. Using `client` filters the list to flags whose client-side SDK availability is set to use the client-side ID. Using `mobile` filters to flags set to use the mobile key. Using `anyClient` filters to flags set to use either the client-side ID or the mobile key. Using `server` filters to flags set to use neither, that is, to flags only available in server-side SDKs.  | `filter=sdkAvailability:client` | | `segmentTargeted`       | A string. It filters the list to flags that target the segment with this key. This filter requires the `filterEnv` filter. | `filter=segmentTargeted:example-segment-key,filterEnv:production` | | `status`                | A string, either `new`, `inactive`, `active`, or `launched`. It filters the list to flags with the specified status in the specified environment. This filter requires the `filterEnv` filter. | `filter=status:active,filterEnv:production` | | `tags`                  | A `+`-separated list of tags. It filters the list to flags that have all of the tags in the list. | `filter=tags:beta+test` | | `type`                  | A string, either `temporary` or `permanent`. It filters the list to flags with the specified type. | `filter=type:permanent` |  The documented values for the `filter` query are prior to URL encoding. For example, the `+` in `filter=tags:beta+test` must be encoded to `%2B`.  By default, this endpoint returns all flags. You can page through the list with the `limit` parameter and by following the `first`, `prev`, `next`, and `last` links in the returned `_links` field. These links will not be present if the pages they refer to don't exist. For example, the `first` and `prev` links will be missing from the response on the first page.  ### Sorting flags  You can sort flags based on the following fields:  - `creationDate` sorts by the creation date of the flag. - `key` sorts by the key of the flag. - `maintainerId` sorts by the flag maintainer. - `name` sorts by flag name. - `tags` sorts by tags. - `targetingModifiedDate` sorts by the date that the flag's targeting rules were last modified in a given environment. It must be used with `env` parameter and it can not be combined with any other sort. If multiple `env` values are provided, it will perform sort using the first one. For example, `sort=-targetingModifiedDate&env=production&env=staging` returns results sorted by `targetingModifiedDate` for the `production` environment. - `type` sorts by flag type  All fields are sorted in ascending order by default. To sort in descending order, prefix the field with a dash ( - ). For example, `sort=-name` sorts the response by flag name in descending order.  ### Expanding response  LaunchDarkly supports the `expand` query param to include additional fields in the response, with the following fields:  - `codeReferences` includes code references for the feature flag - `evaluation` includes evaluation information within returned environments, including which context kinds the flag has been evaluated for in the past 30 days - `migrationSettings` includes migration settings information within the flag and within returned environments. These settings are only included for migration flags, that is, where `purpose` is `migration`.  For example, `expand=evaluation` includes the `evaluation` field in the response.  ### Migration flags For migration flags, the cohort information is included in the `rules` property of a flag's response, and default cohort information is included in the `fallthrough` property of a flag's response. To learn more, read [Migration Flags](https://docs.launchdarkly.com/home/flag-types/migration-flags). 
 
 ### Examples
 
@@ -948,7 +948,7 @@ end
 
 Create a feature flag
 
-Create a feature flag with the given name, key, and variations.  ### Creating a migration flag  When you create a migration flag, the variations are pre-determined based on the number of stages in the migration. To create a migration flag, omit the `variations` and `defaults` information. Instead, provide a `purpose` of `migration`, and `migrationSettings`. If you create a migration flag with six stages, `contextKind` is required. Otherwise, it should be omitted.  Here's an example:  ```json {   \"key\": \"flag-key-123\",   \"purpose\": \"migration\",   \"migrationSettings\": {     \"stageCount\": 6,     \"contextKind\": \"account\"   } } ```  To learn more, read [Migration Flags](https://docs.launchdarkly.com/home/flag-types/migration-flags). 
+Create a feature flag with the given name, key, and variations.  <details> <summary>Click to expand instructions for <strong>creating a migration flag</strong></summary>  ### Creating a migration flag  When you create a migration flag, the variations are pre-determined based on the number of stages in the migration.  To create a migration flag, omit the `variations` and `defaults` information. Instead, provide a `purpose` of `migration`, and `migrationSettings`. If you create a migration flag with six stages, `contextKind` is required. Otherwise, it should be omitted.  Here's an example:  ```json {   \"key\": \"flag-key-123\",   \"purpose\": \"migration\",   \"migrationSettings\": {     \"stageCount\": 6,     \"contextKind\": \"account\"   } } ```  To learn more, read [Migration Flags](https://docs.launchdarkly.com/home/flag-types/migration-flags).  </details> 
 
 ### Examples
 

data/docs/InsightsChartsBetaApi.md

@@ -7,7 +7,7 @@ All URIs are relative to *https://app.launchdarkly.com*
 | [**get_deployment_frequency_chart**](InsightsChartsBetaApi.md#get_deployment_frequency_chart) | **GET** /api/v2/engineering-insights/charts/deployments/frequency | Get deployment frequency chart data |
 | [**get_flag_status_chart**](InsightsChartsBetaApi.md#get_flag_status_chart) | **GET** /api/v2/engineering-insights/charts/flags/status | Get flag status chart data |
 | [**get_lead_time_chart**](InsightsChartsBetaApi.md#get_lead_time_chart) | **GET** /api/v2/engineering-insights/charts/lead-time | Get lead time chart data |
-| [**get_release_frequency_chart**](InsightsChartsBetaApi.md#get_release_frequency_chart) | **GET** /api/v2/engineering-insights/charts/releases/frequency | Get replease frequency chart data |
+| [**get_release_frequency_chart**](InsightsChartsBetaApi.md#get_release_frequency_chart) | **GET** /api/v2/engineering-insights/charts/releases/frequency | Get release frequency chart data |
 | [**get_stale_flags_chart**](InsightsChartsBetaApi.md#get_stale_flags_chart) | **GET** /api/v2/engineering-insights/charts/flags/stale | Get stale flags chart data |
 
 
@@ -270,7 +270,7 @@ end
 
 > <InsightsChart> get_release_frequency_chart(project_key, environment_key, opts)
 
-Get replease frequency chart data
+Get release frequency chart data
 
 Get release frequency chart data. Engineering insights displays release frequency data in the [release frequency metric view](https://docs.launchdarkly.com/home/engineering-insights/metrics/release).
 
@@ -292,7 +292,7 @@ project_key = 'project_key_example' # String | The project key
 environment_key = 'environment_key_example' # String | The environment key
 opts = {
   application_key: 'application_key_example', # String | Comma separated list of application keys
-  has_experiments: true, # Boolean | Filter events to those associated with an experiment
+  has_experiments: true, # Boolean | Filter events to those associated with an experiment (`true`) or without an experiment (`false`)
   global: 'global_example', # String | Filter to include or exclude global events. Default value is `include`. Options: `include`, `exclude`
   group_by: 'group_by_example', # String | Property to group results by. Options: `impact`
   from: Time.parse('2013-10-20T19:20:30+01:00'), # Time | Unix timestamp in milliseconds. Default value is 7 days ago.
@@ -303,7 +303,7 @@ opts = {
 }
 
 begin
-  # Get replease frequency chart data
+  # Get release frequency chart data
   result = api_instance.get_release_frequency_chart(project_key, environment_key, opts)
   p result
 rescue LaunchDarklyApi::ApiError => e
@@ -319,7 +319,7 @@ This returns an Array which contains the response data, status code and headers.
 
 ```ruby
 begin
-  # Get replease frequency chart data
+  # Get release frequency chart data
   data, status_code, headers = api_instance.get_release_frequency_chart_with_http_info(project_key, environment_key, opts)
   p status_code # => 2xx
   p headers # => { ... }
@@ -336,7 +336,7 @@ end
 | **project_key** | **String** | The project key |  |
 | **environment_key** | **String** | The environment key |  |
 | **application_key** | **String** | Comma separated list of application keys | [optional] |
-| **has_experiments** | **Boolean** | Filter events to those associated with an experiment | [optional] |
+| **has_experiments** | **Boolean** | Filter events to those associated with an experiment (&#x60;true&#x60;) or without an experiment (&#x60;false&#x60;) | [optional] |
 | **global** | **String** | Filter to include or exclude global events. Default value is &#x60;include&#x60;. Options: &#x60;include&#x60;, &#x60;exclude&#x60; | [optional] |
 | **group_by** | **String** | Property to group results by. Options: &#x60;impact&#x60; | [optional] |
 | **from** | **Time** | Unix timestamp in milliseconds. Default value is 7 days ago. | [optional] |

data/docs/InsightsFlagEventsBetaApi.md

@@ -35,7 +35,7 @@ opts = {
   application_key: 'application_key_example', # String | Comma separated list of application keys
   query: 'query_example', # String | Filter events by flag key
   impact_size: 'impact_size_example', # String | Filter events by impact size. A small impact created a less than 20% change in the proportion of end users receiving one or more flag variations. A medium impact created between a 20%-80% change. A large impact created a more than 80% change. Options: `none`, `small`, `medium`, `large`
-  has_experiments: true, # Boolean | Filter events to those associated with an experiment
+  has_experiments: true, # Boolean | Filter events to those associated with an experiment (`true`) or without an experiment (`false`)
   global: 'global_example', # String | Filter to include or exclude global events. Default value is `include`. Options: `include`, `exclude`
   expand: 'expand_example', # String | Expand properties in response. Options: `experiments`
   limit: 789, # Integer | The number of deployments to return. Default is 20. Maximum allowed is 100.
@@ -81,7 +81,7 @@ end
 | **application_key** | **String** | Comma separated list of application keys | [optional] |
 | **query** | **String** | Filter events by flag key | [optional] |
 | **impact_size** | **String** | Filter events by impact size. A small impact created a less than 20% change in the proportion of end users receiving one or more flag variations. A medium impact created between a 20%-80% change. A large impact created a more than 80% change. Options: `none`, `small`, `medium`, `large` | [optional] |
-| **has_experiments** | **Boolean** | Filter events to those associated with an experiment | [optional] |
+| **has_experiments** | **Boolean** | Filter events to those associated with an experiment (`true`) or without an experiment (`false`) | [optional] |
 | **global** | **String** | Filter to include or exclude global events. Default value is `include`. Options: `include`, `exclude` | [optional] |
 | **expand** | **String** | Expand properties in response. Options: `experiments` | [optional] |
 | **limit** | **Integer** | The number of deployments to return. Default is 20. Maximum allowed is 100. | [optional] |

data/docs/MetricListingRep.md

@@ -26,9 +26,9 @@
 | **unit** | **String** | For numeric custom metrics, the unit of measure | [optional] |
 | **event_key** | **String** | For custom metrics, the event key to use in your code | [optional] |
 | **randomization_units** | **Array<String>** | An array of randomization units allowed for this metric | [optional] |
-| **unit_aggregation_type** | **String** | The method in which multiple unit event values are aggregated | [optional] |
-| **analysis_type** | **String** | The strategy for analyzing metric events | [optional] |
-| **percentile_value** | **Integer** | The percentile, an integer denoting the target percentile between 0 and 100. Only present when <code>analysisType</code> is <code>percentile</code>. | [optional] |
+| **unit_aggregation_type** | **String** | The method by which multiple unit event values are aggregated | [optional] |
+| **analysis_type** | **String** | The method for analyzing metric events | [optional] |
+| **percentile_value** | **Integer** | The percentile for the analysis method. An integer denoting the target percentile between 0 and 100. Required when <code>analysisType</code> is <code>percentile</code>. | [optional] |
 | **event_default** | [**MetricEventDefaultRep**](MetricEventDefaultRep.md) |  | [optional] |
 
 ## Example

data/docs/MetricPost.md

@@ -17,7 +17,10 @@
 | **success_criteria** | **String** | Success criteria. Required for custom numeric metrics, optional for custom conversion metrics. | [optional] |
 | **tags** | **Array<String>** | Tags for the metric | [optional] |
 | **randomization_units** | **Array<String>** | An array of randomization units allowed for this metric | [optional] |
-| **unit_aggregation_type** | **String** | The method in which multiple unit event values are aggregated | [optional] |
+| **unit_aggregation_type** | **String** | The method by which multiple unit event values are aggregated | [optional] |
+| **analysis_type** | **String** | The method for analyzing metric events | [optional] |
+| **percentile_value** | **Integer** | The percentile for the analysis method. An integer denoting the target percentile between 0 and 100. Required when <code>analysisType</code> is <code>percentile</code>. | [optional] |
+| **event_default** | [**MetricEventDefaultRep**](MetricEventDefaultRep.md) |  | [optional] |
 
 ## Example
 
@@ -38,7 +41,10 @@ instance = LaunchDarklyApi::MetricPost.new(
   success_criteria: HigherThanBaseline,
   tags: ["example-tag"],
   randomization_units: ["user"],
-  unit_aggregation_type: average
+  unit_aggregation_type: average,
+  analysis_type: mean,
+  percentile_value: 95,
+  event_default: null
 )
 ```
 

data/docs/MetricRep.md

@@ -26,9 +26,9 @@
 | **unit** | **String** | For numeric custom metrics, the unit of measure | [optional] |
 | **event_key** | **String** | For custom metrics, the event key to use in your code | [optional] |
 | **randomization_units** | **Array<String>** | An array of randomization units allowed for this metric | [optional] |
-| **unit_aggregation_type** | **String** | The method in which multiple unit event values are aggregated | [optional] |
-| **analysis_type** | **String** | The strategy for analyzing metric events | [optional] |
-| **percentile_value** | **Integer** | The percentile, an integer denoting the target percentile between 0 and 100. Only present when <code>analysisType</code> is <code>percentile</code>. | [optional] |
+| **unit_aggregation_type** | **String** | The method by which multiple unit event values are aggregated | [optional] |
+| **analysis_type** | **String** | The method for analyzing metric events | [optional] |
+| **percentile_value** | **Integer** | The percentile for the analysis method. An integer denoting the target percentile between 0 and 100. Required when <code>analysisType</code> is <code>percentile</code>. | [optional] |
 | **event_default** | [**MetricEventDefaultRep**](MetricEventDefaultRep.md) |  | [optional] |
 | **experiments** | [**Array<DependentExperimentRep>**](DependentExperimentRep.md) |  | [optional] |
 | **metric_groups** | [**Array<DependentMetricGroupRep>**](DependentMetricGroupRep.md) | Metric groups that use this metric | [optional] |

data/docs/Project.md

@@ -10,6 +10,7 @@
 | **include_in_snippet_by_default** | **Boolean** | Whether or not flags created in this project are made available to the client-side JavaScript SDK by default |  |
 | **default_client_side_availability** | [**ClientSideAvailability**](ClientSideAvailability.md) |  | [optional] |
 | **name** | **String** | A human-friendly name for the project |  |
+| **_access** | [**Access**](Access.md) |  | [optional] |
 | **tags** | **Array<String>** | A list of tags for the project |  |
 | **default_release_pipeline_key** | **String** | The key of the default release pipeline for this project | [optional] |
 | **environments** | [**Environments**](Environments.md) |  | [optional] |
@@ -26,6 +27,7 @@ instance = LaunchDarklyApi::Project.new(
   include_in_snippet_by_default: true,
   default_client_side_availability: null,
   name: My Project,
+  _access: null,
   tags: ["ops"],
   default_release_pipeline_key: null,
   environments: null

data/docs/ProjectRep.md

@@ -10,6 +10,7 @@
 | **include_in_snippet_by_default** | **Boolean** | Whether or not flags created in this project are made available to the client-side JavaScript SDK by default |  |
 | **default_client_side_availability** | [**ClientSideAvailability**](ClientSideAvailability.md) |  | [optional] |
 | **name** | **String** | A human-friendly name for the project |  |
+| **_access** | [**Access**](Access.md) |  | [optional] |
 | **tags** | **Array<String>** | A list of tags for the project |  |
 | **default_release_pipeline_key** | **String** | The key of the default release pipeline for this project | [optional] |
 | **environments** | [**Array<Environment>**](Environment.md) | A list of environments for the project |  |
@@ -26,6 +27,7 @@ instance = LaunchDarklyApi::ProjectRep.new(
   include_in_snippet_by_default: true,
   default_client_side_availability: null,
   name: My Project,
+  _access: null,
   tags: ["ops"],
   default_release_pipeline_key: null,
   environments: null

data/docs/ReleaseAudience.md

@@ -0,0 +1,20 @@
+# LaunchDarklyApi::ReleaseAudience
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **environment** | [**EnvironmentSummary**](EnvironmentSummary.md) |  |  |
+| **name** | **String** | The release phase name |  |
+
+## Example
+
+```ruby
+require 'launchdarkly_api'
+
+instance = LaunchDarklyApi::ReleaseAudience.new(
+  environment: null,
+  name: Phase 1 - Testing
+)
+```
+

data/docs/ReleasePhase.md

@@ -10,7 +10,7 @@
 | **_creation_date** | **Integer** |  |  |
 | **_completion_date** | **Integer** |  | [optional] |
 | **_completed_by** | [**CompletedBy**](CompletedBy.md) |  | [optional] |
-| **_audiences** | [**Array<Audience>**](Audience.md) | A logical grouping of one or more environments that share attributes for rolling out changes |  |
+| **_audiences** | [**Array<ReleaseAudience>**](ReleaseAudience.md) | A logical grouping of one or more environments that share attributes for rolling out changes |  |
 
 ## Example