launchdarkly_api 6.0.0 → 6.0.1

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: launchdarkly_api
 version: !ruby/object:Gem::Version
-  version: 6.0.0
+  version: 6.0.1
 platform: ruby
 authors:
-- LaunchDarkly
+- OpenAPI-Generator
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-09-02 00:00:00.000000000 Z
+date: 2021-10-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: typhoeus
@@ -50,8 +50,8 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 3.6.0
-description: '# Authentication  All REST API resources are authenticated with either
-  [personal or service access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens),
+description: '# Overview  ## Authentication  All REST API resources are authenticated
+  with either [personal or service access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens),
   or session cookies. Other authentication mechanisms are not supported. You can manage
   personal access tokens on your [Account settings](https://app.launchdarkly.com/settings/tokens)
   page.  LaunchDarkly also has SDK keys, mobile keys, and client-side IDs that are
@@ -72,17 +72,17 @@ description: '# Authentication  All REST API resources are authenticated with ei
   environment           | Mobile SDKs                                        | | Client-side
   ID                                                                                  |
   Single environment, only flags marked available to client-side                                        |
-  Client-side JavaScript                             |  > ### Keep your access tokens
+  Client-side JavaScript                             |  > #### Keep your access tokens
   and SDK keys private > > Access tokens should _never_ be exposed in untrusted contexts.
   Never put an access token in client-side JavaScript, or embed it in a mobile application.
   LaunchDarkly has special mobile keys that you can embed in mobile apps. If you accidentally
   expose an access token or SDK key, you can reset it from your [Account Settings](https://app.launchdarkly.com/settings#/tokens)
   page. > > The client-side ID is safe to embed in untrusted contexts. It''s designed
-  for use in client-side JavaScript.  ## Via request header  The preferred way to
+  for use in client-side JavaScript.  ### Via request header  The preferred way to
   authenticate with the API is by adding an `Authorization` header containing your
   access token to your requests. The value of the `Authorization` header must be your
   access token.  Manage personal access tokens from the [Account Settings](https://app.launchdarkly.com/settings/tokens)
-  page.  ## Via session cookie  For testing purposes, you can make API calls directly
+  page.  ### Via session cookie  For testing purposes, you can make API calls directly
   from your web browser. If you''re logged in to the application, the API will use
   your existing session to authenticate calls.  If you have a [role](https://docs.launchdarkly.com/home/team/built-in-roles)
   other than Admin, or have a [custom role](https://docs.launchdarkly.com/home/team/custom-roles)
@@ -97,19 +97,19 @@ description: '# Authentication  All REST API resources are authenticated with ei
   *` Chrome extension changes the Origin header to `http://evil.com` and causes the
   app to fail. > > To prevent this error, do not modify your Origin header. > > LaunchDarkly
   does not require origin matching when authenticating with an access token, so this
-  issue does not affect normal API usage.  # Representations  All resources expect
+  issue does not affect normal API usage.  ## Representations  All resources expect
   and return JSON response bodies. Error responses will also send a JSON body. Read
   [Errors](#section/Errors) for a more detailed description of the error format used
   by the API.  In practice this means that you always get a response with a `Content-Type`
   header set to `application/json`.  In addition, request bodies for `PUT`, `POST`,
   `REPORT` and `PATCH` requests must be encoded as JSON with a `Content-Type` header
-  set to `application/json`.  ## Summary and detailed representations  When you fetch
+  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
+  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
   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. -
@@ -124,12 +124,12 @@ description: '# Authentication  All REST API resources are authenticated with ei
   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.  #
+  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](http://tools.ietf.org/html/rfc6902) format. Some resources also
   support the [JSON Merge Patch](https://tools.ietf.org/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
+  appear in outgoing webhooks, the audit log, and other integrations.  ### Updates
   via JSON Patch  [JSON Patch](http://tools.ietf.org/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":
@@ -142,20 +142,20 @@ description: '# Authentication  All REST API resources are authenticated with ei
   "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
+  underscore.  ### Updates via JSON Merge Patch  The API also supports the [JSON Merge
   Patch](https://tools.ietf.org/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":
+  } ```  ### 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
+  "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
@@ -193,14 +193,14 @@ description: '# Authentication  All REST API resources are authenticated with ei
   ["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)
-  > - [Update expiring user target for flags](/tag/User-Settings#operation/patchExpiringFlagsForUser)
-  > - [Update expiring user targets on segment](/tag/Segments#operation/patchExpiringUserTargetsOnSegment)  #
+  > - [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":
   "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  |
+  to debug a problem with a specific API call.  ### HTTP Status - Error Response Codes  |
   Code | Definition        | Desc.                                                                                       |
   Possible Solution                                                | | ---- | -----------------
   | -------------------------------------------------------------------------------------------
@@ -214,7 +214,7 @@ description: '# Authentication  All REST API resources are authenticated with ei
   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).                                               |
-  Wait and try again later.                                        |  # CORS  The
+  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
   as an explicitly allowed origin. Otherwise, a wildcard is returned: `Access-Control-Allow-Origin:
@@ -226,22 +226,22 @@ description: '# Authentication  All REST API resources are authenticated with ei
   calls, using either [token or session-based authentication](#section/Authentication).
   If you’re using session auth, you should set the `withCredentials` property for
   your `xhr` request to `true`. You should never expose your access tokens to untrusted
-  users.  # Rate limiting  We use several rate limiting strategies to ensure the availability
-  of our APIs. Rate-limited calls to our APIs will return a `429` status code. Calls
-  to our APIs will include headers indicating the current rate limit status. The specific
-  headers returned depend on the API route being called. The limits differ based on
-  the route, authentication mechanism, and other factors. Routes that are not rate
-  limited may not contain any of the headers described below.  > ### Rate 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                                                                      |
+  users.  ## Rate limiting  We use several rate limiting strategies to ensure the
+  availability of our APIs. Rate-limited calls to our APIs will return a `429` status
+  code. Calls to our APIs will include headers indicating the current rate limit status.
+  The specific headers returned depend on the API route being called. The limits differ
+  based on the route, authentication mechanism, and other factors. Routes that are
+  not rate limited may not contain any of the headers described below.  > ### Rate
+  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                                                                      |
   | ------------------------------ | --------------------------------------------------------------------------------
   | | `X-Ratelimit-Global-Remaining` | The maximum number of requests the account
   is permitted to make per ten seconds. | | `X-Ratelimit-Reset`            | The time
@@ -249,11 +249,11 @@ description: '# Authentication  All REST API resources are authenticated with ei
   not publicly document the specific number of calls that can be made globally. This
   limit may change, and we encourage clients to program against the specification,
   relying on the two headers defined above, rather than hardcoding to the current
-  limit.  ## Route-level rate limits  Some authenticated routes have custom rate limits.
-  These also reset every ten seconds. Any access tokens hitting the same route share
-  this limit, so exceeding the limit with one access token may impact other tokens.
-  Calls that are subject to route-level rate limits will return the headers below:  |
-  Header name                   | Description                                                                                           |
+  limit.  ### Route-level rate limits  Some authenticated routes have custom rate
+  limits. These also reset every ten seconds. Any access tokens hitting the same route
+  share this limit, so exceeding the limit with one access token may impact other
+  tokens. Calls that are subject to route-level rate limits will return the headers
+  below:  | Header name                   | Description                                                                                           |
   | ----------------------------- | -----------------------------------------------------------------------------------------------------
   | | `X-Ratelimit-Route-Remaining` | The maximum number of requests to the current
   route the account is permitted to make per ten seconds. | | `X-Ratelimit-Reset`           |
@@ -264,25 +264,25 @@ description: '# Authentication  All REST API resources are authenticated with ei
   the specific number of calls that can be made to each endpoint per ten seconds.
   These limits may change, and we encourage clients to program against the specification,
   relying on the two headers defined above, rather than hardcoding to the current
-  limits.  ## IP-based rate limiting  We also employ IP-based rate limiting on some
+  limits.  ### IP-based rate limiting  We also employ IP-based rate limiting on some
   API routes. If you hit an IP-based rate limit, your API response will include a
   `Retry-After` header indicating how long to wait before re-trying the call. Clients
   must wait at least `Retry-After` seconds before making additional calls to our API,
   and should employ jitter and backoff strategies to avoid triggering rate limits
-  again.  # OpenAPI (Swagger)  We have a [complete OpenAPI (Swagger) specification](https://app.launchdarkly.com/api/v2/openapi.json)
+  again.  ## OpenAPI (Swagger)  We have a [complete OpenAPI (Swagger) specification](https://app.launchdarkly.com/api/v2/openapi.json)
   for our API.  You can use this specification to generate client libraries to interact
   with our REST API in your language of choice.  This specification is supported by
   several API-based tools such as Postman and Insomnia. In many cases, you can directly
-  import our specification to ease use in navigating the APIs in the tooling.  # Client
-  libraries  We auto-generate multiple client libraries based on our OpenAPI specification.
-  To learn more, visit [GitHub](https://github.com/search?q=topic%3Alaunchdarkly-api+org%3Alaunchdarkly&type=Repositories).  #
+  import our specification to ease use in navigating the APIs in the tooling.  ##
+  Client libraries  We auto-generate multiple client libraries based on our OpenAPI
+  specification. To learn more, visit [GitHub](https://github.com/search?q=topic%3Alaunchdarkly-api+org%3Alaunchdarkly&type=Repositories).  ##
   Method Overriding  Some firewalls and HTTP clients restrict the use of verbs other
   than `GET` and `POST`. In those environments, our API endpoints that use `PUT`,
   `PATCH`, and `DELETE` verbs will be inaccessible.  To avoid this issue, our API
   supports the `X-HTTP-Method-Override` header, allowing clients to "tunnel" `PUT`,
   `PATCH`, and `DELETE` requests via a `POST` request.  For example, if you wish to
   call one of our `PATCH` resources via a `POST` request, you can include `X-HTTP-Method-Override:PATCH`
-  as a header.  # Beta resources  We sometimes release new API resources in **beta**
+  as a header.  ## Beta resources  We sometimes release new API resources in **beta**
   status before we release them with general availability.  Resources that are in
   beta are still undergoing testing and development. They may change without notice,
   including becoming backwards incompatible.  We try to promote resources into general
@@ -291,31 +291,32 @@ description: '# Authentication  All REST API resources are authenticated with ei
   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 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 unexpected behavior
-  if you don''t prepare for them accordingly.  Updates to our REST API include support
-  for the latest features in LaunchDarkly. We also release a new version of our REST
-  API every time we make a breaking change. We provide simultaneous 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: 20191212 ```  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 the example above the version `20191212`
-  corresponds to December 12, 2019.  ## 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 released have their version set to `20160426` (the
-  version of the API that existed before versioning) so that they continue working
-  the same way they did before versioning.  If you would like to upgrade your integration
-  to use a new API version, you can explicitly 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. '
+  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
+  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
+  unexpected behavior if you don''t prepare for them accordingly.  Updates to our
+  REST API include support for the latest features in LaunchDarkly. We also release
+  a new version of our REST API every time we make a breaking change. We provide simultaneous
+  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: 20191212 ```  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 the example above
+  the version `20191212` corresponds to December 12, 2019.  ### 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 released have their version
+  set to `20160426` (the version of the API that existed before versioning) so that
+  they continue working the same way they did before versioning.  If you would like
+  to upgrade your integration to use a new API version, you can explicitly 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. '
 email:
 - support@launchdarkly.com
 executables: []
@@ -358,6 +359,8 @@ files:
 - docs/CustomRolePostData.md
 - docs/CustomRoles.md
 - docs/CustomRolesApi.md
+- docs/CustomWorkflowMeta.md
+- docs/CustomWorkflowStageMeta.md
 - docs/DataExportDestinationsApi.md
 - docs/DefaultClientSideAvailabilityPost.md
 - docs/Defaults.md
@@ -439,6 +442,8 @@ files:
 - docs/PatchSegmentInstruction.md
 - docs/PatchSegmentRequest.md
 - docs/PatchWithComment.md
+- docs/PermissionGrantInput.md
+- docs/PermissionGrantRep.md
 - docs/PostApprovalRequestApplyRequest.md
 - docs/PostApprovalRequestReviewRequest.md
 - docs/PostFlagScheduledChangesInput.md
@@ -483,6 +488,11 @@ files:
 - docs/SubjectDataRep.md
 - docs/Target.md
 - docs/TargetResourceRep.md
+- docs/TeamCollectionRep.md
+- docs/TeamPatchInput.md
+- docs/TeamPostInput.md
+- docs/TeamRep.md
+- docs/TeamsBetaApi.md
 - docs/TitleRep.md
 - docs/Token.md
 - docs/TokenDataRep.md
@@ -532,6 +542,7 @@ files:
 - lib/launchdarkly_api/api/relay_proxy_configurations_api.rb
 - lib/launchdarkly_api/api/scheduled_changes_api.rb
 - lib/launchdarkly_api/api/segments_api.rb
+- lib/launchdarkly_api/api/teams_beta_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
@@ -564,6 +575,8 @@ files:
 - lib/launchdarkly_api/models/custom_role_post.rb
 - lib/launchdarkly_api/models/custom_role_post_data.rb
 - lib/launchdarkly_api/models/custom_roles.rb
+- lib/launchdarkly_api/models/custom_workflow_meta.rb
+- lib/launchdarkly_api/models/custom_workflow_stage_meta.rb
 - lib/launchdarkly_api/models/default_client_side_availability_post.rb
 - lib/launchdarkly_api/models/defaults.rb
 - lib/launchdarkly_api/models/dependent_flag.rb
@@ -638,6 +651,8 @@ files:
 - lib/launchdarkly_api/models/patch_segment_instruction.rb
 - lib/launchdarkly_api/models/patch_segment_request.rb
 - lib/launchdarkly_api/models/patch_with_comment.rb
+- lib/launchdarkly_api/models/permission_grant_input.rb
+- lib/launchdarkly_api/models/permission_grant_rep.rb
 - lib/launchdarkly_api/models/post_approval_request_apply_request.rb
 - lib/launchdarkly_api/models/post_approval_request_review_request.rb
 - lib/launchdarkly_api/models/post_flag_scheduled_changes_input.rb
@@ -678,6 +693,10 @@ files:
 - lib/launchdarkly_api/models/subject_data_rep.rb
 - lib/launchdarkly_api/models/target.rb
 - lib/launchdarkly_api/models/target_resource_rep.rb
+- lib/launchdarkly_api/models/team_collection_rep.rb
+- lib/launchdarkly_api/models/team_patch_input.rb
+- lib/launchdarkly_api/models/team_post_input.rb
+- lib/launchdarkly_api/models/team_rep.rb
 - lib/launchdarkly_api/models/title_rep.rb
 - lib/launchdarkly_api/models/token.rb
 - lib/launchdarkly_api/models/token_data_rep.rb
@@ -721,6 +740,7 @@ files:
 - spec/api/relay_proxy_configurations_api_spec.rb
 - spec/api/scheduled_changes_api_spec.rb
 - spec/api/segments_api_spec.rb
+- spec/api/teams_beta_api_spec.rb
 - spec/api/user_settings_api_spec.rb
 - spec/api/users_api_spec.rb
 - spec/api/users_beta_api_spec.rb
@@ -752,6 +772,8 @@ files:
 - spec/models/custom_role_post_spec.rb
 - spec/models/custom_role_spec.rb
 - spec/models/custom_roles_spec.rb
+- spec/models/custom_workflow_meta_spec.rb
+- spec/models/custom_workflow_stage_meta_spec.rb
 - spec/models/default_client_side_availability_post_spec.rb
 - spec/models/defaults_spec.rb
 - spec/models/dependent_flag_environment_spec.rb
@@ -826,6 +848,8 @@ files:
 - spec/models/patch_segment_instruction_spec.rb
 - spec/models/patch_segment_request_spec.rb
 - spec/models/patch_with_comment_spec.rb
+- spec/models/permission_grant_input_spec.rb
+- spec/models/permission_grant_rep_spec.rb
 - spec/models/post_approval_request_apply_request_spec.rb
 - spec/models/post_approval_request_review_request_spec.rb
 - spec/models/post_flag_scheduled_changes_input_spec.rb
@@ -866,6 +890,10 @@ files:
 - spec/models/subject_data_rep_spec.rb
 - spec/models/target_resource_rep_spec.rb
 - spec/models/target_spec.rb
+- spec/models/team_collection_rep_spec.rb
+- spec/models/team_patch_input_spec.rb
+- spec/models/team_post_input_spec.rb
+- spec/models/team_rep_spec.rb
 - spec/models/title_rep_spec.rb
 - spec/models/token_data_rep_spec.rb
 - spec/models/token_spec.rb
@@ -891,7 +919,7 @@ files:
 - spec/models/webhooks_spec.rb
 - spec/models/weighted_variation_spec.rb
 - spec/spec_helper.rb
-homepage: https://github.com/launchdarkly/api-client-ruby
+homepage: https://openapi-generator.tech
 licenses:
 - Unlicense
 metadata: {}
@@ -910,197 +938,205 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.5.2.3
+rubygems_version: 3.1.2
 signing_key: 
 specification_version: 4
 summary: LaunchDarkly REST API Ruby Gem
 test_files:
-- spec/api/feature_flags_beta_api_spec.rb
-- spec/api/metrics_api_spec.rb
-- spec/api/scheduled_changes_api_spec.rb
 - spec/api/custom_roles_api_spec.rb
-- spec/api/approvals_api_spec.rb
-- spec/api/user_settings_api_spec.rb
 - spec/api/users_beta_api_spec.rb
-- spec/api/webhooks_api_spec.rb
-- spec/api/environments_api_spec.rb
+- spec/api/scheduled_changes_api_spec.rb
+- spec/api/feature_flags_api_spec.rb
+- spec/api/metrics_api_spec.rb
+- spec/api/user_settings_api_spec.rb
 - spec/api/projects_api_spec.rb
-- spec/api/relay_proxy_configurations_api_spec.rb
 - spec/api/account_members_api_spec.rb
-- spec/api/data_export_destinations_api_spec.rb
-- spec/api/other_api_spec.rb
+- spec/api/teams_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/users_api_spec.rb
-- spec/api/feature_flags_api_spec.rb
-- spec/api/experiments_beta_api_spec.rb
+- spec/api/webhooks_api_spec.rb
+- spec/api/data_export_destinations_api_spec.rb
+- spec/api/approvals_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/relay_proxy_configurations_api_spec.rb
 - spec/api/segments_api_spec.rb
 - spec/api/account_usage_beta_api_spec.rb
-- spec/api/audit_log_api_spec.rb
+- spec/api/users_api_spec.rb
+- spec/api/other_api_spec.rb
 - spec/api_client_spec.rb
 - spec/configuration_spec.rb
-- spec/models/branch_rep_spec.rb
-- spec/models/modification_spec.rb
-- spec/models/dependent_flag_spec.rb
-- spec/models/feature_flag_status_across_environments_spec.rb
-- spec/models/webhook_spec.rb
-- spec/models/experiment_enabled_period_rep_spec.rb
-- spec/models/access_token_post_spec.rb
-- spec/models/post_flag_scheduled_changes_input_spec.rb
-- spec/models/experiment_environment_setting_rep_spec.rb
-- spec/models/custom_property_spec.rb
-- spec/models/client_side_availability_post_spec.rb
-- spec/models/feature_flag_config_spec.rb
-- spec/models/user_segment_spec.rb
-- spec/models/client_side_availability_spec.rb
-- spec/models/conflict_spec.rb
-- spec/models/statement_rep_spec.rb
-- spec/models/variation_summary_spec.rb
-- spec/models/relay_auto_config_rep_spec.rb
-- spec/models/member_data_rep_spec.rb
-- spec/models/resource_id_response_spec.rb
-- spec/models/big_segment_target_spec.rb
-- spec/models/feature_flags_spec.rb
+- spec/models/webhook_post_spec.rb
 - spec/models/audit_log_entry_listing_rep_collection_spec.rb
-- spec/models/experiment_totals_rep_spec.rb
-- spec/models/project_spec.rb
-- spec/models/feature_flag_statuses_spec.rb
-- spec/models/resource_access_spec.rb
-- spec/models/feature_flag_scheduled_changes_spec.rb
-- spec/models/expiring_user_target_get_response_spec.rb
-- spec/models/multi_environment_dependent_flags_spec.rb
-- spec/models/prerequisite_spec.rb
-- spec/models/post_approval_request_apply_request_spec.rb
-- spec/models/integration_metadata_spec.rb
-- spec/models/project_listing_rep_spec.rb
-- spec/models/tokens_spec.rb
-- spec/models/subject_data_rep_spec.rb
 - spec/models/rollout_spec.rb
-- spec/models/environment_spec.rb
-- spec/models/series_list_rep_spec.rb
-- spec/models/flag_scheduled_changes_input_spec.rb
-- spec/models/user_flag_settings_spec.rb
+- spec/models/integration_status_spec.rb
+- spec/models/members_spec.rb
+- spec/models/custom_workflow_stage_meta_spec.rb
+- spec/models/user_flag_setting_spec.rb
+- spec/models/project_post_spec.rb
+- spec/models/user_segments_spec.rb
+- spec/models/team_patch_input_spec.rb
 - spec/models/member_summary_rep_spec.rb
-- spec/models/repository_post_spec.rb
-- spec/models/experiment_time_series_slice_spec.rb
-- spec/models/token_spec.rb
+- spec/models/projects_spec.rb
+- spec/models/metric_collection_rep_spec.rb
+- spec/models/multi_environment_dependent_flags_spec.rb
+- spec/models/source_flag_spec.rb
+- spec/models/flag_listing_rep_spec.rb
+- spec/models/custom_role_post_spec.rb
+- spec/models/experiment_results_rep_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
+- spec/models/expiring_user_target_error_spec.rb
+- spec/models/ip_list_spec.rb
+- spec/models/sdk_version_rep_spec.rb
+- spec/models/create_copy_flag_config_approval_request_request_spec.rb
+- spec/models/access_token_post_spec.rb
+- spec/models/destinations_spec.rb
+- spec/models/user_segment_spec.rb
+- spec/models/project_spec.rb
+- spec/models/authorized_app_data_rep_spec.rb
+- spec/models/feature_flag_scheduled_change_spec.rb
+- spec/models/review_response_spec.rb
+- spec/models/default_client_side_availability_post_spec.rb
+- spec/models/flag_summary_spec.rb
+- spec/models/team_rep_spec.rb
+- spec/models/permission_grant_rep_spec.rb
+- spec/models/dependent_flags_by_environment_spec.rb
+- spec/models/member_spec.rb
+- spec/models/experiment_stats_rep_spec.rb
 - spec/models/patch_segment_instruction_spec.rb
+- spec/models/reference_rep_spec.rb
 - spec/models/inline_object_spec.rb
-- spec/models/repository_rep_spec.rb
-- spec/models/environment_post_spec.rb
-- spec/models/expiring_user_target_item_spec.rb
-- spec/models/dependent_flag_environment_spec.rb
-- spec/models/default_client_side_availability_post_spec.rb
 - spec/models/access_denied_reason_rep_spec.rb
-- spec/models/custom_role_post_data_spec.rb
-- spec/models/relay_auto_config_collection_rep_spec.rb
-- spec/models/experiment_time_series_variation_slice_spec.rb
-- spec/models/approval_settings_spec.rb
-- spec/models/project_post_spec.rb
-- spec/models/segment_metadata_spec.rb
-- spec/models/variate_spec.rb
-- spec/models/experiment_metadata_rep_spec.rb
-- spec/models/experiment_results_rep_spec.rb
-- spec/models/sdk_list_rep_spec.rb
-- spec/models/segment_user_state_spec.rb
+- spec/models/repository_rep_spec.rb
+- spec/models/variation_summary_spec.rb
+- spec/models/audit_log_entry_rep_spec.rb
+- spec/models/experiment_environment_setting_rep_spec.rb
+- spec/models/resource_access_spec.rb
+- spec/models/statistic_collection_rep_spec.rb
+- spec/models/custom_role_spec.rb
+- spec/models/pub_nub_detail_rep_spec.rb
+- spec/models/last_seen_metadata_spec.rb
+- spec/models/destination_spec.rb
+- spec/models/flag_scheduled_changes_input_spec.rb
+- spec/models/experiment_totals_rep_spec.rb
+- spec/models/member_data_rep_spec.rb
+- spec/models/experiment_time_series_slice_spec.rb
+- spec/models/parent_resource_rep_spec.rb
+- spec/models/modification_spec.rb
+- spec/models/segment_body_spec.rb
 - spec/models/rule_spec.rb
+- spec/models/user_segment_rule_spec.rb
 - spec/models/experiment_allocation_rep_spec.rb
-- spec/models/last_seen_metadata_spec.rb
-- spec/models/authorized_app_data_rep_spec.rb
-- spec/models/create_copy_flag_config_approval_request_request_spec.rb
-- spec/models/statement_post_spec.rb
-- spec/models/extinction_spec.rb
-- spec/models/patch_operation_spec.rb
-- spec/models/custom_roles_spec.rb
-- spec/models/hunk_rep_spec.rb
 - spec/models/feature_flag_spec.rb
-- spec/models/user_attribute_names_rep_spec.rb
-- spec/models/pub_nub_detail_rep_spec.rb
-- spec/models/destinations_spec.rb
-- spec/models/extinction_collection_rep_spec.rb
+- spec/models/sdk_version_list_rep_spec.rb
 - spec/models/flag_config_approval_requests_response_spec.rb
-- spec/models/experiment_rep_spec.rb
-- spec/models/defaults_spec.rb
-- spec/models/feature_flag_status_spec.rb
-- spec/models/post_approval_request_review_request_spec.rb
-- spec/models/experiment_info_rep_spec.rb
-- spec/models/clause_spec.rb
-- spec/models/custom_role_spec.rb
-- spec/models/members_spec.rb
-- spec/models/metric_collection_rep_spec.rb
-- spec/models/title_rep_spec.rb
+- spec/models/metric_post_spec.rb
+- spec/models/new_member_form_spec.rb
 - spec/models/access_rep_spec.rb
-- spec/models/member_permission_grant_summary_rep_spec.rb
-- spec/models/metric_listing_rep_spec.rb
-- spec/models/parent_resource_rep_spec.rb
-- spec/models/integration_status_spec.rb
-- spec/models/confidence_interval_rep_spec.rb
-- spec/models/target_spec.rb
-- spec/models/statistic_rep_spec.rb
-- spec/models/source_flag_spec.rb
-- spec/models/flag_copy_config_post_spec.rb
+- spec/models/feature_flag_config_spec.rb
+- spec/models/audit_log_entry_listing_rep_spec.rb
+- spec/models/flag_status_rep_spec.rb
+- spec/models/defaults_spec.rb
+- spec/models/client_side_availability_post_spec.rb
+- spec/models/flag_config_approval_request_response_spec.rb
+- spec/models/feature_flags_spec.rb
+- spec/models/prerequisite_spec.rb
 - spec/models/url_post_spec.rb
+- spec/models/tokens_spec.rb
+- spec/models/expiring_user_target_item_spec.rb
+- spec/models/experiment_info_rep_spec.rb
+- spec/models/dependent_flag_spec.rb
+- spec/models/metric_rep_spec.rb
+- spec/models/versions_rep_spec.rb
+- spec/models/experiment_metadata_rep_spec.rb
+- spec/models/experiment_enabled_period_rep_spec.rb
 - spec/models/copied_from_env_spec.rb
-- spec/models/audit_log_entry_rep_spec.rb
-- spec/models/flag_summary_spec.rb
-- spec/models/projects_spec.rb
-- spec/models/reference_rep_spec.rb
-- spec/models/sdk_version_rep_spec.rb
+- spec/models/statistic_rep_spec.rb
+- spec/models/segment_metadata_spec.rb
+- spec/models/conflict_spec.rb
+- spec/models/inline_object1_spec.rb
+- spec/models/custom_roles_spec.rb
+- spec/models/target_resource_rep_spec.rb
+- spec/models/resource_id_response_spec.rb
+- spec/models/extinction_rep_spec.rb
+- spec/models/extinction_spec.rb
+- spec/models/user_spec.rb
+- spec/models/team_post_input_spec.rb
+- spec/models/token_spec.rb
+- spec/models/custom_workflow_meta_spec.rb
+- spec/models/post_approval_request_apply_request_spec.rb
+- spec/models/target_spec.rb
+- spec/models/feature_flag_body_spec.rb
+- spec/models/team_collection_rep_spec.rb
+- spec/models/create_flag_config_approval_request_request_spec.rb
 - spec/models/expiring_user_target_patch_response_spec.rb
-- spec/models/webhook_post_spec.rb
 - spec/models/member_team_summary_rep_spec.rb
-- spec/models/user_record_spec.rb
-- spec/models/branch_collection_rep_spec.rb
-- spec/models/value_put_spec.rb
+- spec/models/feature_flag_status_across_environments_spec.rb
+- spec/models/experiment_time_series_variation_slice_spec.rb
+- spec/models/experiment_rep_spec.rb
+- spec/models/link_spec.rb
+- spec/models/variation_or_rollout_rep_spec.rb
+- spec/models/patch_with_comment_spec.rb
+- spec/models/custom_role_post_data_spec.rb
+- spec/models/patch_segment_request_spec.rb
+- spec/models/relay_auto_config_rep_spec.rb
+- spec/models/webhook_spec.rb
+- spec/models/metric_listing_rep_spec.rb
+- spec/models/flag_copy_config_post_spec.rb
+- spec/models/relay_auto_config_post_spec.rb
+- spec/models/user_attribute_names_rep_spec.rb
+- spec/models/confidence_interval_rep_spec.rb
 - spec/models/flag_copy_config_environment_spec.rb
-- spec/models/statistics_root_spec.rb
-- spec/models/flag_status_rep_spec.rb
-- spec/models/access_denied_rep_spec.rb
-- spec/models/create_flag_config_approval_request_request_spec.rb
-- spec/models/extinction_rep_spec.rb
-- spec/models/metric_post_spec.rb
-- spec/models/segment_user_list_spec.rb
-- spec/models/flag_config_approval_request_response_spec.rb
-- spec/models/new_member_form_spec.rb
-- spec/models/target_resource_rep_spec.rb
-- spec/models/weighted_variation_spec.rb
-- spec/models/users_spec.rb
-- spec/models/destination_spec.rb
-- spec/models/user_flag_setting_spec.rb
-- spec/models/inline_response200_spec.rb
-- spec/models/flag_listing_rep_spec.rb
-- spec/models/feature_flag_scheduled_change_spec.rb
-- spec/models/metric_rep_spec.rb
+- spec/models/value_put_spec.rb
 - spec/models/webhooks_spec.rb
-- spec/models/statement_post_data_spec.rb
+- spec/models/environment_post_spec.rb
+- spec/models/project_listing_rep_spec.rb
+- spec/models/user_record_spec.rb
+- spec/models/inline_response200_spec.rb
+- spec/models/user_flag_settings_spec.rb
+- spec/models/dependent_flag_environment_spec.rb
+- spec/models/feature_flag_statuses_spec.rb
+- spec/models/access_denied_rep_spec.rb
 - spec/models/repository_collection_rep_spec.rb
-- spec/models/user_spec.rb
-- spec/models/relay_auto_config_post_spec.rb
-- spec/models/expiring_user_target_error_spec.rb
-- spec/models/user_segments_spec.rb
-- spec/models/destination_post_spec.rb
-- spec/models/statement_spec.rb
-- spec/models/review_response_spec.rb
-- spec/models/segment_body_spec.rb
-- spec/models/user_segment_rule_spec.rb
-- spec/models/dependent_flags_by_environment_spec.rb
-- spec/models/custom_role_post_spec.rb
-- spec/models/patch_segment_request_spec.rb
-- spec/models/sdk_version_list_rep_spec.rb
+- spec/models/clause_spec.rb
+- spec/models/custom_property_spec.rb
+- 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/flag_global_attributes_rep_spec.rb
-- spec/models/versions_rep_spec.rb
-- spec/models/multi_environment_dependent_flag_spec.rb
-- spec/models/experiment_stats_rep_spec.rb
-- spec/models/patch_with_comment_spec.rb
-- spec/models/inline_object1_spec.rb
+- spec/models/patch_operation_spec.rb
+- spec/models/subject_data_rep_spec.rb
+- spec/models/segment_user_state_spec.rb
+- spec/models/variate_spec.rb
+- spec/models/integration_metadata_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/variation_spec.rb
-- spec/models/feature_flag_body_spec.rb
-- spec/models/ip_list_spec.rb
-- spec/models/link_spec.rb
-- spec/models/audit_log_entry_listing_rep_spec.rb
-- spec/models/token_data_rep_spec.rb
-- spec/models/member_spec.rb
-- spec/models/statistic_collection_rep_spec.rb
-- spec/models/variation_or_rollout_rep_spec.rb
+- spec/models/relay_auto_config_collection_rep_spec.rb
+- spec/models/permission_grant_input_spec.rb
+- spec/models/statistics_root_spec.rb
+- spec/models/client_side_availability_spec.rb
+- spec/models/statement_post_spec.rb
+- spec/models/series_list_rep_spec.rb
+- spec/models/weighted_variation_spec.rb
+- spec/models/post_flag_scheduled_changes_input_spec.rb
+- spec/models/multi_environment_dependent_flag_spec.rb
+- spec/models/statement_post_data_spec.rb
+- spec/models/statement_spec.rb
+- spec/models/destination_post_spec.rb
+- spec/models/title_rep_spec.rb
+- spec/models/segment_user_list_spec.rb
+- spec/models/repository_post_spec.rb
+- spec/models/environment_spec.rb
+- spec/models/branch_collection_rep_spec.rb
+- spec/models/branch_rep_spec.rb
+- spec/models/feature_flag_scheduled_changes_spec.rb
+- spec/models/approval_settings_spec.rb
 - spec/spec_helper.rb