Update an environment. Updating an environment uses a JSON patch representation of the desired changes. To learn more, read Updates.
To update fields in the environment object that are arrays, set the path to the name of the field and then append /<array index>. Using /0 appends to the beginning of the array.
This request only returns the approvalSettings key if the flag approvals feature is enabled.
Only the canReviewOwnRequest, canApplyDeclinedChanges, minNumApprovals, required and requiredApprovalTagsfields are editable.
If you try to patch the environment by setting both required and requiredApprovalTags, the request fails and an error appears. You can specify either required approvals for all flags in an environment or those with specific tags, but not both.
The project key
The environment key
Environment response
The location and content type of related resources
The ID for the environment. Use this as the client-side ID for authorization in some client-side SDKs, and to associate LaunchDarkly environments with CDN integrations in edge SDKs.
A project-unique key for the new environment
A human-friendly name for the new environment
The SDK key for the environment. Use this for authorization in server-side SDKs.
The mobile key for the environment. Use this for authorization in mobile SDKs.
The color used to indicate this environment in the UI
The default time (in minutes) that the PHP SDK can cache feature flag rules locally
Ensures that one end user of the client-side SDK cannot inspect the variations for another end user
Enables tracking detailed information for new flags by default
Whether members who modify flags and segments through the LaunchDarkly user interface are required to add a comment
Whether members who modify flags and segments through the LaunchDarkly user interface are required to confirm those changes
Whether the environment is critical
Details on the approval settings for this environment
Details on the approval settings for this environment for each resource kind