Predefined variations (#13)

* regenerate

* 3.1.0

Author: novalisdenahi

.openapi-generator/FILES

@@ -48,6 +48,8 @@ model/create-environment-model.ts
 model/create-integration-model.ts
 model/create-or-update-environment-access-model.ts
 model/create-permission-group-request.ts
+model/create-predefined-variation-model.ts
+model/create-predefined-variation-value-model.ts
 model/create-product-request.ts
 model/create-segment-model.ts
 model/create-setting-initial-values.ts
@@ -88,6 +90,8 @@ model/organization-permission-model.ts
 model/organization-product-model.ts
 model/percentage-option-model.ts
 model/permission-group-model.ts
+model/predefined-variation-model.ts
+model/predefined-variation-value-model.ts
 model/preferences-model.ts
 model/prerequisite-comparator.ts
 model/prerequisite-flag-condition-model.ts
@@ -107,6 +111,7 @@ model/segment-condition-model.ts
 model/segment-list-model.ts
 model/segment-model.ts
 model/setting-data-model.ts
+model/setting-data-v2-model.ts
 model/setting-formula-model.ts
 model/setting-model.ts
 model/setting-tag-model.ts
@@ -134,6 +139,9 @@ model/update-evaluation-formulas-model.ts
 model/update-member-permissions-request.ts
 model/update-percentage-option-model.ts
 model/update-permission-group-request.ts
+model/update-predefined-variation-model.ts
+model/update-predefined-variation-value-model.ts
+model/update-predefined-variations-request.ts
 model/update-preferences-request.ts
 model/update-prerequisite-flag-condition-model.ts
 model/update-product-request.ts

api/feature-flags-settings-api.ts

@@ -29,6 +29,8 @@ import { JsonPatchOperation } from '../model';
 import { ReplaceSettingModel } from '../model';
 // @ts-ignore
 import { SettingModel } from '../model';
+// @ts-ignore
+import { UpdatePredefinedVariationsRequest } from '../model';
 /**
  * FeatureFlagsSettingsApi - axios parameter creator
  * @export
@@ -237,6 +239,50 @@ export const FeatureFlagsSettingsApiAxiosParamCreator = function (configuration?
                 options: localVarRequestOptions,
             };
         },
+        /**
+         * This endpoint updates the predefined variations for a Feature Flag or Setting identified by the `settingId` parameter.  **Important:** You can only update a predefined variation\'s value if it is not used anywhere in your feature flags.  **Beta feature:** The feature is currently in closed beta state and cannot be used.
+         * @summary Update predefined variations (Beta)
+         * @param {number} settingId The identifier of the Setting.
+         * @param {UpdatePredefinedVariationsRequest} updatePredefinedVariationsRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        updatePredefinedVariations: async (settingId: number, updatePredefinedVariationsRequest: UpdatePredefinedVariationsRequest, options: RawAxiosRequestConfig = {}): Promise<RequestArgs> => {
+            // verify required parameter 'settingId' is not null or undefined
+            assertParamExists('updatePredefinedVariations', 'settingId', settingId)
+            // verify required parameter 'updatePredefinedVariationsRequest' is not null or undefined
+            assertParamExists('updatePredefinedVariations', 'updatePredefinedVariationsRequest', updatePredefinedVariationsRequest)
+            const localVarPath = `/v1/settings/{settingId}/predefined-variations`
+                .replace(`{${"settingId"}}`, encodeURIComponent(String(settingId)));
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+
+            const localVarRequestOptions = { method: 'PUT', ...baseOptions, ...options};
+            const localVarHeaderParameter = {} as any;
+            const localVarQueryParameter = {} as any;
+
+            // authentication Basic required
+            // http basic authentication required
+            setBasicAuthToObject(localVarRequestOptions, configuration)
+
+
+    
+            localVarHeaderParameter['Content-Type'] = 'application/json';
+
+            setSearchParams(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers};
+            localVarRequestOptions.data = serializeDataIfNeeded(updatePredefinedVariationsRequest, localVarRequestOptions, configuration)
+
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        },
         /**
          * This endpoint updates the metadata of a Feature Flag or Setting  with a collection of [JSON Patch](https://jsonpatch.com) operations in a specified Config.  Only the `name`, `hint` and `tags` attributes are modifiable by this endpoint. The `tags` attribute is a simple collection of the [tag IDs](#operation/get-tags) attached to the given setting.  The advantage of using JSON Patch is that you can describe individual update operations on a resource without touching attributes that you don\'t want to change.  For example: We have the following resource. ```json {   \"settingId\": 5345,   \"key\": \"myGrandFeature\",   \"name\": \"Tihs is a naem with soem typos.\",   \"hint\": \"This flag controls my grandioso feature.\",   \"settingType\": \"boolean\",   \"tags\": [     {       \"tagId\": 0,        \"name\": \"sample tag\",        \"color\": \"whale\"     }   ] } ``` If we send an update request body as below (it changes the `name` and adds the already existing tag with the id `2`): ```json [   {     \"op\": \"replace\",      \"path\": \"/name\",      \"value\": \"This is the name without typos.\"   },    {     \"op\": \"add\",      \"path\": \"/tags/-\",      \"value\": 2   } ] ``` Only the `name` and `tags` are updated and all the other attributes remain unchanged. So we get a response like this: ```json {   \"settingId\": 5345,    \"key\": \"myGrandFeature\",    \"name\": \"This is the name without typos.\",    \"hint\": \"This flag controls my grandioso feature.\",    \"settingType\": \"boolean\",    \"tags\": [     {       \"tagId\": 0,        \"name\": \"sample tag\",        \"color\": \"whale\"     },      {       \"tagId\": 2,        \"name\": \"another tag\",        \"color\": \"koala\"     }   ] } ```
          * @summary Update Flag
@@ -358,6 +404,20 @@ export const FeatureFlagsSettingsApiFp = function(configuration?: Configuration)
             const localVarOperationServerBasePath = operationServerMap['FeatureFlagsSettingsApi.replaceSetting']?.[localVarOperationServerIndex]?.url;
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
+        /**
+         * This endpoint updates the predefined variations for a Feature Flag or Setting identified by the `settingId` parameter.  **Important:** You can only update a predefined variation\'s value if it is not used anywhere in your feature flags.  **Beta feature:** The feature is currently in closed beta state and cannot be used.
+         * @summary Update predefined variations (Beta)
+         * @param {number} settingId The identifier of the Setting.
+         * @param {UpdatePredefinedVariationsRequest} updatePredefinedVariationsRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        async updatePredefinedVariations(settingId: number, updatePredefinedVariationsRequest: UpdatePredefinedVariationsRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SettingModel>> {
+            const localVarAxiosArgs = await localVarAxiosParamCreator.updatePredefinedVariations(settingId, updatePredefinedVariationsRequest, options);
+            const localVarOperationServerIndex = configuration?.serverIndex ?? 0;
+            const localVarOperationServerBasePath = operationServerMap['FeatureFlagsSettingsApi.updatePredefinedVariations']?.[localVarOperationServerIndex]?.url;
+            return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+        },
         /**
          * This endpoint updates the metadata of a Feature Flag or Setting  with a collection of [JSON Patch](https://jsonpatch.com) operations in a specified Config.  Only the `name`, `hint` and `tags` attributes are modifiable by this endpoint. The `tags` attribute is a simple collection of the [tag IDs](#operation/get-tags) attached to the given setting.  The advantage of using JSON Patch is that you can describe individual update operations on a resource without touching attributes that you don\'t want to change.  For example: We have the following resource. ```json {   \"settingId\": 5345,   \"key\": \"myGrandFeature\",   \"name\": \"Tihs is a naem with soem typos.\",   \"hint\": \"This flag controls my grandioso feature.\",   \"settingType\": \"boolean\",   \"tags\": [     {       \"tagId\": 0,        \"name\": \"sample tag\",        \"color\": \"whale\"     }   ] } ``` If we send an update request body as below (it changes the `name` and adds the already existing tag with the id `2`): ```json [   {     \"op\": \"replace\",      \"path\": \"/name\",      \"value\": \"This is the name without typos.\"   },    {     \"op\": \"add\",      \"path\": \"/tags/-\",      \"value\": 2   } ] ``` Only the `name` and `tags` are updated and all the other attributes remain unchanged. So we get a response like this: ```json {   \"settingId\": 5345,    \"key\": \"myGrandFeature\",    \"name\": \"This is the name without typos.\",    \"hint\": \"This flag controls my grandioso feature.\",    \"settingType\": \"boolean\",    \"tags\": [     {       \"tagId\": 0,        \"name\": \"sample tag\",        \"color\": \"whale\"     },      {       \"tagId\": 2,        \"name\": \"another tag\",        \"color\": \"koala\"     }   ] } ```
          * @summary Update Flag
@@ -434,6 +494,17 @@ export const FeatureFlagsSettingsApiFactory = function (configuration?: Configur
         replaceSetting(settingId: number, replaceSettingModel: ReplaceSettingModel, options?: any): AxiosPromise<SettingModel> {
             return localVarFp.replaceSetting(settingId, replaceSettingModel, options).then((request) => request(axios, basePath));
         },
+        /**
+         * This endpoint updates the predefined variations for a Feature Flag or Setting identified by the `settingId` parameter.  **Important:** You can only update a predefined variation\'s value if it is not used anywhere in your feature flags.  **Beta feature:** The feature is currently in closed beta state and cannot be used.
+         * @summary Update predefined variations (Beta)
+         * @param {number} settingId The identifier of the Setting.
+         * @param {UpdatePredefinedVariationsRequest} updatePredefinedVariationsRequest 
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        updatePredefinedVariations(settingId: number, updatePredefinedVariationsRequest: UpdatePredefinedVariationsRequest, options?: any): AxiosPromise<SettingModel> {
+            return localVarFp.updatePredefinedVariations(settingId, updatePredefinedVariationsRequest, options).then((request) => request(axios, basePath));
+        },
         /**
          * This endpoint updates the metadata of a Feature Flag or Setting  with a collection of [JSON Patch](https://jsonpatch.com) operations in a specified Config.  Only the `name`, `hint` and `tags` attributes are modifiable by this endpoint. The `tags` attribute is a simple collection of the [tag IDs](#operation/get-tags) attached to the given setting.  The advantage of using JSON Patch is that you can describe individual update operations on a resource without touching attributes that you don\'t want to change.  For example: We have the following resource. ```json {   \"settingId\": 5345,   \"key\": \"myGrandFeature\",   \"name\": \"Tihs is a naem with soem typos.\",   \"hint\": \"This flag controls my grandioso feature.\",   \"settingType\": \"boolean\",   \"tags\": [     {       \"tagId\": 0,        \"name\": \"sample tag\",        \"color\": \"whale\"     }   ] } ``` If we send an update request body as below (it changes the `name` and adds the already existing tag with the id `2`): ```json [   {     \"op\": \"replace\",      \"path\": \"/name\",      \"value\": \"This is the name without typos.\"   },    {     \"op\": \"add\",      \"path\": \"/tags/-\",      \"value\": 2   } ] ``` Only the `name` and `tags` are updated and all the other attributes remain unchanged. So we get a response like this: ```json {   \"settingId\": 5345,    \"key\": \"myGrandFeature\",    \"name\": \"This is the name without typos.\",    \"hint\": \"This flag controls my grandioso feature.\",    \"settingType\": \"boolean\",    \"tags\": [     {       \"tagId\": 0,        \"name\": \"sample tag\",        \"color\": \"whale\"     },      {       \"tagId\": 2,        \"name\": \"another tag\",        \"color\": \"koala\"     }   ] } ```
          * @summary Update Flag
@@ -517,6 +588,19 @@ export class FeatureFlagsSettingsApi extends BaseAPI {
         return FeatureFlagsSettingsApiFp(this.configuration).replaceSetting(settingId, replaceSettingModel, options).then((request) => request(this.axios, this.basePath));
     }
 
+    /**
+     * This endpoint updates the predefined variations for a Feature Flag or Setting identified by the `settingId` parameter.  **Important:** You can only update a predefined variation\'s value if it is not used anywhere in your feature flags.  **Beta feature:** The feature is currently in closed beta state and cannot be used.
+     * @summary Update predefined variations (Beta)
+     * @param {number} settingId The identifier of the Setting.
+     * @param {UpdatePredefinedVariationsRequest} updatePredefinedVariationsRequest 
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof FeatureFlagsSettingsApi
+     */
+    public updatePredefinedVariations(settingId: number, updatePredefinedVariationsRequest: UpdatePredefinedVariationsRequest, options?: RawAxiosRequestConfig) {
+        return FeatureFlagsSettingsApiFp(this.configuration).updatePredefinedVariations(settingId, updatePredefinedVariationsRequest, options).then((request) => request(this.axios, this.basePath));
+    }
+
     /**
      * This endpoint updates the metadata of a Feature Flag or Setting  with a collection of [JSON Patch](https://jsonpatch.com) operations in a specified Config.  Only the `name`, `hint` and `tags` attributes are modifiable by this endpoint. The `tags` attribute is a simple collection of the [tag IDs](#operation/get-tags) attached to the given setting.  The advantage of using JSON Patch is that you can describe individual update operations on a resource without touching attributes that you don\'t want to change.  For example: We have the following resource. ```json {   \"settingId\": 5345,   \"key\": \"myGrandFeature\",   \"name\": \"Tihs is a naem with soem typos.\",   \"hint\": \"This flag controls my grandioso feature.\",   \"settingType\": \"boolean\",   \"tags\": [     {       \"tagId\": 0,        \"name\": \"sample tag\",        \"color\": \"whale\"     }   ] } ``` If we send an update request body as below (it changes the `name` and adds the already existing tag with the id `2`): ```json [   {     \"op\": \"replace\",      \"path\": \"/name\",      \"value\": \"This is the name without typos.\"   },    {     \"op\": \"add\",      \"path\": \"/tags/-\",      \"value\": 2   } ] ``` Only the `name` and `tags` are updated and all the other attributes remain unchanged. So we get a response like this: ```json {   \"settingId\": 5345,    \"key\": \"myGrandFeature\",    \"name\": \"This is the name without typos.\",    \"hint\": \"This flag controls my grandioso feature.\",    \"settingType\": \"boolean\",    \"tags\": [     {       \"tagId\": 0,        \"name\": \"sample tag\",        \"color\": \"whale\"     },      {       \"tagId\": 2,        \"name\": \"another tag\",        \"color\": \"koala\"     }   ] } ```
      * @summary Update Flag

model/audit-log-type.ts

@@ -47,6 +47,9 @@ export const AuditLogType = {
     SettingChanged: 'settingChanged',
     SettingDeleted: 'settingDeleted',
     SettingsReordered: 'settingsReordered',
+    PredefinedVariationsChanged: 'predefinedVariationsChanged',
+    SettingConvertedToPredefinedVariations: 'settingConvertedToPredefinedVariations',
+    SettingConvertedToCustomValues: 'settingConvertedToCustomValues',
     SettingValueChanged: 'settingValueChanged',
     WebHookCreated: 'webHookCreated',
     WebHookChanged: 'webHookChanged',
@@ -112,7 +115,15 @@ export const AuditLogType = {
     AwsDisconnected: 'awsDisconnected',
     UserEnabled: 'userEnabled',
     SyncUserDeleted: 'syncUserDeleted',
-    SyncGroupDeleted: 'syncGroupDeleted'
+    SyncGroupDeleted: 'syncGroupDeleted',
+    ProxyConfigurationCreated: 'proxyConfigurationCreated',
+    ProxyConfigurationChanged: 'proxyConfigurationChanged',
+    ProxyConfigurationDeleted: 'proxyConfigurationDeleted',
+    ProxyConfigurationSecretRegenerated: 'proxyConfigurationSecretRegenerated',
+    ProxyNotificationSettingsUpdated: 'proxyNotificationSettingsUpdated',
+    ProxyNotificationSettingsDeleted: 'proxyNotificationSettingsDeleted',
+    ProxyNotificationSigningKeyAdded: 'proxyNotificationSigningKeyAdded',
+    ProxyNotificationSigningKeyDeleted: 'proxyNotificationSigningKeyDeleted'
 } as const;
 
 export type AuditLogType = typeof AuditLogType[keyof typeof AuditLogType];

model/comparison-value-list-model.ts

@@ -31,6 +31,6 @@ export interface ComparisonValueListModel {
      * @type {string}
      * @memberof ComparisonValueListModel
      */
-    'hint'?: string | null;
+    'hint': string | null;
 }
 

model/comparison-value-model.ts

@@ -28,18 +28,18 @@ export interface ComparisonValueModel {
      * @type {string}
      * @memberof ComparisonValueModel
      */
-    'stringValue'?: string | null;
+    'stringValue': string | null;
     /**
      * The number representation of the comparison value.
      * @type {number}
      * @memberof ComparisonValueModel
      */
-    'doubleValue'?: number | null;
+    'doubleValue': number | null;
     /**
      * The list representation of the comparison value.
      * @type {Array<ComparisonValueListModel>}
      * @memberof ComparisonValueModel
      */
-    'listValue'?: Array<ComparisonValueListModel> | null;
+    'listValue': Array<ComparisonValueListModel> | null;
 }
 

model/config-setting-formula-model.ts

@@ -18,7 +18,7 @@
 import { IntegrationLinkModel } from './integration-link-model';
 // May contain unused imports in some cases
 // @ts-ignore
-import { SettingDataModel } from './setting-data-model';
+import { SettingDataV2Model } from './setting-data-v2-model';
 // May contain unused imports in some cases
 // @ts-ignore
 import { SettingTagModel } from './setting-tag-model';
@@ -55,10 +55,10 @@ export interface ConfigSettingFormulaModel {
     'targetingRules': Array<TargetingRuleModel>;
     /**
      * 
-     * @type {SettingDataModel}
+     * @type {SettingDataV2Model}
      * @memberof ConfigSettingFormulaModel
      */
-    'setting': SettingDataModel;
+    'setting': SettingDataV2Model;
     /**
      * The last updated date and time when the Feature Flag or Setting.
      * @type {string}