post-setting-values-v2
Batch update feature flags and settings with their complete configuration. Omitted fields are reset, so include all current values and targeting rules to preserve them.
Instructions
This endpoint batch updates the Feature Flags and Settings of a Config identified by the configId parameter
in a specified Environment identified by the environmentId parameter.
Only those Feature Flags and Settings are updated which are part of the request, all the others are left untouched.
Important: As this endpoint is doing a complete replace on those Feature Flags and Settings, which are set in the request. It's important to set every other field that you don't want to change in its original state. Not listing a field means that it will reset.
For example: We have the following resource of a Feature Flag.
{
"settingFormulas": [
{
"defaultValue": {
"boolValue": false
},
"targetingRules": [
{
"conditions": [
{
"userCondition": {
"comparisonAttribute": "Email",
"comparator": "sensitiveTextEquals",
"comparisonValue": {
"stringValue": "test@example.com"
}
}
}
],
"percentageOptions": [],
"value": {
"boolValue": true
}
}
],
"settingId": 1
}
]
}If we send a batch replace request body as below:
{
"updateFormulas": [
{
"defaultValue": {
"boolValue": false
},
"settingId": 1
}
]
}Then besides that the default value is set to true, all Targeting Rules of the related Feature Flag are deleted.
So we get a response like this:
{
"settingFormulas": [
{
"defaultValue": {
"boolValue": false
},
"targetingRules": [],
"setting":
{
"settingId": 1
}
}
]
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | The reason note for the Audit Log if the Product's "Config changes require a reason" preference is turned on. | |
| configId | Yes | The identifier of the Config. | |
| requestBody | Yes | ||
| environmentId | Yes | The identifier of the Environment. | |
| bypassApproval | No | Whether to bypass the approval process and directly apply the change. This is only applicable for users with bypass approval permission. | |
| latestVersionId | No | Optional. The version identifier of the last change made to the Feature Flag or Setting in the Environment. It can be used to make sure concurrent updates are not overwriting each other. If provided and the version identifier does not match the current version, the update will be rejected with a 409 Conflict response. The latest version id can be acquired from the `LastVersionId` property of the response models. |