launchdarkly_api 8.0.0 → 10.0.0

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: launchdarkly_api
 version: !ruby/object:Gem::Version
-  version: 8.0.0
+  version: 10.0.0
 platform: ruby
 authors:
 - OpenAPI-Generator
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-03-11 00:00:00.000000000 Z
+date: 2022-07-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: typhoeus
@@ -106,11 +106,15 @@ description: '# Overview  ## Authentication  All REST API resources are authenti
   set to `application/json`.  ### Summary and detailed representations  When you fetch
   a list of resources, the response includes only the most important attributes of
   each resource. This is a _summary representation_ of the resource. When you fetch
-  an individual resource (for example, a single feature flag), you receive a _detailed
-  representation_ containing all of the attributes of the resource.  The best way
-  to find a detailed representation is to follow links. Every summary representation
-  includes a link to its detailed representation.  ### Links and addressability  The
-  best way to navigate the API is by following links. These are attributes in representations
+  an individual resource, such as a single feature flag, you receive a _detailed representation_
+  of the resource.  The best way to find a detailed representation is to follow links.
+  Every summary representation includes a link to its detailed representation.  In
+  most cases, the detailed representation contains all of the attributes of the resource.
+  In a few cases, the detailed representation contains many, but not all, of the attributes
+  of the resource. Typically this happens when an attribute of the requested resource
+  is itself paginated. You can request that the response include a particular attribute
+  by using the `expand` request parameter.  ### Links and addressability  The best
+  way to navigate the API is by following links. These are attributes in representations
   that link to other resources. The API always uses the same format for links:  -
   Links to other resources within the API are encapsulated in a `_links` object. -
   If the resource has a corresponding link to HTML content on the site, it is stored
@@ -124,96 +128,106 @@ description: '# Overview  ## Authentication  All REST API resources are authenti
   are always represented as a JSON object with an `items` attribute containing an
   array of representations. Like all other representations, collections have `_links`
   defined at the top level.  Paginated collections include `first`, `last`, `next`,
-  and `prev` links containing a URL with the respective set of elements in the collection.  ##
-  Updates  Resources that accept partial updates use the `PATCH` verb, and support
-  the [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902) format. Some resources
-  also support the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386)
-  format. In addition, some resources support optional comments that can be submitted
-  with updates. Comments appear in outgoing webhooks, the audit log, and other integrations.  ###
-  Updates via JSON Patch  [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902)
-  is a way to specify the modifications to perform on a resource. For example, in
-  this feature flag representation:  ```json {     "name": "New recommendations engine",     "key":
-  "engine.enable",     "description": "This is the description",     ... } ```  You
-  can change the feature flag''s description with the following patch document:  ```json
+  and `prev` links containing a URL with the respective set of elements in the collection.  ###
+  Expanding responses  Sometimes the detailed representation of a resource does not
+  include all of the attributes of the resource by default. If this is the case, the
+  request method will clearly document this and describe which attributes you can
+  include in an expanded response.  To include the additional attributes, append the
+  `expand` request parameter to your request and add a comma-separated list of the
+  attributes to include. For example, when you append `?expand=members,roles` to the
+  [Get team](/tag/Teams-(beta)#operation/getTeam) endpoint, the expanded response
+  includes both of these attributes.  ## Updates  Resources that accept partial updates
+  use the `PATCH` verb. Most resources support the [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902)
+  format. Some resources also support the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386)
+  format, and some resources support the [semantic patch](/reference#updates-using-semantic-patch)
+  format, which is a way to specify the modifications to perform as a set of executable
+  instructions. Each resource supports optional [comments](/reference#updates-with-comments)
+  that you can submit with updates. Comments appear in outgoing webhooks, the audit
+  log, and other integrations.  ### Updates using JSON patch  [JSON Patch](https://datatracker.ietf.org/doc/html/rfc6902)
+  is a way to specify the modifications to perform on a resource. JSON patch uses
+  paths and a limited set of operations to describe how to transform the current state
+  of the resource into a new state. JSON patch documents are always arrays, where
+  each element contains an operation, a path to the field to update, and the new value.  For
+  example, in this feature flag representation:  ```json {     "name": "New recommendations
+  engine",     "key": "engine.enable",     "description": "This is the description",     ...
+  } ``` You can change the feature flag''s description with the following patch document:  ```json
   [{ "op": "replace", "path": "/description", "value": "This is the new description"
-  }] ```  JSON Patch documents are always arrays. You can specify multiple modifications
-  to perform in a single request. You can also test that certain preconditions are
-  met before applying the patch:  ```json [   { "op": "test", "path": "/version",
-  "value": 10 },   { "op": "replace", "path": "/description", "value": "The new description"
-  } ] ```  The above patch request tests whether the feature flag''s `version` is
-  `10`, and if so, changes the feature flag''s description.  Attributes that aren''t
-  editable, like a resource''s `_links`, have names that start with an underscore.  ###
-  Updates via JSON Merge Patch  The API also supports the [JSON Merge Patch](https://datatracker.ietf.org/doc/html/rfc7386)
-  format, as well as the [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag)
-  resource.  JSON Merge Patch is less expressive than JSON Patch but in many cases,
-  it is simpler to construct a merge patch document. For example, you can change a
-  feature flag''s description with the following merge patch document:  ```json {   "description":
-  "New flag description" } ```  ### Updates with comments  You can submit optional
-  comments with `PATCH` changes. The [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag)
-  resource supports comments.  To submit a comment along with a JSON Patch document,
-  use the following format:  ```json {   "comment": "This is a comment string",   "patch":
-  [{ "op": "replace", "path": "/description", "value": "The new description" }] }
-  ```  To submit a comment along with a JSON Merge Patch document, use the following
-  format:  ```json {   "comment": "This is a comment string",   "merge": { "description":
-  "New flag description" } } ```  ### Updates via semantic patches  The API also supports
-  the Semantic patch format. A semantic `PATCH` is a way to specify the modifications
-  to perform on a resource as a set of executable instructions.  JSON Patch uses paths
-  and a limited set of operations to describe how to transform the current state of
-  the resource into a new state. Semantic patch allows you to be explicit about intent
-  using precise, custom instructions. In many cases, semantic patch instructions can
-  also be defined independently of the current state of the resource. This can be
-  useful when defining a change that may be applied at a future date.  For example,
-  in this feature flag configuration in environment Production:  ```json {     "name":
-  "Alternate sort order",     "kind": "boolean",     "key": "sort.order",    ...     "environments":
-  {         "production": {             "on": true,             "archived": false,             "salt":
-  "c29ydC5vcmRlcg==",             "sel": "8de1085cb7354b0ab41c0e778376dfd3",             "lastModified":
-  1469131558260,             "version": 81,             "targets": [                 {                     "values":
-  [                         "Gerhard.Little@yahoo.com"                     ],                     "variation":
-  0                 },                 {                     "values": [                         "1461797806429-33-861961230",                         "438580d8-02ee-418d-9eec-0085cab2bdf0"                     ],                     "variation":
-  1                 }             ],             "rules": [],             "fallthrough":
-  {                 "variation": 0             },             "offVariation": 1,             "prerequisites":
-  [],             "_site": {                 "href": "/default/production/features/sort.order",                 "type":
-  "text/html"             }        }     } } ```  You can add a date you want a user
-  to be removed from the feature flag''s user targets. For example, “remove user 1461797806429-33-861961230
-  from the user target for variation 0 on the Alternate sort order flag in the production
-  environment on Wed Jul 08 2020 at 15:27:41 pm”. This is done using the following:  ```json
-  {   "comment": "update expiring user targets",   "instructions": [     {       "kind":
-  "removeExpireUserTargetDate",       "userKey": "userKey",       "variationId": "978d53f9-7fe3-4a63-992d-97bcb4535dc8"     },     {       "kind":
-  "updateExpireUserTargetDate",       "userKey": "userKey2",       "variationId":
-  "978d53f9-7fe3-4a63-992d-97bcb4535dc8",       "value": 1587582000000     },     {       "kind":
-  "addExpireUserTargetDate",       "userKey": "userKey3",       "variationId": "978d53f9-7fe3-4a63-992d-97bcb4535dc8",       "value":
-  1594247266386     }   ] } ```  Here is another example. In this feature flag configuration:  ```json
-  {   "name": "New recommendations engine",   "key": "engine.enable",   "environments":
-  {     "test": {       "on": true     }   } } ```  You can change the feature flag''s
-  description with the following patch document as a set of executable instructions.
-  For example, “add user X to targets for variation Y and remove user A from targets
-  for variation B for test flag”:  ```json {   "comment": "",   "instructions": [     {       "kind":
-  "removeUserTargets",       "values": ["438580d8-02ee-418d-9eec-0085cab2bdf0"],       "variationId":
-  "852cb784-54ff-46b9-8c35-5498d2e4f270"     },     {       "kind": "addUserTargets",       "values":
-  ["438580d8-02ee-418d-9eec-0085cab2bdf0"],       "variationId": "1bb18465-33b6-49aa-a3bd-eeb6650b33ad"     }   ]
-  } ```  > ### Supported semantic patch API endpoints > > - [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag)
-  > - [Update expiring user targets on feature flag](/tag/Feature-flags#operation/patchExpiringUserTargets)
+  }] ```  You can specify multiple modifications to perform in a single request. You
+  can also test that certain preconditions are met before applying the patch:  ```json
+  [   { "op": "test", "path": "/version", "value": 10 },   { "op": "replace", "path":
+  "/description", "value": "The new description" } ] ```  The above patch request
+  tests whether the feature flag''s `version` is `10`, and if so, changes the feature
+  flag''s description.  Attributes that aren''t editable, like a resource''s `_links`,
+  have names that start with an underscore.  ### Updates using JSON merge patch  [JSON
+  merge patch](https://datatracker.ietf.org/doc/html/rfc7386) is another format for
+  specifying the modifications to perform on a resource. JSON merge patch is less
+  expressive than JSON patch but in many cases, it is simpler to construct a merge
+  patch document. For example, you can change a feature flag''s description with the
+  following merge patch document:  ```json {   "description": "New flag description"
+  } ```  ### Updates using semantic patch  The API also supports the semantic patch
+  format. A semantic `PATCH` is a way to specify the modifications to perform on a
+  resource as a set of executable instructions.  Semantic patch allows you to be explicit
+  about intent using precise, custom instructions. In many cases, you can define semantic
+  patch instructions independently of the current state of the resource. This can
+  be useful when defining a change that may be applied at a future date.  To make
+  a semantic patch request, you must append `domain-model=launchdarkly.semanticpatch`
+  to your `Content-Type` header.  Here''s how:  ``` Content-Type: application/json;
+  domain-model=launchdarkly.semanticpatch ```  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.  The body of a semantic patch request takes
+  the following properties:  * `comment` (string): (Optional) A description of the
+  update. * `environmentKey` (string): (Required for some resources only) The environment
+  key. * `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. The documentation for each resource that supports
+  semantic patch includes the available instructions and any additional parameters.  For
+  example:  ```json {   "comment": "optional comment",   "instructions": [ {"kind":
+  "turnFlagOn"} ] } ```  If any instruction in the patch encounters an error, the
+  endpoint returns an error and will not change the resource. In general, each instruction
+  silently does nothing if the resource is already in the state you request.  > ###
+  Supported semantic patch API endpoints > > - [Patch experiment](/tag/Experiments-(beta)#operation/patchExperiment)
+  > - [Patch segment](/tag/Segments#operation/patchSegment) > - [Update feature flag](/tag/Feature-flags#operation/patchFeatureFlag)
+  > - [Update flag trigger](/tag/Flag-triggers#operation/patchTriggerWorkflow) > -
+  [Update expiring user targets on feature flag](/tag/Feature-flags#operation/patchExpiringUserTargets)
   > - [Update expiring user target for flags](/tag/User-settings#operation/patchExpiringFlagsForUser)
-  > - [Update expiring user targets on segment](/tag/Segments#operation/patchExpiringUserTargetsForSegment)  ##
-  Errors  The API always returns errors in a common format. Here''s an example:  ```json
-  {   "code": "invalid_request",   "message": "A feature with that key already exists",   "id":
+  > - [Update expiring user targets for segment](/tag/Segments#operation/patchExpiringUserTargetsForSegment)
+  > - [Update scheduled changes workflow](/tag/Scheduled-changes#operation/patchFlagConfigScheduledChange)
+  > - [Update team](/tag/Teams-(beta)#operation/patchTeam)  ### Updates with comments  You
+  can submit optional comments with `PATCH` changes.  To submit a comment along with
+  a JSON Patch document, use the following format:  ```json {   "comment": "This is
+  a comment string",   "patch": [{ "op": "replace", "path": "/description", "value":
+  "The new description" }] } ```  To submit a comment along with a JSON merge patch
+  document, use the following format:  ```json {   "comment": "This is a comment string",   "merge":
+  { "description": "New flag description" } } ```  To submit a comment along with
+  a semantic patch, use the following format:  ```json {   "comment": "This is a comment
+  string",   "instructions": [ {"kind": "turnFlagOn"} ] } ```  ## Errors  The API
+  always returns errors in a common format. Here''s an example:  ```json {   "code":
+  "invalid_request",   "message": "A feature with that key already exists",   "id":
   "30ce6058-87da-11e4-b116-123b93f75cba" } ```  The general class of error is indicated
   by the `code`. The `message` is a human-readable explanation of what went wrong.
   The `id` is a unique identifier. Use it when you''re working with LaunchDarkly support
   to debug a problem with a specific API call.  ### HTTP Status - Error Response Codes  |
-  Code | Definition        | Desc.                                                                                       |
+  Code | Definition        | Description                                                                                       |
   Possible Solution                                                | | ---- | -----------------
   | -------------------------------------------------------------------------------------------
-  | ---------------------------------------------------------------- | | 400  | Bad
-  Request       | A request that fails may return this HTTP response code.                                    |
-  Ensure JSON syntax in request body is correct.                   | | 401  | Unauthorized      |
-  User doesn''t have permission to an API call.                                                |
-  Ensure your SDK key is good.                                     | | 403  | Forbidden         |
-  User does not have permission for operation.                                                |
-  Ensure that the user or access token has proper permissions set. | | 409  | Conflict          |
-  The API request could not be completed because it conflicted with a concurrent API
-  request. | Retry your request.                                              | |
-  429  | Too many requests | See [Rate limiting](/#section/Rate-limiting).                                               |
+  | ---------------------------------------------------------------- | | 400  | Invalid
+  request       | The request cannot be understood.                                    |
+  Ensure JSON syntax in request body is correct.                   | | 401  | Invalid
+  access token      | User is unauthorized or does not have permission for this API
+  call.                                                | Ensure your API access token
+  is valid and has the appropriate permissions.                                     |
+  | 403  | Forbidden         | User does not have access to this resource.                                                |
+  Ensure that the user or access token has proper permissions set. | | 404  | Invalid
+  resource identifier | The requested resource is not valid. | Ensure that the resource
+  is correctly identified by id or key. | | 405  | Method not allowed | The request
+  method is not allowed on this resource. | Ensure that the HTTP verb is correct.
+  | | 409  | Conflict          | The API request can not be completed because it conflicted
+  with a concurrent API request. | Retry your request.                                              |
+  | 422  | Unprocessable entity | The API request can not be completed because the
+  update description can not be understood. | Ensure that the request body is correct
+  for the type of patch you are using (JSON patch or semantic patch). | 429  | Too
+  many requests | Read [Rate limiting](/#section/Rate-limiting).                                               |
   Wait and try again later.                                        |  ## CORS  The
   LaunchDarkly API supports Cross Origin Resource Sharing (CORS) for AJAX requests
   from any origin. If an `Origin` header is given in a request, it will be echoed
@@ -235,13 +249,12 @@ description: '# Overview  ## Authentication  All REST API resources are authenti
   limiting and SDKs > > LaunchDarkly SDKs are never rate limited and do not use the
   API endpoints defined here. LaunchDarkly uses a different set of approaches, including
   streaming/server-sent events and a global CDN, to ensure availability to the routes
-  used by LaunchDarkly SDKs. > > The client-side ID is safe to embed in untrusted
-  contexts. It''s designed for use in client-side JavaScript.  ### Global rate limits  Authenticated
-  requests are subject to a global limit. This is the maximum number of calls that
-  can be made to the API per ten seconds. All personal access tokens on the account
-  share this limit, so exceeding the limit with one access token will impact other
-  tokens. Calls that are subject to global rate limits will return the headers below:  |
-  Header name                    | Description                                                                      |
+  used by LaunchDarkly SDKs.  ### Global rate limits  Authenticated requests are subject
+  to a global limit. This is the maximum number of calls that can be made to the API
+  per ten seconds. All personal access tokens on the account share this limit, so
+  exceeding the limit with one access token will impact other tokens. Calls that are
+  subject to global rate limits will return the headers below:  | Header name                    |
+  Description                                                                      |
   | ------------------------------ | --------------------------------------------------------------------------------
   | | `X-Ratelimit-Global-Remaining` | The maximum number of requests the account
   is permitted to make per ten seconds. | | `X-Ratelimit-Reset`            | The time
@@ -291,9 +304,9 @@ description: '# Overview  ## Authentication  All REST API resources are authenti
   mark beta resources with a "Beta" callout in our documentation, pictured below:  >
   ### This feature is in beta > > To use this feature, pass in a header including
   the `LD-API-Version` key with value set to `beta`. Use this header with each call.
-  To learn more, read [Beta resources](/#section/Beta-resources).  ### Using beta
-  resources  To use a beta resource, you must include a header in the request. If
-  you call a beta resource without this header, you''ll receive a `403` response.  Use
+  To learn more, read [Beta resources](/#section/Overview/Beta-resources).  ### Using
+  beta resources  To use a beta resource, you must include a header in the request.
+  If you call a beta resource without this header, you''ll receive a `403` response.  Use
   this header:  ``` LD-API-Version: beta ```  ## Versioning  We try hard to keep our
   REST API backwards compatible, but we occasionally have to make backwards-incompatible
   changes in the process of shipping new features. These breaking changes can cause
@@ -303,10 +316,10 @@ description: '# Overview  ## Authentication  All REST API resources are authenti
   support for multiple API versions so you can migrate from your current API version
   to a new version at your own pace.  ### Setting the API version per request  You
   can set the API version on a specific request by sending an `LD-API-Version` header,
-  as shown in the example below:  ``` LD-API-Version: 20210729 ```  The header value
+  as shown in the example below:  ``` LD-API-Version: 20220603 ```  The header value
   is the version number of the API version you''d like to request. The number for
   each version corresponds to the date the version was released in yyyymmdd format.
-  In the example above the version `20210729` corresponds to July 29, 2021.  ### Setting
+  In the example above the version `20220603` corresponds to June 03, 2022.  ### Setting
   the API version per access token  When creating an access token, you must specify
   a specific version of the API to use. This ensures that integrations using this
   token cannot be broken by version changes.  Tokens created before versioning was
@@ -316,23 +329,28 @@ description: '# Overview  ## Authentication  All REST API resources are authenti
   set the header described above.  > ### Best practice: Set the header for every client
   or integration > > We recommend that you set the API version header explicitly in
   any client or integration you build. > > Only rely on the access token API version
-  during manual testing.  ### API version changelog  | Version | Changes | |---|---|
-  | `20210729` | <ul><li>Changed the [create approval request](/tag/Approvals#operation/postApprovalRequest)
-  return value. It now returns HTTP Status Code `201` instead of `200`.</li><li> Changed
-  the [get users](/tag/Users#operation/getUser) return value. It now returns a user
-  record, not a user. </li><li> Added additional optional fields to environment, segments,
-  flags, members, and segments, including the ability to create Big Segments. </li><li>
-  Added default values for flag variations when new environments are created. </li><li>
-  Added filtering and pagination for getting flags and members, including `limit`,
-  `number`, `filter`, and `sort` query parameters. </li><li> Added endpoints for expiring
-  user targets for flags and segments, scheduled changes, access tokens, Relay Proxy
-  configuration, integrations and subscriptions, and approvals. </li></ul> | | `20191212`
-  | <ul><li>[List feature flags](/tag/Feature-flags#operation/getFeatureFlags) now
-  defaults to sending summaries of feature flag configurations, equivalent to setting
-  the query parameter `summary=true`. Summaries omit flag targeting rules and individual
-  user targets from the payload. </li><li> Added endpoints for flags, flag status,
-  projects, environments, users, audit logs, members, users, custom roles, segments,
-  usage, streams, events, and data export. </li></ul> | | `20160426` | <ul><li>Initial
+  during manual testing.  ### API version changelog  |<div style="width:75px">Version</div>
+  | Changes | |---|---| | `20220603` | <ul><li>Changed the [list projects](tag/Projects#operation/getProjects)
+  return value:<ul><li>Response is now paginated with a default limit of `20`.</li><li>Added
+  support for filter and sort.</li><li>The project `environments` field is now expandable.
+  This field is omitted by default.</li></ul></li><li>Changed the [get project](tag/Projects#operation/getProject)
+  return value:<ul><li>The `environments` field is now expandable. This field is omitted
+  by default.</li></ul></li></ul> | | `20210729` | <ul><li>Changed the [create approval
+  request](/tag/Approvals#operation/postApprovalRequest) return value. It now returns
+  HTTP Status Code `201` instead of `200`.</li><li> Changed the [get users](/tag/Users#operation/getUser)
+  return value. It now returns a user record, not a user. </li><li> Added additional
+  optional fields to environment, segments, flags, members, and segments, including
+  the ability to create Big Segments. </li><li> Added default values for flag variations
+  when new environments are created. </li><li> Added filtering and pagination for
+  getting flags and members, including `limit`, `number`, `filter`, and `sort` query
+  parameters. </li><li> Added endpoints for expiring user targets for flags and segments,
+  scheduled changes, access tokens, Relay Proxy configuration, integrations and subscriptions,
+  and approvals. </li></ul> | | `20191212` | <ul><li>[List feature flags](/tag/Feature-flags#operation/getFeatureFlags)
+  now defaults to sending summaries of feature flag configurations, equivalent to
+  setting the query parameter `summary=true`. Summaries omit flag targeting rules
+  and individual user targets from the payload. </li><li> Added endpoints for flags,
+  flag status, projects, environments, users, audit logs, members, users, custom roles,
+  segments, usage, streams, events, and data export. </li></ul> | | `20160426` | <ul><li>Initial
   versioning of API. Tokens created before versioning have their version set to this.</li></ul>
   | '
 email:
@@ -369,6 +387,8 @@ files:
 - docs/BranchCollectionRep.md
 - docs/BranchRep.md
 - docs/Clause.md
+- docs/Client.md
+- docs/ClientCollection.md
 - docs/ClientSideAvailability.md
 - docs/ClientSideAvailabilityPost.md
 - docs/CodeReferencesApi.md
@@ -381,6 +401,7 @@ files:
 - docs/CopiedFromEnv.md
 - docs/CreateCopyFlagConfigApprovalRequestRequest.md
 - docs/CreateFlagConfigApprovalRequestRequest.md
+- docs/CredibleIntervalRep.md
 - docs/CustomProperty.md
 - docs/CustomRole.md
 - docs/CustomRolePost.md
@@ -403,15 +424,22 @@ files:
 - docs/Destinations.md
 - docs/Environment.md
 - docs/EnvironmentPost.md
+- docs/Environments.md
 - docs/EnvironmentsApi.md
+- docs/EvaluationReason.md
 - docs/ExecutionOutputRep.md
+- docs/Experiment.md
 - docs/ExperimentAllocationRep.md
+- docs/ExperimentBayesianResultsRep.md
+- docs/ExperimentCollectionRep.md
 - docs/ExperimentEnabledPeriodRep.md
 - docs/ExperimentEnvironmentSettingRep.md
+- docs/ExperimentExpandableProperties.md
 - docs/ExperimentInfoRep.md
 - docs/ExperimentMetadataRep.md
-- docs/ExperimentRep.md
-- docs/ExperimentResultsRep.md
+- docs/ExperimentPatchInput.md
+- docs/ExperimentPost.md
+- docs/ExperimentResults.md
 - docs/ExperimentStatsRep.md
 - docs/ExperimentTimeSeriesSlice.md
 - docs/ExperimentTimeSeriesVariationSlice.md
@@ -440,22 +468,30 @@ files:
 - docs/FlagConfigApprovalRequestsResponse.md
 - docs/FlagCopyConfigEnvironment.md
 - docs/FlagCopyConfigPost.md
+- docs/FlagFollowersByProjEnvGetRep.md
+- docs/FlagFollowersGetRep.md
 - docs/FlagGlobalAttributesRep.md
+- docs/FlagInput.md
 - docs/FlagLinkCollectionRep.md
 - docs/FlagLinkMember.md
 - docs/FlagLinkPost.md
 - docs/FlagLinkRep.md
 - docs/FlagLinksBetaApi.md
 - docs/FlagListingRep.md
+- docs/FlagRep.md
 - docs/FlagScheduledChangesInput.md
 - docs/FlagStatusRep.md
 - docs/FlagSummary.md
 - docs/FlagTriggerInput.md
 - docs/FlagTriggersApi.md
+- docs/FollowFlagMember.md
+- docs/FollowFlagsApi.md
+- docs/FollowersPerFlag.md
 - docs/ForbiddenErrorRep.md
 - docs/HunkRep.md
 - docs/Import.md
 - docs/InitiatorRep.md
+- docs/InstructionUserRequest.md
 - docs/Integration.md
 - docs/IntegrationAuditLogSubscriptionsApi.md
 - docs/IntegrationDeliveryConfiguration.md
@@ -472,7 +508,11 @@ files:
 - docs/Integrations.md
 - docs/InvalidRequestErrorRep.md
 - docs/IpList.md
+- docs/IterationExpandableProperties.md
+- docs/IterationInput.md
+- docs/IterationRep.md
 - docs/LastSeenMetadata.md
+- docs/LegacyExperimentRep.md
 - docs/Link.md
 - docs/Member.md
 - docs/MemberDataRep.md
@@ -484,22 +524,30 @@ files:
 - docs/Members.md
 - docs/MethodNotAllowedErrorRep.md
 - docs/MetricCollectionRep.md
+- docs/MetricInput.md
 - docs/MetricListingRep.md
 - docs/MetricPost.md
 - docs/MetricRep.md
 - docs/MetricSeen.md
+- docs/MetricV2Rep.md
 - docs/MetricsApi.md
 - docs/Modification.md
 - docs/MultiEnvironmentDependentFlag.md
 - docs/MultiEnvironmentDependentFlags.md
 - docs/NewMemberForm.md
 - docs/NotFoundErrorRep.md
+- docs/OAuth2ClientsBetaApi.md
+- docs/OauthClientPost.md
 - docs/OtherApi.md
+- docs/ParameterDefault.md
+- docs/ParameterRep.md
 - docs/ParentResourceRep.md
 - docs/PatchFailedErrorRep.md
+- docs/PatchFlagsRequest.md
 - docs/PatchOperation.md
 - docs/PatchSegmentInstruction.md
 - docs/PatchSegmentRequest.md
+- docs/PatchUsersRequest.md
 - docs/PatchWithComment.md
 - docs/PermissionGrantInput.md
 - docs/PostApprovalRequestApplyRequest.md
@@ -509,6 +557,7 @@ files:
 - docs/Project.md
 - docs/ProjectListingRep.md
 - docs/ProjectPost.md
+- docs/ProjectRep.md
 - docs/ProjectSummary.md
 - docs/Projects.md
 - docs/ProjectsApi.md
@@ -517,6 +566,7 @@ files:
 - docs/RateLimitedErrorRep.md
 - docs/RecentTriggerBody.md
 - docs/ReferenceRep.md
+- docs/RelativeDifferenceRep.md
 - docs/RelayAutoConfigCollectionRep.md
 - docs/RelayAutoConfigPost.md
 - docs/RelayAutoConfigRep.md
@@ -535,6 +585,7 @@ files:
 - docs/ReviewResponse.md
 - docs/Rollout.md
 - docs/Rule.md
+- docs/RuleClause.md
 - docs/ScheduleConditionInputRep.md
 - docs/ScheduleConditionOutputRep.md
 - docs/ScheduledChangesApi.md
@@ -555,9 +606,9 @@ files:
 - docs/Statement.md
 - docs/StatementPost.md
 - docs/StatementPostData.md
-- docs/StatementRep.md
 - docs/StatisticCollectionRep.md
 - docs/StatisticRep.md
+- docs/StatisticsRep.md
 - docs/StatisticsRoot.md
 - docs/StatusConflictErrorRep.md
 - docs/SubjectDataRep.md
@@ -571,16 +622,22 @@ files:
 - docs/TeamCustomRoles.md
 - docs/TeamImportsRep.md
 - docs/TeamMaintainers.md
+- docs/TeamMembers.md
 - docs/TeamPatchInput.md
 - docs/TeamPostInput.md
 - docs/TeamProjects.md
+- docs/TeamRepExpandableProperties.md
 - docs/Teams.md
-- docs/TeamsBetaApi.md
+- docs/TeamsApi.md
 - docs/TimestampRep.md
 - docs/TitleRep.md
 - docs/Token.md
 - docs/TokenDataRep.md
 - docs/Tokens.md
+- docs/TreatmentInput.md
+- docs/TreatmentParameterInput.md
+- docs/TreatmentRep.md
+- docs/TreatmentResultRep.md
 - docs/TriggerPost.md
 - docs/TriggerWorkflowCollectionRep.md
 - docs/TriggerWorkflowRep.md
@@ -599,6 +656,7 @@ files:
 - docs/Users.md
 - docs/UsersApi.md
 - docs/UsersBetaApi.md
+- docs/UsersRep.md
 - docs/ValuePut.md
 - docs/Variation.md
 - docs/VariationOrRolloutRep.md
@@ -609,6 +667,8 @@ files:
 - docs/Webhooks.md
 - docs/WebhooksApi.md
 - docs/WeightedVariation.md
+- docs/WorkflowTemplateMetadata.md
+- docs/WorkflowTemplateParameter.md
 - docs/WorkflowsBetaApi.md
 - git_push.sh
 - launchdarkly_api.gemspec
@@ -627,9 +687,11 @@ files:
 - lib/launchdarkly_api/api/feature_flags_beta_api.rb
 - lib/launchdarkly_api/api/flag_links_beta_api.rb
 - lib/launchdarkly_api/api/flag_triggers_api.rb
+- lib/launchdarkly_api/api/follow_flags_api.rb
 - lib/launchdarkly_api/api/integration_audit_log_subscriptions_api.rb
 - lib/launchdarkly_api/api/integration_delivery_configurations_beta_api.rb
 - lib/launchdarkly_api/api/metrics_api.rb
+- lib/launchdarkly_api/api/o_auth2_clients_beta_api.rb
 - lib/launchdarkly_api/api/other_api.rb
 - lib/launchdarkly_api/api/projects_api.rb
 - lib/launchdarkly_api/api/relay_proxy_configurations_api.rb
@@ -637,7 +699,7 @@ files:
 - lib/launchdarkly_api/api/segments_api.rb
 - lib/launchdarkly_api/api/segments_beta_api.rb
 - lib/launchdarkly_api/api/tags_api.rb
-- lib/launchdarkly_api/api/teams_beta_api.rb
+- lib/launchdarkly_api/api/teams_api.rb
 - lib/launchdarkly_api/api/user_settings_api.rb
 - lib/launchdarkly_api/api/users_api.rb
 - lib/launchdarkly_api/api/users_beta_api.rb
@@ -665,6 +727,8 @@ files:
 - lib/launchdarkly_api/models/branch_collection_rep.rb
 - lib/launchdarkly_api/models/branch_rep.rb
 - lib/launchdarkly_api/models/clause.rb
+- lib/launchdarkly_api/models/client.rb
+- lib/launchdarkly_api/models/client_collection.rb
 - lib/launchdarkly_api/models/client_side_availability.rb
 - lib/launchdarkly_api/models/client_side_availability_post.rb
 - lib/launchdarkly_api/models/condition_base_output_rep.rb
@@ -676,6 +740,7 @@ files:
 - lib/launchdarkly_api/models/copied_from_env.rb
 - lib/launchdarkly_api/models/create_copy_flag_config_approval_request_request.rb
 - lib/launchdarkly_api/models/create_flag_config_approval_request_request.rb
+- lib/launchdarkly_api/models/credible_interval_rep.rb
 - lib/launchdarkly_api/models/custom_property.rb
 - lib/launchdarkly_api/models/custom_role.rb
 - lib/launchdarkly_api/models/custom_role_post.rb
@@ -696,14 +761,21 @@ files:
 - lib/launchdarkly_api/models/destinations.rb
 - lib/launchdarkly_api/models/environment.rb
 - lib/launchdarkly_api/models/environment_post.rb
+- lib/launchdarkly_api/models/environments.rb
+- lib/launchdarkly_api/models/evaluation_reason.rb
 - lib/launchdarkly_api/models/execution_output_rep.rb
+- lib/launchdarkly_api/models/experiment.rb
 - lib/launchdarkly_api/models/experiment_allocation_rep.rb
+- lib/launchdarkly_api/models/experiment_bayesian_results_rep.rb
+- lib/launchdarkly_api/models/experiment_collection_rep.rb
 - lib/launchdarkly_api/models/experiment_enabled_period_rep.rb
 - lib/launchdarkly_api/models/experiment_environment_setting_rep.rb
+- lib/launchdarkly_api/models/experiment_expandable_properties.rb
 - lib/launchdarkly_api/models/experiment_info_rep.rb
 - lib/launchdarkly_api/models/experiment_metadata_rep.rb
-- lib/launchdarkly_api/models/experiment_rep.rb
-- lib/launchdarkly_api/models/experiment_results_rep.rb
+- lib/launchdarkly_api/models/experiment_patch_input.rb
+- lib/launchdarkly_api/models/experiment_post.rb
+- lib/launchdarkly_api/models/experiment_results.rb
 - lib/launchdarkly_api/models/experiment_stats_rep.rb
 - lib/launchdarkly_api/models/experiment_time_series_slice.rb
 - lib/launchdarkly_api/models/experiment_time_series_variation_slice.rb
@@ -729,20 +801,27 @@ files:
 - lib/launchdarkly_api/models/flag_config_approval_requests_response.rb
 - lib/launchdarkly_api/models/flag_copy_config_environment.rb
 - lib/launchdarkly_api/models/flag_copy_config_post.rb
+- lib/launchdarkly_api/models/flag_followers_by_proj_env_get_rep.rb
+- lib/launchdarkly_api/models/flag_followers_get_rep.rb
 - lib/launchdarkly_api/models/flag_global_attributes_rep.rb
+- lib/launchdarkly_api/models/flag_input.rb
 - lib/launchdarkly_api/models/flag_link_collection_rep.rb
 - lib/launchdarkly_api/models/flag_link_member.rb
 - lib/launchdarkly_api/models/flag_link_post.rb
 - lib/launchdarkly_api/models/flag_link_rep.rb
 - lib/launchdarkly_api/models/flag_listing_rep.rb
+- lib/launchdarkly_api/models/flag_rep.rb
 - lib/launchdarkly_api/models/flag_scheduled_changes_input.rb
 - lib/launchdarkly_api/models/flag_status_rep.rb
 - lib/launchdarkly_api/models/flag_summary.rb
 - lib/launchdarkly_api/models/flag_trigger_input.rb
+- lib/launchdarkly_api/models/follow_flag_member.rb
+- lib/launchdarkly_api/models/followers_per_flag.rb
 - lib/launchdarkly_api/models/forbidden_error_rep.rb
 - lib/launchdarkly_api/models/hunk_rep.rb
 - lib/launchdarkly_api/models/import.rb
 - lib/launchdarkly_api/models/initiator_rep.rb
+- lib/launchdarkly_api/models/instruction_user_request.rb
 - lib/launchdarkly_api/models/integration.rb
 - lib/launchdarkly_api/models/integration_delivery_configuration.rb
 - lib/launchdarkly_api/models/integration_delivery_configuration_collection.rb
@@ -757,7 +836,11 @@ files:
 - lib/launchdarkly_api/models/integrations.rb
 - lib/launchdarkly_api/models/invalid_request_error_rep.rb
 - lib/launchdarkly_api/models/ip_list.rb
+- lib/launchdarkly_api/models/iteration_expandable_properties.rb
+- lib/launchdarkly_api/models/iteration_input.rb
+- lib/launchdarkly_api/models/iteration_rep.rb
 - lib/launchdarkly_api/models/last_seen_metadata.rb
+- lib/launchdarkly_api/models/legacy_experiment_rep.rb
 - lib/launchdarkly_api/models/link.rb
 - lib/launchdarkly_api/models/member.rb
 - lib/launchdarkly_api/models/member_data_rep.rb
@@ -769,20 +852,27 @@ files:
 - lib/launchdarkly_api/models/members.rb
 - lib/launchdarkly_api/models/method_not_allowed_error_rep.rb
 - lib/launchdarkly_api/models/metric_collection_rep.rb
+- lib/launchdarkly_api/models/metric_input.rb
 - lib/launchdarkly_api/models/metric_listing_rep.rb
 - lib/launchdarkly_api/models/metric_post.rb
 - lib/launchdarkly_api/models/metric_rep.rb
 - lib/launchdarkly_api/models/metric_seen.rb
+- lib/launchdarkly_api/models/metric_v2_rep.rb
 - lib/launchdarkly_api/models/modification.rb
 - lib/launchdarkly_api/models/multi_environment_dependent_flag.rb
 - lib/launchdarkly_api/models/multi_environment_dependent_flags.rb
 - lib/launchdarkly_api/models/new_member_form.rb
 - lib/launchdarkly_api/models/not_found_error_rep.rb
+- lib/launchdarkly_api/models/oauth_client_post.rb
+- lib/launchdarkly_api/models/parameter_default.rb
+- lib/launchdarkly_api/models/parameter_rep.rb
 - lib/launchdarkly_api/models/parent_resource_rep.rb
 - lib/launchdarkly_api/models/patch_failed_error_rep.rb
+- lib/launchdarkly_api/models/patch_flags_request.rb
 - lib/launchdarkly_api/models/patch_operation.rb
 - lib/launchdarkly_api/models/patch_segment_instruction.rb
 - lib/launchdarkly_api/models/patch_segment_request.rb
+- lib/launchdarkly_api/models/patch_users_request.rb
 - lib/launchdarkly_api/models/patch_with_comment.rb
 - lib/launchdarkly_api/models/permission_grant_input.rb
 - lib/launchdarkly_api/models/post_approval_request_apply_request.rb
@@ -792,6 +882,7 @@ files:
 - lib/launchdarkly_api/models/project.rb
 - lib/launchdarkly_api/models/project_listing_rep.rb
 - lib/launchdarkly_api/models/project_post.rb
+- lib/launchdarkly_api/models/project_rep.rb
 - lib/launchdarkly_api/models/project_summary.rb
 - lib/launchdarkly_api/models/projects.rb
 - lib/launchdarkly_api/models/pub_nub_detail_rep.rb
@@ -799,6 +890,7 @@ files:
 - lib/launchdarkly_api/models/rate_limited_error_rep.rb
 - lib/launchdarkly_api/models/recent_trigger_body.rb
 - lib/launchdarkly_api/models/reference_rep.rb
+- lib/launchdarkly_api/models/relative_difference_rep.rb
 - lib/launchdarkly_api/models/relay_auto_config_collection_rep.rb
 - lib/launchdarkly_api/models/relay_auto_config_post.rb
 - lib/launchdarkly_api/models/relay_auto_config_rep.rb
@@ -816,6 +908,7 @@ files:
 - lib/launchdarkly_api/models/review_response.rb
 - lib/launchdarkly_api/models/rollout.rb
 - lib/launchdarkly_api/models/rule.rb
+- lib/launchdarkly_api/models/rule_clause.rb
 - lib/launchdarkly_api/models/schedule_condition_input_rep.rb
 - lib/launchdarkly_api/models/schedule_condition_output_rep.rb
 - lib/launchdarkly_api/models/sdk_list_rep.rb
@@ -833,9 +926,9 @@ files:
 - lib/launchdarkly_api/models/statement.rb
 - lib/launchdarkly_api/models/statement_post.rb
 - lib/launchdarkly_api/models/statement_post_data.rb
-- lib/launchdarkly_api/models/statement_rep.rb
 - lib/launchdarkly_api/models/statistic_collection_rep.rb
 - lib/launchdarkly_api/models/statistic_rep.rb
+- lib/launchdarkly_api/models/statistics_rep.rb
 - lib/launchdarkly_api/models/statistics_root.rb
 - lib/launchdarkly_api/models/status_conflict_error_rep.rb
 - lib/launchdarkly_api/models/subject_data_rep.rb
@@ -848,15 +941,21 @@ files:
 - lib/launchdarkly_api/models/team_custom_roles.rb
 - lib/launchdarkly_api/models/team_imports_rep.rb
 - lib/launchdarkly_api/models/team_maintainers.rb
+- lib/launchdarkly_api/models/team_members.rb
 - lib/launchdarkly_api/models/team_patch_input.rb
 - lib/launchdarkly_api/models/team_post_input.rb
 - lib/launchdarkly_api/models/team_projects.rb
+- lib/launchdarkly_api/models/team_rep_expandable_properties.rb
 - lib/launchdarkly_api/models/teams.rb
 - lib/launchdarkly_api/models/timestamp_rep.rb
 - lib/launchdarkly_api/models/title_rep.rb
 - lib/launchdarkly_api/models/token.rb
 - lib/launchdarkly_api/models/token_data_rep.rb
 - lib/launchdarkly_api/models/tokens.rb
+- lib/launchdarkly_api/models/treatment_input.rb
+- lib/launchdarkly_api/models/treatment_parameter_input.rb
+- lib/launchdarkly_api/models/treatment_rep.rb
+- lib/launchdarkly_api/models/treatment_result_rep.rb
 - lib/launchdarkly_api/models/trigger_post.rb
 - lib/launchdarkly_api/models/trigger_workflow_collection_rep.rb
 - lib/launchdarkly_api/models/trigger_workflow_rep.rb
@@ -872,6 +971,7 @@ files:
 - lib/launchdarkly_api/models/user_segment_rule.rb
 - lib/launchdarkly_api/models/user_segments.rb
 - lib/launchdarkly_api/models/users.rb
+- lib/launchdarkly_api/models/users_rep.rb
 - lib/launchdarkly_api/models/value_put.rb
 - lib/launchdarkly_api/models/variation.rb
 - lib/launchdarkly_api/models/variation_or_rollout_rep.rb
@@ -881,6 +981,8 @@ files:
 - lib/launchdarkly_api/models/webhook_post.rb
 - lib/launchdarkly_api/models/webhooks.rb
 - lib/launchdarkly_api/models/weighted_variation.rb
+- lib/launchdarkly_api/models/workflow_template_metadata.rb
+- lib/launchdarkly_api/models/workflow_template_parameter.rb
 - lib/launchdarkly_api/version.rb
 - spec/api/access_tokens_api_spec.rb
 - spec/api/account_members_api_spec.rb
@@ -896,9 +998,11 @@ files:
 - spec/api/feature_flags_beta_api_spec.rb
 - spec/api/flag_links_beta_api_spec.rb
 - spec/api/flag_triggers_api_spec.rb
+- spec/api/follow_flags_api_spec.rb
 - spec/api/integration_audit_log_subscriptions_api_spec.rb
 - spec/api/integration_delivery_configurations_beta_api_spec.rb
 - spec/api/metrics_api_spec.rb
+- spec/api/o_auth2_clients_beta_api_spec.rb
 - spec/api/other_api_spec.rb
 - spec/api/projects_api_spec.rb
 - spec/api/relay_proxy_configurations_api_spec.rb
@@ -906,7 +1010,7 @@ files:
 - spec/api/segments_api_spec.rb
 - spec/api/segments_beta_api_spec.rb
 - spec/api/tags_api_spec.rb
-- spec/api/teams_beta_api_spec.rb
+- spec/api/teams_api_spec.rb
 - spec/api/user_settings_api_spec.rb
 - spec/api/users_api_spec.rb
 - spec/api/users_beta_api_spec.rb
@@ -933,8 +1037,10 @@ files:
 - spec/models/branch_collection_rep_spec.rb
 - spec/models/branch_rep_spec.rb
 - spec/models/clause_spec.rb
+- spec/models/client_collection_spec.rb
 - spec/models/client_side_availability_post_spec.rb
 - spec/models/client_side_availability_spec.rb
+- spec/models/client_spec.rb
 - spec/models/condition_base_output_rep_spec.rb
 - spec/models/condition_input_rep_spec.rb
 - spec/models/condition_output_rep_spec.rb
@@ -944,6 +1050,7 @@ files:
 - spec/models/copied_from_env_spec.rb
 - spec/models/create_copy_flag_config_approval_request_request_spec.rb
 - spec/models/create_flag_config_approval_request_request_spec.rb
+- spec/models/credible_interval_rep_spec.rb
 - spec/models/custom_property_spec.rb
 - spec/models/custom_role_post_data_spec.rb
 - spec/models/custom_role_post_spec.rb
@@ -964,14 +1071,21 @@ files:
 - spec/models/destinations_spec.rb
 - spec/models/environment_post_spec.rb
 - spec/models/environment_spec.rb
+- spec/models/environments_spec.rb
+- spec/models/evaluation_reason_spec.rb
 - spec/models/execution_output_rep_spec.rb
 - spec/models/experiment_allocation_rep_spec.rb
+- spec/models/experiment_bayesian_results_rep_spec.rb
+- spec/models/experiment_collection_rep_spec.rb
 - spec/models/experiment_enabled_period_rep_spec.rb
 - spec/models/experiment_environment_setting_rep_spec.rb
+- spec/models/experiment_expandable_properties_spec.rb
 - spec/models/experiment_info_rep_spec.rb
 - spec/models/experiment_metadata_rep_spec.rb
-- spec/models/experiment_rep_spec.rb
-- spec/models/experiment_results_rep_spec.rb
+- spec/models/experiment_patch_input_spec.rb
+- spec/models/experiment_post_spec.rb
+- spec/models/experiment_results_spec.rb
+- spec/models/experiment_spec.rb
 - spec/models/experiment_stats_rep_spec.rb
 - spec/models/experiment_time_series_slice_spec.rb
 - spec/models/experiment_time_series_variation_slice_spec.rb
@@ -997,20 +1111,27 @@ files:
 - spec/models/flag_config_approval_requests_response_spec.rb
 - spec/models/flag_copy_config_environment_spec.rb
 - spec/models/flag_copy_config_post_spec.rb
+- spec/models/flag_followers_by_proj_env_get_rep_spec.rb
+- spec/models/flag_followers_get_rep_spec.rb
 - spec/models/flag_global_attributes_rep_spec.rb
+- spec/models/flag_input_spec.rb
 - spec/models/flag_link_collection_rep_spec.rb
 - spec/models/flag_link_member_spec.rb
 - spec/models/flag_link_post_spec.rb
 - spec/models/flag_link_rep_spec.rb
 - spec/models/flag_listing_rep_spec.rb
+- spec/models/flag_rep_spec.rb
 - spec/models/flag_scheduled_changes_input_spec.rb
 - spec/models/flag_status_rep_spec.rb
 - spec/models/flag_summary_spec.rb
 - spec/models/flag_trigger_input_spec.rb
+- spec/models/follow_flag_member_spec.rb
+- spec/models/followers_per_flag_spec.rb
 - spec/models/forbidden_error_rep_spec.rb
 - spec/models/hunk_rep_spec.rb
 - spec/models/import_spec.rb
 - spec/models/initiator_rep_spec.rb
+- spec/models/instruction_user_request_spec.rb
 - spec/models/integration_delivery_configuration_collection_links_spec.rb
 - spec/models/integration_delivery_configuration_collection_spec.rb
 - spec/models/integration_delivery_configuration_links_spec.rb
@@ -1025,7 +1146,11 @@ files:
 - spec/models/integrations_spec.rb
 - spec/models/invalid_request_error_rep_spec.rb
 - spec/models/ip_list_spec.rb
+- spec/models/iteration_expandable_properties_spec.rb
+- spec/models/iteration_input_spec.rb
+- spec/models/iteration_rep_spec.rb
 - spec/models/last_seen_metadata_spec.rb
+- spec/models/legacy_experiment_rep_spec.rb
 - spec/models/link_spec.rb
 - spec/models/member_data_rep_spec.rb
 - spec/models/member_import_item_spec.rb
@@ -1037,20 +1162,27 @@ files:
 - spec/models/members_spec.rb
 - spec/models/method_not_allowed_error_rep_spec.rb
 - spec/models/metric_collection_rep_spec.rb
+- spec/models/metric_input_spec.rb
 - spec/models/metric_listing_rep_spec.rb
 - spec/models/metric_post_spec.rb
 - spec/models/metric_rep_spec.rb
 - spec/models/metric_seen_spec.rb
+- spec/models/metric_v2_rep_spec.rb
 - spec/models/modification_spec.rb
 - spec/models/multi_environment_dependent_flag_spec.rb
 - spec/models/multi_environment_dependent_flags_spec.rb
 - spec/models/new_member_form_spec.rb
 - spec/models/not_found_error_rep_spec.rb
+- spec/models/oauth_client_post_spec.rb
+- spec/models/parameter_default_spec.rb
+- spec/models/parameter_rep_spec.rb
 - spec/models/parent_resource_rep_spec.rb
 - spec/models/patch_failed_error_rep_spec.rb
+- spec/models/patch_flags_request_spec.rb
 - spec/models/patch_operation_spec.rb
 - spec/models/patch_segment_instruction_spec.rb
 - spec/models/patch_segment_request_spec.rb
+- spec/models/patch_users_request_spec.rb
 - spec/models/patch_with_comment_spec.rb
 - spec/models/permission_grant_input_spec.rb
 - spec/models/post_approval_request_apply_request_spec.rb
@@ -1059,6 +1191,7 @@ files:
 - spec/models/prerequisite_spec.rb
 - spec/models/project_listing_rep_spec.rb
 - spec/models/project_post_spec.rb
+- spec/models/project_rep_spec.rb
 - spec/models/project_spec.rb
 - spec/models/project_summary_spec.rb
 - spec/models/projects_spec.rb
@@ -1067,6 +1200,7 @@ files:
 - spec/models/rate_limited_error_rep_spec.rb
 - spec/models/recent_trigger_body_spec.rb
 - spec/models/reference_rep_spec.rb
+- spec/models/relative_difference_rep_spec.rb
 - spec/models/relay_auto_config_collection_rep_spec.rb
 - spec/models/relay_auto_config_post_spec.rb
 - spec/models/relay_auto_config_rep_spec.rb
@@ -1083,6 +1217,7 @@ files:
 - spec/models/review_output_rep_spec.rb
 - spec/models/review_response_spec.rb
 - spec/models/rollout_spec.rb
+- spec/models/rule_clause_spec.rb
 - spec/models/rule_spec.rb
 - spec/models/schedule_condition_input_rep_spec.rb
 - spec/models/schedule_condition_output_rep_spec.rb
@@ -1100,10 +1235,10 @@ files:
 - spec/models/stage_output_rep_spec.rb
 - spec/models/statement_post_data_spec.rb
 - spec/models/statement_post_spec.rb
-- spec/models/statement_rep_spec.rb
 - spec/models/statement_spec.rb
 - spec/models/statistic_collection_rep_spec.rb
 - spec/models/statistic_rep_spec.rb
+- spec/models/statistics_rep_spec.rb
 - spec/models/statistics_root_spec.rb
 - spec/models/status_conflict_error_rep_spec.rb
 - spec/models/subject_data_rep_spec.rb
@@ -1115,9 +1250,11 @@ files:
 - spec/models/team_custom_roles_spec.rb
 - spec/models/team_imports_rep_spec.rb
 - spec/models/team_maintainers_spec.rb
+- spec/models/team_members_spec.rb
 - spec/models/team_patch_input_spec.rb
 - spec/models/team_post_input_spec.rb
 - spec/models/team_projects_spec.rb
+- spec/models/team_rep_expandable_properties_spec.rb
 - spec/models/team_spec.rb
 - spec/models/teams_spec.rb
 - spec/models/timestamp_rep_spec.rb
@@ -1125,6 +1262,10 @@ files:
 - spec/models/token_data_rep_spec.rb
 - spec/models/token_spec.rb
 - spec/models/tokens_spec.rb
+- spec/models/treatment_input_spec.rb
+- spec/models/treatment_parameter_input_spec.rb
+- spec/models/treatment_rep_spec.rb
+- spec/models/treatment_result_rep_spec.rb
 - spec/models/trigger_post_spec.rb
 - spec/models/trigger_workflow_collection_rep_spec.rb
 - spec/models/trigger_workflow_rep_spec.rb
@@ -1139,6 +1280,7 @@ files:
 - spec/models/user_segment_spec.rb
 - spec/models/user_segments_spec.rb
 - spec/models/user_spec.rb
+- spec/models/users_rep_spec.rb
 - spec/models/users_spec.rb
 - spec/models/value_put_spec.rb
 - spec/models/variation_or_rollout_rep_spec.rb
@@ -1149,6 +1291,8 @@ files:
 - spec/models/webhook_spec.rb
 - spec/models/webhooks_spec.rb
 - spec/models/weighted_variation_spec.rb
+- spec/models/workflow_template_metadata_spec.rb
+- spec/models/workflow_template_parameter_spec.rb
 - spec/spec_helper.rb
 homepage: https://openapi-generator.tech
 licenses:
@@ -1185,20 +1329,22 @@ test_files:
 - spec/api/tags_api_spec.rb
 - spec/api/projects_api_spec.rb
 - spec/api/account_members_api_spec.rb
-- spec/api/teams_beta_api_spec.rb
 - spec/api/workflows_beta_api_spec.rb
 - spec/api/feature_flags_beta_api_spec.rb
 - spec/api/audit_log_api_spec.rb
 - spec/api/code_references_api_spec.rb
 - spec/api/webhooks_api_spec.rb
 - spec/api/data_export_destinations_api_spec.rb
+- spec/api/teams_api_spec.rb
 - spec/api/approvals_api_spec.rb
 - spec/api/flag_triggers_api_spec.rb
 - spec/api/environments_api_spec.rb
 - spec/api/access_tokens_api_spec.rb
 - spec/api/experiments_beta_api_spec.rb
+- spec/api/follow_flags_api_spec.rb
 - spec/api/relay_proxy_configurations_api_spec.rb
 - spec/api/segments_api_spec.rb
+- spec/api/o_auth2_clients_beta_api_spec.rb
 - spec/api/account_usage_beta_api_spec.rb
 - spec/api/segments_beta_api_spec.rb
 - spec/api/users_api_spec.rb
@@ -1209,7 +1355,11 @@ test_files:
 - spec/models/webhook_post_spec.rb
 - spec/models/audit_log_entry_listing_rep_collection_spec.rb
 - spec/models/access_spec.rb
+- spec/models/legacy_experiment_rep_spec.rb
+- spec/models/experiment_bayesian_results_rep_spec.rb
+- spec/models/experiment_patch_input_spec.rb
 - spec/models/rollout_spec.rb
+- spec/models/workflow_template_metadata_spec.rb
 - spec/models/integration_status_spec.rb
 - spec/models/execution_output_rep_spec.rb
 - spec/models/review_output_rep_spec.rb
@@ -1228,10 +1378,9 @@ test_files:
 - spec/models/source_flag_spec.rb
 - spec/models/trigger_post_spec.rb
 - spec/models/flag_listing_rep_spec.rb
+- spec/models/users_rep_spec.rb
 - spec/models/custom_role_post_spec.rb
-- spec/models/experiment_results_rep_spec.rb
 - spec/models/resolved_image_spec.rb
-- spec/models/statement_rep_spec.rb
 - spec/models/member_permission_grant_summary_rep_spec.rb
 - spec/models/extinction_collection_rep_spec.rb
 - spec/models/users_spec.rb
@@ -1240,6 +1389,7 @@ test_files:
 - spec/models/member_teams_post_input_spec.rb
 - spec/models/sdk_version_rep_spec.rb
 - spec/models/timestamp_rep_spec.rb
+- spec/models/metric_input_spec.rb
 - spec/models/create_copy_flag_config_approval_request_request_spec.rb
 - spec/models/access_allowed_reason_spec.rb
 - spec/models/access_token_post_spec.rb
@@ -1253,6 +1403,7 @@ test_files:
 - spec/models/team_imports_rep_spec.rb
 - spec/models/default_client_side_availability_post_spec.rb
 - spec/models/flag_summary_spec.rb
+- spec/models/rule_clause_spec.rb
 - spec/models/dependent_flags_by_environment_spec.rb
 - spec/models/member_spec.rb
 - spec/models/integration_delivery_configuration_collection_links_spec.rb
@@ -1260,6 +1411,7 @@ test_files:
 - spec/models/patch_segment_instruction_spec.rb
 - spec/models/reference_rep_spec.rb
 - spec/models/resolved_ui_block_element_spec.rb
+- spec/models/credible_interval_rep_spec.rb
 - spec/models/integration_subscription_status_rep_spec.rb
 - spec/models/repository_rep_spec.rb
 - spec/models/variation_summary_spec.rb
@@ -1269,6 +1421,7 @@ test_files:
 - spec/models/resource_access_spec.rb
 - spec/models/unauthorized_error_rep_spec.rb
 - spec/models/statistic_collection_rep_spec.rb
+- spec/models/patch_users_request_spec.rb
 - spec/models/custom_role_spec.rb
 - spec/models/pub_nub_detail_rep_spec.rb
 - spec/models/last_seen_metadata_spec.rb
@@ -1281,11 +1434,13 @@ test_files:
 - spec/models/experiment_time_series_slice_spec.rb
 - spec/models/parent_resource_rep_spec.rb
 - spec/models/modification_spec.rb
+- spec/models/experiment_post_spec.rb
 - spec/models/stage_input_rep_spec.rb
 - spec/models/segment_body_spec.rb
 - spec/models/rule_spec.rb
 - spec/models/invalid_request_error_rep_spec.rb
 - spec/models/user_segment_rule_spec.rb
+- spec/models/treatment_rep_spec.rb
 - spec/models/trigger_workflow_rep_spec.rb
 - spec/models/experiment_allocation_rep_spec.rb
 - spec/models/subscription_post_spec.rb
@@ -1300,14 +1455,17 @@ test_files:
 - spec/models/new_member_form_spec.rb
 - spec/models/method_not_allowed_error_rep_spec.rb
 - spec/models/feature_flag_config_spec.rb
+- spec/models/iteration_input_spec.rb
 - spec/models/audit_log_entry_listing_rep_spec.rb
 - spec/models/flag_status_rep_spec.rb
+- spec/models/flag_rep_spec.rb
 - spec/models/defaults_spec.rb
 - spec/models/approval_condition_output_rep_spec.rb
 - spec/models/patch_failed_error_rep_spec.rb
 - spec/models/flag_trigger_input_spec.rb
 - spec/models/teams_spec.rb
 - spec/models/client_side_availability_post_spec.rb
+- spec/models/metric_v2_rep_spec.rb
 - spec/models/flag_config_approval_request_response_spec.rb
 - spec/models/condition_input_rep_spec.rb
 - spec/models/put_branch_spec.rb
@@ -1316,6 +1474,7 @@ test_files:
 - spec/models/member_import_item_spec.rb
 - spec/models/source_env_spec.rb
 - spec/models/rate_limited_error_rep_spec.rb
+- spec/models/team_members_spec.rb
 - spec/models/url_post_spec.rb
 - spec/models/tokens_spec.rb
 - spec/models/metric_seen_spec.rb
@@ -1337,7 +1496,9 @@ test_files:
 - spec/models/segment_metadata_spec.rb
 - spec/models/conflict_spec.rb
 - spec/models/schedule_condition_output_rep_spec.rb
+- spec/models/parameter_default_spec.rb
 - spec/models/condition_output_rep_spec.rb
+- spec/models/experiment_results_spec.rb
 - spec/models/custom_roles_spec.rb
 - spec/models/target_resource_rep_spec.rb
 - spec/models/resource_id_response_spec.rb
@@ -1352,10 +1513,11 @@ test_files:
 - spec/models/create_flag_config_approval_request_request_spec.rb
 - spec/models/expiring_user_target_patch_response_spec.rb
 - spec/models/member_team_summary_rep_spec.rb
+- spec/models/evaluation_reason_spec.rb
 - spec/models/feature_flag_status_across_environments_spec.rb
 - spec/models/experiment_time_series_variation_slice_spec.rb
 - spec/models/access_denied_spec.rb
-- spec/models/experiment_rep_spec.rb
+- spec/models/project_rep_spec.rb
 - spec/models/integration_delivery_configuration_response_spec.rb
 - spec/models/link_spec.rb
 - spec/models/variation_or_rollout_rep_spec.rb
@@ -1370,10 +1532,14 @@ test_files:
 - spec/models/schedule_condition_input_rep_spec.rb
 - spec/models/webhook_spec.rb
 - spec/models/metric_listing_rep_spec.rb
+- spec/models/treatment_result_rep_spec.rb
 - spec/models/flag_copy_config_post_spec.rb
 - spec/models/relay_auto_config_post_spec.rb
+- spec/models/parameter_rep_spec.rb
 - spec/models/flag_link_collection_rep_spec.rb
 - spec/models/trigger_workflow_collection_rep_spec.rb
+- spec/models/client_spec.rb
+- spec/models/client_collection_spec.rb
 - spec/models/user_attribute_names_rep_spec.rb
 - spec/models/project_summary_spec.rb
 - spec/models/confidence_interval_rep_spec.rb
@@ -1382,11 +1548,14 @@ test_files:
 - spec/models/webhooks_spec.rb
 - spec/models/environment_post_spec.rb
 - spec/models/project_listing_rep_spec.rb
+- spec/models/treatment_parameter_input_spec.rb
 - spec/models/user_record_spec.rb
 - spec/models/action_input_rep_spec.rb
 - spec/models/user_flag_settings_spec.rb
+- spec/models/workflow_template_parameter_spec.rb
 - spec/models/dependent_flag_environment_spec.rb
 - spec/models/feature_flag_statuses_spec.rb
+- spec/models/experiment_spec.rb
 - spec/models/approval_condition_input_rep_spec.rb
 - spec/models/repository_collection_rep_spec.rb
 - spec/models/clause_spec.rb
@@ -1397,20 +1566,31 @@ test_files:
 - spec/models/token_data_rep_spec.rb
 - spec/models/expiring_user_target_get_response_spec.rb
 - spec/models/feature_flag_status_spec.rb
+- spec/models/team_rep_expandable_properties_spec.rb
 - spec/models/flag_global_attributes_rep_spec.rb
 - spec/models/patch_operation_spec.rb
 - spec/models/subject_data_rep_spec.rb
+- spec/models/experiment_collection_rep_spec.rb
+- spec/models/followers_per_flag_spec.rb
+- spec/models/instruction_user_request_spec.rb
 - spec/models/segment_user_state_spec.rb
 - spec/models/access_denied_reason_spec.rb
+- spec/models/experiment_expandable_properties_spec.rb
 - spec/models/import_spec.rb
+- spec/models/iteration_rep_spec.rb
+- spec/models/flag_followers_by_proj_env_get_rep_spec.rb
 - spec/models/integration_metadata_spec.rb
+- spec/models/statistics_rep_spec.rb
 - spec/models/hunk_rep_spec.rb
 - spec/models/big_segment_target_spec.rb
 - spec/models/post_approval_request_review_request_spec.rb
 - spec/models/sdk_list_rep_spec.rb
 - spec/models/custom_workflows_listing_output_rep_spec.rb
 - spec/models/access_allowed_rep_spec.rb
+- spec/models/follow_flag_member_spec.rb
 - spec/models/variation_spec.rb
+- spec/models/environments_spec.rb
+- spec/models/flag_input_spec.rb
 - spec/models/relay_auto_config_collection_rep_spec.rb
 - spec/models/permission_grant_input_spec.rb
 - spec/models/integrations_spec.rb
@@ -1422,7 +1602,9 @@ test_files:
 - spec/models/series_list_rep_spec.rb
 - spec/models/weighted_variation_spec.rb
 - spec/models/team_custom_roles_spec.rb
+- spec/models/oauth_client_post_spec.rb
 - spec/models/post_flag_scheduled_changes_input_spec.rb
+- spec/models/treatment_input_spec.rb
 - spec/models/multi_environment_dependent_flag_spec.rb
 - spec/models/statement_post_data_spec.rb
 - spec/models/statement_spec.rb
@@ -1430,14 +1612,18 @@ test_files:
 - spec/models/title_rep_spec.rb
 - spec/models/segment_user_list_spec.rb
 - spec/models/flag_link_post_spec.rb
+- spec/models/iteration_expandable_properties_spec.rb
 - spec/models/member_summary_spec.rb
 - spec/models/custom_workflow_output_rep_spec.rb
 - spec/models/repository_post_spec.rb
 - spec/models/environment_spec.rb
+- spec/models/patch_flags_request_spec.rb
 - spec/models/branch_collection_rep_spec.rb
 - spec/models/tag_collection_spec.rb
+- spec/models/flag_followers_get_rep_spec.rb
 - spec/models/branch_rep_spec.rb
 - spec/models/feature_flag_scheduled_changes_spec.rb
+- spec/models/relative_difference_rep_spec.rb
 - spec/models/recent_trigger_body_spec.rb
 - spec/models/approval_settings_spec.rb
 - spec/models/resolved_ui_blocks_spec.rb