post-setting-values
Replace all values, targeting rules, and percentage rules for a feature flag or setting in a given config and environment. This is a full replacement; include unchanged attributes to avoid resetting them.
Instructions
This endpoint replaces the values of a specified Config's Feature Flags or Settings identified by the configId parameter
in a specified Environment identified by the environmentId parameter.
Only the value, rolloutRules and percentageRules attributes are modifiable by this endpoint.
Important: As this endpoint is doing a complete replace, it's important to set every other attribute that you don't want to change in its original state. Not listing one means it will reset.
For example: We have the following resource.
{
"settingValues": [
{
"rolloutPercentageItems": [
{
"percentage": 30,
"value": true
},
{
"percentage": 70,
"value": false
}
],
"rolloutRules": [],
"value": false,
"settingId": 1
}
]
}If we send a replace request body as below:
{
"settingValues": [
{
"value": true,
"settingId": 1
}
]
}Then besides that the default value is set to true, all the Percentage Rules are deleted.
So we get a response like this:
{
"settingValues": [
{
"rolloutPercentageItems": [],
"rolloutRules": [],
"value": true,
"setting":
{
"settingId": 1
}
}
]
}The rolloutRules property describes two types of rules:
Targeting rules: When you want to add or update a targeting rule, the
comparator,comparisonAttribute, andcomparisonValuemembers are required.Segment rules: When you want to add add or update a segment rule, the
segmentIdwhich identifies the desired segment and thesegmentComparatormembers are required.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| configId | Yes | The identifier of the Config. | |
| environmentId | Yes | The identifier of the Environment. | |
| reason | No | The reason note for the Audit Log if the Product's "Config changes require a reason" preference is turned on. | |
| requestBody | Yes |