From e656850bfb69d5e8021f8429f49ea5e31362e557 Mon Sep 17 00:00:00 2001 From: Lajos Date: Wed, 14 Oct 2020 17:21:07 +0200 Subject: [PATCH] api update --- README.md | 36 +- api/swagger.yaml | 1298 ++++++++++++++--- api_audit_logs.go | 4 +- api_configs.go | 335 ++++- api_environments.go | 161 +- api_feature_flag_setting_values.go | 8 +- ...ature_flag_setting_values_using_sdk_key.go | 97 +- api_feature_flags_settings.go | 12 +- api_integration_links.go | 2 +- api_me.go | 2 +- api_organizations.go | 109 ++ api_products.go | 334 ++++- api_tags.go | 443 ++++++ client.go | 8 +- configuration.go | 4 +- docs/AuditLogsApi.md | 4 +- docs/ConfigModelhaljsonLinks.md | 1 + docs/ConfigsApi.md | 122 +- docs/CreateConfigRequest.md | 9 + docs/CreateProductRequest.md | 9 + docs/CreateSettingModel.md | 1 + docs/CreateTagModel.md | 10 + docs/EnvironmentModelHaljson.md | 11 + docs/EnvironmentModelhaljsonLinks.md | 9 + docs/EnvironmentsApi.md | 66 +- docs/FeatureFlagSettingValuesApi.md | 8 +- .../FeatureFlagSettingValuesUsingSDKKeyApi.md | 8 +- docs/FeatureFlagsSettingsApi.md | 12 +- docs/IntegrationLinksApi.md | 2 +- docs/MeApi.md | 2 +- docs/OrganizationModelHaljson.md | 11 + docs/OrganizationModelhaljsonLinks.md | 9 + docs/OrganizationsApi.md | 32 + ...ProductModelhaljsonEmbeddedOrganization.md | 1 + docs/ProductModelhaljsonLinks.md | 2 + docs/ProductsApi.md | 120 +- docs/SettingModel.md | 1 + docs/SettingModelHaljson.md | 20 + docs/SettingModelhaljsonEmbedded.md | 9 + docs/SettingModelhaljsonEmbeddedTags.md | 12 + docs/SettingValueModelHaljson.md | 2 +- ...ingValueModelhaljsonEmbeddedEnvironment.md | 1 + docs/TagModel.md | 11 + docs/TagModelHaljson.md | 12 + docs/TagsApi.md | 154 ++ docs/UpdateConfigRequest.md | 9 + docs/UpdateProductRequest.md | 9 + docs/UpdateTagModel.md | 10 + model_add_or_update_integration_link_model.go | 4 +- model_audit_log_item_model.go | 2 +- model_audit_log_type.go | 2 +- model_config_model.go | 2 +- model_config_model_haljson.go | 2 +- model_config_modelhaljson__links.go | 3 +- model_create_config_request.go | 14 + model_create_environment_model.go | 2 +- model_create_product_request.go | 14 + model_create_setting_model.go | 4 +- model_create_tag_model.go | 15 + model_delete_integration_link_model.go | 2 +- model_environment_model.go | 2 +- model_environment_model_haljson.go | 16 + model_environment_modelhaljson__links.go | 14 + model_integration_link_detail.go | 2 +- model_integration_link_details_model.go | 2 +- model_integration_link_model.go | 2 +- model_integration_link_type.go | 2 +- model_me_model.go | 2 +- model_operation.go | 2 +- model_organization_model.go | 2 +- model_organization_model_haljson.go | 16 + model_organization_modelhaljson__links.go | 14 + model_product_model.go | 2 +- model_product_model_haljson.go | 2 +- model_product_modelhaljson__embedded.go | 2 +- ...uct_modelhaljson__embedded_organization.go | 3 +- model_product_modelhaljson__links.go | 4 +- model_rollout_percentage_item_model.go | 2 +- model_rollout_rule_comparator.go | 2 +- model_rollout_rule_model.go | 2 +- model_setting_data_model.go | 2 +- model_setting_model.go | 3 +- model_setting_model_haljson.go | 24 + model_setting_modelhaljson__embedded.go | 14 + model_setting_modelhaljson__embedded_tags.go | 17 + model_setting_tag_model.go | 2 +- model_setting_type.go | 2 +- model_setting_value_model.go | 2 +- model_setting_value_model_haljson.go | 6 +- model_setting_value_modelhaljson__embedded.go | 2 +- ...ing_value_modelhaljson__embedded_config.go | 2 +- ...alue_modelhaljson__embedded_environment.go | 3 +- ...odelhaljson__embedded_integration_links.go | 2 +- ...ng_value_modelhaljson__embedded_setting.go | 2 +- ...lue_modelhaljson__embedded_setting_tags.go | 2 +- model_tag_model.go | 16 + model_tag_model_haljson.go | 17 + model_update_config_request.go | 14 + model_update_environment_model.go | 2 +- model_update_product_request.go | 14 + model_update_setting_value_model.go | 2 +- model_update_tag_model.go | 15 + response.go | 2 +- 103 files changed, 3524 insertions(+), 356 deletions(-) create mode 100644 api_organizations.go create mode 100644 api_tags.go create mode 100644 docs/CreateConfigRequest.md create mode 100644 docs/CreateProductRequest.md create mode 100644 docs/CreateTagModel.md create mode 100644 docs/EnvironmentModelHaljson.md create mode 100644 docs/EnvironmentModelhaljsonLinks.md create mode 100644 docs/OrganizationModelHaljson.md create mode 100644 docs/OrganizationModelhaljsonLinks.md create mode 100644 docs/OrganizationsApi.md create mode 100644 docs/SettingModelHaljson.md create mode 100644 docs/SettingModelhaljsonEmbedded.md create mode 100644 docs/SettingModelhaljsonEmbeddedTags.md create mode 100644 docs/TagModel.md create mode 100644 docs/TagModelHaljson.md create mode 100644 docs/TagsApi.md create mode 100644 docs/UpdateConfigRequest.md create mode 100644 docs/UpdateProductRequest.md create mode 100644 docs/UpdateTagModel.md create mode 100644 model_create_config_request.go create mode 100644 model_create_product_request.go create mode 100644 model_create_tag_model.go create mode 100644 model_environment_model_haljson.go create mode 100644 model_environment_modelhaljson__links.go create mode 100644 model_organization_model_haljson.go create mode 100644 model_organization_modelhaljson__links.go create mode 100644 model_setting_model_haljson.go create mode 100644 model_setting_modelhaljson__embedded.go create mode 100644 model_setting_modelhaljson__embedded_tags.go create mode 100644 model_tag_model.go create mode 100644 model_tag_model_haljson.go create mode 100644 model_update_config_request.go create mode 100644 model_update_product_request.go create mode 100644 model_update_tag_model.go diff --git a/README.md b/README.md index 694b2a6..c956480 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Go API client for configcatpublicapi -**Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. +**Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. ## Overview This API client was generated by the [swagger-codegen](https://github.com/swagger-api/swagger-codegen) project. By using the [swagger-spec](https://github.com/swagger-api/swagger-spec) from a remote server, you can easily generate an API client. @@ -18,13 +18,19 @@ import "./configcatpublicapi" ## Documentation for API Endpoints -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Class | Method | HTTP request | Description ------------ | ------------- | ------------- | ------------- *AuditLogsApi* | [**GetAuditlogs**](docs/AuditLogsApi.md#getauditlogs) | **Get** /v1/products/{productId}/auditlogs | List Audit logs +*ConfigsApi* | [**CreateConfig**](docs/ConfigsApi.md#createconfig) | **Post** /v1/products/{productId}/configs | Create Config +*ConfigsApi* | [**DeleteConfig**](docs/ConfigsApi.md#deleteconfig) | **Delete** /v1/configs/{configId} | Delete Config +*ConfigsApi* | [**GetConfig**](docs/ConfigsApi.md#getconfig) | **Get** /v1/configs/{configId} | Get Config *ConfigsApi* | [**GetConfigs**](docs/ConfigsApi.md#getconfigs) | **Get** /v1/products/{productId}/configs | List Configs +*ConfigsApi* | [**UpdateConfig**](docs/ConfigsApi.md#updateconfig) | **Put** /v1/configs/{configId} | Update Config *EnvironmentsApi* | [**CreateEnvironment**](docs/EnvironmentsApi.md#createenvironment) | **Post** /v1/products/{productId}/environments | Create Environment +*EnvironmentsApi* | [**DeleteEnvironment**](docs/EnvironmentsApi.md#deleteenvironment) | **Delete** /v1/environments/{environmentId} | Delete Environment +*EnvironmentsApi* | [**GetEnvironment**](docs/EnvironmentsApi.md#getenvironment) | **Get** /v1/environments/{environmentId} | Get Environment *EnvironmentsApi* | [**GetEnvironments**](docs/EnvironmentsApi.md#getenvironments) | **Get** /v1/products/{productId}/environments | List Environments *EnvironmentsApi* | [**UpdateEnvironment**](docs/EnvironmentsApi.md#updateenvironment) | **Put** /v1/environments/{environmentId} | Update Environment *FeatureFlagSettingValuesApi* | [**GetSettingValue**](docs/FeatureFlagSettingValuesApi.md#getsettingvalue) | **Get** /v1/environments/{environmentId}/settings/{settingId}/value | Get value @@ -42,7 +48,17 @@ Class | Method | HTTP request | Description *IntegrationLinksApi* | [**DeleteIntegrationLink**](docs/IntegrationLinksApi.md#deleteintegrationlink) | **Delete** /v1/environments/{environmentId}/settings/{settingId}/integrationLinks/{integrationLinkType}/{key} | Delete Integration link *IntegrationLinksApi* | [**GetIntegrationLinkDetails**](docs/IntegrationLinksApi.md#getintegrationlinkdetails) | **Get** /v1/integrationLink/{integrationLinkType}/{key}/details | Get Integration link *MeApi* | [**GetMe**](docs/MeApi.md#getme) | **Get** /v1/me | Get authenticated user details +*OrganizationsApi* | [**GetOrganizations**](docs/OrganizationsApi.md#getorganizations) | **Get** /v1/organizations | List Organizations +*ProductsApi* | [**CreateProduct**](docs/ProductsApi.md#createproduct) | **Post** /v1/organizations/{organizationId}/products | Create Product +*ProductsApi* | [**DeleteProduct**](docs/ProductsApi.md#deleteproduct) | **Delete** /v1/products/{productId} | Delete Product +*ProductsApi* | [**GetProduct**](docs/ProductsApi.md#getproduct) | **Get** /v1/products/{productId} | Get Product *ProductsApi* | [**GetProducts**](docs/ProductsApi.md#getproducts) | **Get** /v1/products | List Products +*ProductsApi* | [**UpdateProduct**](docs/ProductsApi.md#updateproduct) | **Put** /v1/products/{productId} | Update Product +*TagsApi* | [**CreateTag**](docs/TagsApi.md#createtag) | **Post** /v1/products/{productId}/tags | Create Tag +*TagsApi* | [**DeleteTag**](docs/TagsApi.md#deletetag) | **Delete** /v1/tags/{tagId} | Delete Tag +*TagsApi* | [**GetTag**](docs/TagsApi.md#gettag) | **Get** /v1/tags/{tagId} | Get Tag +*TagsApi* | [**GetTags**](docs/TagsApi.md#gettags) | **Get** /v1/products/{productId}/tags | List Tags +*TagsApi* | [**UpdateTag**](docs/TagsApi.md#updatetag) | **Put** /v1/tags/{tagId} | Update Tag ## Documentation For Models @@ -52,10 +68,15 @@ Class | Method | HTTP request | Description - [ConfigModel](docs/ConfigModel.md) - [ConfigModelHaljson](docs/ConfigModelHaljson.md) - [ConfigModelhaljsonLinks](docs/ConfigModelhaljsonLinks.md) + - [CreateConfigRequest](docs/CreateConfigRequest.md) - [CreateEnvironmentModel](docs/CreateEnvironmentModel.md) + - [CreateProductRequest](docs/CreateProductRequest.md) - [CreateSettingModel](docs/CreateSettingModel.md) + - [CreateTagModel](docs/CreateTagModel.md) - [DeleteIntegrationLinkModel](docs/DeleteIntegrationLinkModel.md) - [EnvironmentModel](docs/EnvironmentModel.md) + - [EnvironmentModelHaljson](docs/EnvironmentModelHaljson.md) + - [EnvironmentModelhaljsonLinks](docs/EnvironmentModelhaljsonLinks.md) - [IntegrationLinkDetail](docs/IntegrationLinkDetail.md) - [IntegrationLinkDetailsModel](docs/IntegrationLinkDetailsModel.md) - [IntegrationLinkModel](docs/IntegrationLinkModel.md) @@ -63,6 +84,8 @@ Class | Method | HTTP request | Description - [MeModel](docs/MeModel.md) - [Operation](docs/Operation.md) - [OrganizationModel](docs/OrganizationModel.md) + - [OrganizationModelHaljson](docs/OrganizationModelHaljson.md) + - [OrganizationModelhaljsonLinks](docs/OrganizationModelhaljsonLinks.md) - [ProductModel](docs/ProductModel.md) - [ProductModelHaljson](docs/ProductModelHaljson.md) - [ProductModelhaljsonEmbedded](docs/ProductModelhaljsonEmbedded.md) @@ -73,6 +96,9 @@ Class | Method | HTTP request | Description - [RolloutRuleModel](docs/RolloutRuleModel.md) - [SettingDataModel](docs/SettingDataModel.md) - [SettingModel](docs/SettingModel.md) + - [SettingModelHaljson](docs/SettingModelHaljson.md) + - [SettingModelhaljsonEmbedded](docs/SettingModelhaljsonEmbedded.md) + - [SettingModelhaljsonEmbeddedTags](docs/SettingModelhaljsonEmbeddedTags.md) - [SettingTagModel](docs/SettingTagModel.md) - [SettingType](docs/SettingType.md) - [SettingValueModel](docs/SettingValueModel.md) @@ -83,9 +109,13 @@ Class | Method | HTTP request | Description - [SettingValueModelhaljsonEmbeddedIntegrationLinks](docs/SettingValueModelhaljsonEmbeddedIntegrationLinks.md) - [SettingValueModelhaljsonEmbeddedSetting](docs/SettingValueModelhaljsonEmbeddedSetting.md) - [SettingValueModelhaljsonEmbeddedSettingTags](docs/SettingValueModelhaljsonEmbeddedSettingTags.md) - - [SettingValueModelhaljsonLinks](docs/SettingValueModelhaljsonLinks.md) + - [TagModel](docs/TagModel.md) + - [TagModelHaljson](docs/TagModelHaljson.md) + - [UpdateConfigRequest](docs/UpdateConfigRequest.md) - [UpdateEnvironmentModel](docs/UpdateEnvironmentModel.md) + - [UpdateProductRequest](docs/UpdateProductRequest.md) - [UpdateSettingValueModel](docs/UpdateSettingValueModel.md) + - [UpdateTagModel](docs/UpdateTagModel.md) ## Documentation For Authorization diff --git a/api/swagger.yaml b/api/swagger.yaml index c33566d..2543f36 100644 --- a/api/swagger.yaml +++ b/api/swagger.yaml @@ -1,28 +1,28 @@ openapi: 3.0.1 info: title: ConfigCat Public Management API - description: "**Base API URL**: https://api.configcat.com\n\nIf you prefer the swagger\ - \ documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger).\n\ - \nThe purpose of this API is to access the ConfigCat platform programmatically.\ - \ \nYou can **Create**, **Read**, **Update** and **Delete** any entities like\ - \ **Feature Flags, Configs, Environments** or **Products** within ConfigCat. \n\ - \nThe API is based on HTTP REST, uses resource-oriented URLs, status codes and\ - \ supports JSON \nand JSON+HAL format. Do not use this API for accessing and evaluating\ - \ feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview).\n\ - \n\n# OpenAPI Specification\n\nThe complete specification is publicly available\ - \ here: [swagger.json](v1/swagger.json). \nYou can use it to generate client libraries\ - \ in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator)\ - \ or\n[Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact\ - \ with this API.\n\n# Authentication\nThis API uses the [Basic HTTP Authentication\ - \ Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). \n\n\n\n# Throttling and rate limits\nAll\ - \ the rate limited API calls are returning information about the current rate\ - \ limit period in the following HTTP headers:\n\n| Header | Description |\n| :-\ - \ | :- |\n| X-Rate-Limit-Remaining | The maximum number of requests remaining\ - \ in the current rate limit period. |\n| X-Rate-Limit-Reset | The time\twhen\ - \ the current rate limit period resets.\t\t\t\t\t\t |\n\nWhen the rate limit\ - \ is exceeded by a request, the API returns with a `HTTP 429 - Too many requests`\ - \ status along with a `Retry-After` HTTP header.\n" + description: "**Base API URL**: https://localhost\r\n\r\nIf you prefer the swagger\ + \ documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger).\r\ + \n\r\nThe purpose of this API is to access the ConfigCat platform programmatically.\ + \ \r\nYou can **Create**, **Read**, **Update** and **Delete** any entities like\ + \ **Feature Flags, Configs, Environments** or **Products** within ConfigCat. \r\ + \n\r\nThe API is based on HTTP REST, uses resource-oriented URLs, status codes\ + \ and supports JSON \r\nand JSON+HAL format. Do not use this API for accessing\ + \ and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview).\r\ + \n\r\n\r\n# OpenAPI Specification\r\n\r\nThe complete specification is publicly\ + \ available here: [swagger.json](v1/swagger.json). \r\nYou can use it to generate\ + \ client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator)\ + \ or\r\n[Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact\ + \ with this API.\r\n\r\n# Authentication\r\nThis API uses the [Basic HTTP Authentication\ + \ Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). \r\n\r\n\ + \r\n\r\n# Throttling and rate limits\r\ + \nAll the rate limited API calls are returning information about the current rate\ + \ limit period in the following HTTP headers:\r\n\r\n| Header | Description |\r\ + \n| :- | :- |\r\n| X-Rate-Limit-Remaining | The maximum number of requests remaining\ + \ in the current rate limit period. |\r\n| X-Rate-Limit-Reset | The time\t\ + when the current rate limit period resets.\t\t\t\t\t\t |\r\n\r\nWhen the rate\ + \ limit is exceeded by a request, the API returns with a `HTTP 429 - Too many\ + \ requests` status along with a `Retry-After` HTTP header.\r\n" termsOfService: https://configcat.com/termsofserviceagreement contact: name: ConfigCat @@ -30,63 +30,71 @@ info: email: support@configcat.com version: v1 x-logo: - url: https://api.configcat.com/resources/configcat-logo-horiz.svg + url: https://localhost/resources/configcat-logo-horiz.svg servers: -- url: https://api.configcat.com +- url: https://localhost security: - Basic: [] tags: - name: Feature Flag & Setting values using SDK Key description: "With these endpoints you can control how your existing Feature Flags\ - \ and Settings should serve their values. \nYou can turn Feature Flags on or off,\ - \ update Setting values and also add, remove or change the order of Percentage\ - \ and Targeting Rules.\n\nThese endpoints are determining the Environment and\ - \ Config by the SDK key passed in\nthe `X-CONFIGCAT-SDKKEY` request header. To identify the\ - \ desired Feature Flag or Setting to change, \nyou can use either its `settingId`\ - \ or `key` attribute. You can get those attributes \nfrom the [Feature Flag &\ - \ Setting](#tag/Feature-Flags-and-Settings) endpoints." + \ and Settings should serve their values. \r\nYou can turn Feature Flags on or\ + \ off, update Setting values and also add, remove or change the order of Percentage\ + \ and Targeting Rules.\r\n\r\nThese endpoints are determining the Environment\ + \ and Config by the SDK key passed in\r\nthe `X-CONFIGCAT-SDKKEY` request header. To identify\ + \ the desired Feature Flag or Setting to change, \r\nyou can use either its `settingId`\ + \ or `key` attribute. You can get those attributes \r\nfrom the [Feature Flag\ + \ & Setting](#tag/Feature-Flags-and-Settings) endpoints." - name: Feature Flag & Setting values description: "With these endpoints you can control how your existing Feature Flags\ - \ and Settings should serve their values. \nYou can turn Feature Flags on or off,\ - \ update Setting values and also add, remove or reorder Percentage and Targeting\ - \ Rules.\n\nTo determine which Feature Flag or Setting you want to work with you\ - \ have to pass its `settingId`. It can be\nobtained from the [Feature Flag & Setting](#tag/Feature-Flags-and-Settings)\ - \ endpoints.\n\nYou also have to specify in which Environment you want to change\ - \ the served value configuration by its\n`environmentId` which can be obtained\ - \ from the [List Environments](#operation/get-environments) endpoint." + \ and Settings should serve their values. \r\nYou can turn Feature Flags on or\ + \ off, update Setting values and also add, remove or reorder Percentage and Targeting\ + \ Rules.\r\n\r\nTo determine which Feature Flag or Setting you want to work with\ + \ you have to pass its `settingId`. It can be\r\nobtained from the [Feature Flag\ + \ & Setting](#tag/Feature-Flags-and-Settings) endpoints.\r\n\r\nYou also have\ + \ to specify in which Environment you want to change the served value configuration\ + \ by its\r\n`environmentId` which can be obtained from the [List Environments](#operation/get-environments)\ + \ endpoint." - name: Feature Flags & Settings description: "With these endpoints you can manage your Feature Flags or Settings\ - \ within a Config. \nHowever you can't use them for manipulating the values of\ - \ your Feature Flags and Settings,\nto do that please visit the [Feature Flag\ - \ & Setting values using SDK Key](#tag/Feature-Flag-and-Setting-values-using-SDK-Key)\n\ - and [Feature Flag & Setting values](#tag/Feature-Flag-and-Setting-values) sections\ - \ of the API.\n\nFor using these endpoints, first you have to select which Config\ - \ you want to work with by its `configId` \nwhich can be obtained from the [List\ - \ Configs](#operation/get-configs) endpoint. \nThen you can use it to create new\ - \ Feature Flags or to get information about existing ones.\n\nThen you can obtain\ - \ the `settingId` or `key` of your desired Feature Flag or Setting \nto use them\ - \ for further operations in this API. \n\nHere you can read more about\ - \ the concept of Settings." + \ within a Config. \r\nHowever you can't use them for manipulating the values\ + \ of your Feature Flags and Settings,\r\nto do that please visit the [Feature\ + \ Flag & Setting values using SDK Key](#tag/Feature-Flag-and-Setting-values-using-SDK-Key)\r\ + \nand [Feature Flag & Setting values](#tag/Feature-Flag-and-Setting-values) sections\ + \ of the API.\r\n\r\nFor using these endpoints, first you have to select which\ + \ Config you want to work with by its `configId` \r\nwhich can be obtained from\ + \ the [List Configs](#operation/get-configs) endpoint. \r\nThen you can use it\ + \ to create new Feature Flags or to get information about existing ones.\r\n\r\ + \nThen you can obtain the `settingId` or `key` of your desired Feature Flag or\ + \ Setting \r\nto use them for further operations in this API. \r\n\r\nHere you can read more about the concept of Settings." +- name: Organizations + description: "With these endpoints you can get useful information about your Organizations.\r\ + \nThis also can be used to manage your [Products](#tag/Products).\r\n\r\nHere you can read more about the Organizations." - name: Products - description: |- - With these endpoints you can get useful information about your Products. - This also can be used to manage [Environments](#tag/Environments) and [Configs](#tag/Configs) through this API. - - Here you can read more about the concept of Products. + description: "With these endpoints you can get useful information about your Products.\r\ + \nThis also can be used to manage [Environments](#tag/Environments) and [Configs](#tag/Configs)\ + \ through this API.\r\n\r\nHere you can read more about\ + \ the concept of Products." - name: Configs - description: "With these endpoints you can get useful information about your Configs.\n\ - This also can be used to manage [Feature Flags and Settings](#tag/Feature-Flags-and-Settings)\ - \ and their \n[served values](#tag/Feature-Flag-and-Setting-values) through this\ - \ API.\n\nHere you can read more about the concept\ - \ of Configs." + description: "With these endpoints you can get useful information about your Configs.\r\ + \nThis also can be used to manage [Feature Flags and Settings](#tag/Feature-Flags-and-Settings)\ + \ and their \r\n[served values](#tag/Feature-Flag-and-Setting-values) through\ + \ this API.\r\n\r\nHere you can read more about\ + \ the concept of Configs." - name: Environments description: "With these endpoints you can update existing Environments or add new\ - \ ones into your selected [Product](#tag/Products). \n\nHere you can read more about\ \ the concept of Environments." +- name: Tags + description: With these endpoints you can manage your Tags. - name: Audit logs description: Access audit log entries. - name: Me @@ -98,7 +106,7 @@ paths: - Audit logs summary: List Audit logs description: "This endpoint returns the list of Audit logs for a given Product\ - \ \nand the result can be optionally filtered by Config and/or Environment." + \ \r\nand the result can be optionally filtered by Config and/or Environment." operationId: get-auditlogs parameters: - name: productId @@ -187,9 +195,9 @@ paths: tags: - Configs summary: List Configs - description: |- - This endpoint returns the list of the Configs that belongs to the given Product identified by the - `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. + description: "This endpoint returns the list of the Configs that belongs to\ + \ the given Product identified by the\r\n`productId` parameter, which can\ + \ be obtained from the [List Products](#operation/get-products) endpoint." operationId: get-configs parameters: - name: productId @@ -225,14 +233,178 @@ paths: "429": description: Too many requests. In case of the request rate exceeds the rate limits. + post: + tags: + - Configs + summary: Create Config + description: "This endpoint creates a new Config in a specified Product \r\n\ + identified by the `productId` parameter, which can be obtained from the [List\ + \ Products](#operation/get-products) endpoint." + operationId: create-config + parameters: + - name: productId + in: path + description: The identifier of the Product. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + requestBody: + content: + application/json: + schema: + $ref: '#/components/schemas/CreateConfigRequest' + text/json: + schema: + $ref: '#/components/schemas/CreateConfigRequest' + application/*+json: + schema: + $ref: '#/components/schemas/CreateConfigRequest' + required: true + responses: + "201": + description: When the creation was successful. + content: + application/json: + schema: + $ref: '#/components/schemas/ConfigModel' + application/hal+json: + schema: + $ref: '#/components/schemas/ConfigModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + /v1/configs/{configId}: + get: + tags: + - Configs + summary: Get Config + description: "This endpoint returns the metadata of a Config\r\nidentified by\ + \ the `configId`." + operationId: get-config + parameters: + - name: configId + in: path + description: The identifier of the Config. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + responses: + "200": + description: When everything is ok, the config data returned. + content: + application/json: + schema: + $ref: '#/components/schemas/ConfigModel' + application/hal+json: + schema: + $ref: '#/components/schemas/ConfigModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + put: + tags: + - Configs + summary: Update Config + description: This endpoint updates a Config identified by the `configId` parameter. + operationId: update-config + parameters: + - name: configId + in: path + description: The identifier of the Config. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + requestBody: + content: + application/json: + schema: + $ref: '#/components/schemas/UpdateConfigRequest' + text/json: + schema: + $ref: '#/components/schemas/UpdateConfigRequest' + application/*+json: + schema: + $ref: '#/components/schemas/UpdateConfigRequest' + required: true + responses: + "200": + content: + application/json: + schema: + $ref: '#/components/schemas/ConfigModel' + application/hal+json: + schema: + $ref: '#/components/schemas/ConfigModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + delete: + tags: + - Configs + summary: Delete Config + description: This endpoint removes a Config identified by the `configId` parameter. + operationId: delete-config + parameters: + - name: configId + in: path + description: The identifier of the Config. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + responses: + "204": + description: When the delete was successful. + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. /v1/products/{productId}/environments: get: tags: - Environments summary: List Environments - description: |- - This endpoint returns the list of the Environments that belongs to the given Product identified by the - `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. + description: "This endpoint returns the list of the Environments that belongs\ + \ to the given Product identified by the\r\n`productId` parameter, which can\ + \ be obtained from the [List Products](#operation/get-products) endpoint." operationId: get-environments parameters: - name: productId @@ -257,7 +429,7 @@ paths: schema: type: array items: - $ref: '#/components/schemas/EnvironmentModel' + $ref: '#/components/schemas/EnvironmentModel-haljson' "400": description: Bad request. "404": @@ -273,8 +445,8 @@ paths: - Environments summary: Create Environment description: "This endpoint creates a new Environment in a specified Product\ - \ \nidentified by the `productId` parameter, which can be obtained from the\ - \ [List Products](#operation/get-products) endpoint." + \ \r\nidentified by the `productId` parameter, which can be obtained from\ + \ the [List Products](#operation/get-products) endpoint." operationId: create-environment parameters: - name: productId @@ -299,14 +471,15 @@ paths: $ref: '#/components/schemas/CreateEnvironmentModel' required: true responses: - "200": + "201": + description: When the creation was successful. content: application/json: schema: $ref: '#/components/schemas/EnvironmentModel' application/hal+json: schema: - $ref: '#/components/schemas/EnvironmentModel' + $ref: '#/components/schemas/EnvironmentModel-haljson' "400": description: Bad request. "404": @@ -318,6 +491,43 @@ paths: description: Too many requests. In case of the request rate exceeds the rate limits. /v1/environments/{environmentId}: + get: + tags: + - Environments + summary: Get Environment + description: "This endpoint returns the metadata of an Environment \r\nidentified\ + \ by the `environmentId`." + operationId: get-environment + parameters: + - name: environmentId + in: path + description: The identifier of the Environment. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + responses: + "200": + description: When everything is ok, the environment data returned. + content: + application/json: + schema: + $ref: '#/components/schemas/EnvironmentModel' + application/hal+json: + schema: + $ref: '#/components/schemas/EnvironmentModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. put: tags: - Environments @@ -328,7 +538,7 @@ paths: parameters: - name: environmentId in: path - description: The identifier of the Product. + description: The identifier of the Environment. required: true style: simple explode: false @@ -355,7 +565,37 @@ paths: $ref: '#/components/schemas/EnvironmentModel' application/hal+json: schema: - $ref: '#/components/schemas/EnvironmentModel' + $ref: '#/components/schemas/EnvironmentModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + delete: + tags: + - Environments + summary: Delete Environment + description: This endpoint removes an Environment identified by the `environmentId` + parameter. + operationId: delete-environment + parameters: + - name: environmentId + in: path + description: The identifier of the Environment. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + responses: + "204": + description: When the delete was successful. "400": description: Bad request. "404": @@ -371,17 +611,17 @@ paths: tags: - Feature Flag & Setting values summary: Get value - description: "This endpoint returns the value of a Feature Flag or Setting \n\ - in a specified Environment identified by the `environmentId` parameter.\n\n\ - The most important attributes in the response are the `value`, `rolloutRules`\ - \ and `percentageRules`.\nThe `value` represents what the clients will get\ - \ when the evaluation requests of our SDKs \nare not matching to any of the\ - \ defined Targeting or Percentage Rules, or when there are no additional rules\ - \ to evaluate.\n\nThe `rolloutRules` and `percentageRules` attributes are\ - \ representing the current \nTargeting and Percentage Rules configuration\ - \ of the actual Feature Flag or Setting \nin an **ordered** collection, which\ - \ means the order of the returned rules is matching to the\nevaluation order.\ - \ You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/)." + description: "This endpoint returns the value of a Feature Flag or Setting \r\ + \nin a specified Environment identified by the `environmentId` parameter.\r\ + \n\r\nThe most important attributes in the response are the `value`, `rolloutRules`\ + \ and `percentageRules`.\r\nThe `value` represents what the clients will get\ + \ when the evaluation requests of our SDKs \r\nare not matching to any of\ + \ the defined Targeting or Percentage Rules, or when there are no additional\ + \ rules to evaluate.\r\n\r\nThe `rolloutRules` and `percentageRules` attributes\ + \ are representing the current \r\nTargeting and Percentage Rules configuration\ + \ of the actual Feature Flag or Setting \r\nin an **ordered** collection,\ + \ which means the order of the returned rules is matching to the\r\nevaluation\ + \ order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/)." operationId: get-setting-value parameters: - name: environmentId @@ -427,18 +667,20 @@ paths: - Feature Flag & Setting values summary: Replace value description: "This endpoint replaces the whole value of a Feature Flag or Setting\ - \ in a specified Environment.\n\nOnly the `value`, `rolloutRules` and `percentageRules`\ - \ attributes are modifiable by this endpoint.\n\n**Important:** As this endpoint\ - \ is doing a complete replace, it's important to set every other attribute\ - \ that you don't \nwant to change in its original state. Not listing one means\ - \ that it will reset.\n\nFor example: We have the following resource.\n```\n\ - {\n\t\"rolloutPercentageItems\": [\n\t\t{\n\t\t\t\"percentage\": 30,\n\t\t\ - \t\"value\": true\n\t\t},\n\t\t{\n\t\t\t\"percentage\": 70,\n\t\t\t\"value\"\ - : false\n\t\t}\n\t],\n\t\"rolloutRules\": [],\n\t\"value\": false\n}\n```\n\ - If we send a replace request body as below:\n```\n{\n\t\"value\": true\n}\n\ - ```\nThen besides that the default value is set to `true`, all the Percentage\ - \ Rules are deleted. \nSo we get a response like this:\n```\n{\n\t\"rolloutPercentageItems\"\ - : [],\n\t\"rolloutRules\": [],\n\t\"value\": true\n}\n```" + \ in a specified Environment.\r\n\r\nOnly the `value`, `rolloutRules` and\ + \ `percentageRules` attributes are modifiable by this endpoint.\r\n\r\n**Important:**\ + \ As this endpoint is doing a complete replace, it's important to set every\ + \ other attribute that you don't \r\nwant to change in its original state.\ + \ Not listing one means that it will reset.\r\n\r\nFor example: We have the\ + \ following resource.\r\n```\r\n{\r\n\t\"rolloutPercentageItems\": [\r\n\t\ + \t{\r\n\t\t\t\"percentage\": 30,\r\n\t\t\t\"value\": true\r\n\t\t},\r\n\t\t\ + {\r\n\t\t\t\"percentage\": 70,\r\n\t\t\t\"value\": false\r\n\t\t}\r\n\t],\r\ + \n\t\"rolloutRules\": [],\r\n\t\"value\": false\r\n}\r\n```\r\nIf we send\ + \ a replace request body as below:\r\n```\r\n{\r\n\t\"value\": true\r\n}\r\ + \n```\r\nThen besides that the default value is set to `true`, all the Percentage\ + \ Rules are deleted. \r\nSo we get a response like this:\r\n```\r\n{\r\n\t\ + \"rolloutPercentageItems\": [],\r\n\t\"rolloutRules\": [],\r\n\t\"value\"\ + : true\r\n}\r\n```" operationId: replace-setting-value parameters: - name: environmentId @@ -549,24 +791,25 @@ paths: tags: - Feature Flag & Setting values summary: Update value - description: "This endpoint updates the value of a Feature Flag or Setting \n\ - with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified\ - \ Environment.\n\nOnly the `value`, `rolloutRules` and `percentageRules` attributes\ - \ are modifiable by this endpoint.\n\nThe advantage of using JSON Patch is\ - \ that you can describe individual update operations on a resource\nwithout\ - \ touching attributes that you don't want to change. It supports collection\ - \ reordering, so it also \ncan be used for reordering the targeting rules\ - \ of a Feature Flag or Setting.\n\nFor example: We have the following resource.\n\ - ```\n{\n\t\"rolloutPercentageItems\": [\n\t\t{\n\t\t\t\"percentage\": 30,\n\ - \t\t\t\"value\": true\n\t\t},\n\t\t{\n\t\t\t\"percentage\": 70,\n\t\t\t\"\ - value\": false\n\t\t}\n\t],\n\t\"rolloutRules\": [],\n\t\"value\": false\n\ - }\n```\nIf we send an update request body as below:\n```\n[\n\t{\n\t\t\"op\"\ - : \"replace\",\n\t\t\"path\": \"/value\",\n\t\t\"value\": true\n\t}\n]\n```\n\ - Only the default value is going to be set to `true` and all the Percentage\ - \ Rules are remaining unchanged.\nSo we get a response like this:\n```\n{\n\ - \t\"rolloutPercentageItems\": [\n\t\t{\n\t\t\t\"percentage\": 30,\n\t\t\t\"\ - value\": true\n\t\t},\n\t\t{\n\t\t\t\"percentage\": 70,\n\t\t\t\"value\":\ - \ false\n\t\t}\n\t],\n\t\"rolloutRules\": [],\n\t\"value\": true\n}\n```" + description: "This endpoint updates the value of a Feature Flag or Setting \r\ + \nwith a collection of [JSON Patch](http://jsonpatch.com) operations in a\ + \ specified Environment.\r\n\r\nOnly the `value`, `rolloutRules` and `percentageRules`\ + \ attributes are modifiable by this endpoint.\r\n\r\nThe advantage of using\ + \ JSON Patch is that you can describe individual update operations on a resource\r\ + \nwithout touching attributes that you don't want to change. It supports collection\ + \ reordering, so it also \r\ncan be used for reordering the targeting rules\ + \ of a Feature Flag or Setting.\r\n\r\nFor example: We have the following\ + \ resource.\r\n```\r\n{\r\n\t\"rolloutPercentageItems\": [\r\n\t\t{\r\n\t\t\ + \t\"percentage\": 30,\r\n\t\t\t\"value\": true\r\n\t\t},\r\n\t\t{\r\n\t\t\t\ + \"percentage\": 70,\r\n\t\t\t\"value\": false\r\n\t\t}\r\n\t],\r\n\t\"rolloutRules\"\ + : [],\r\n\t\"value\": false\r\n}\r\n```\r\nIf we send an update request body\ + \ as below:\r\n```\r\n[\r\n\t{\r\n\t\t\"op\": \"replace\",\r\n\t\t\"path\"\ + : \"/value\",\r\n\t\t\"value\": true\r\n\t}\r\n]\r\n```\r\nOnly the default\ + \ value is going to be set to `true` and all the Percentage Rules are remaining\ + \ unchanged.\r\nSo we get a response like this:\r\n```\r\n{\r\n\t\"rolloutPercentageItems\"\ + : [\r\n\t\t{\r\n\t\t\t\"percentage\": 30,\r\n\t\t\t\"value\": true\r\n\t\t\ + },\r\n\t\t{\r\n\t\t\t\"percentage\": 70,\r\n\t\t\t\"value\": false\r\n\t\t\ + }\r\n\t],\r\n\t\"rolloutRules\": [],\r\n\t\"value\": true\r\n}\r\n```" operationId: update-setting-value parameters: - name: environmentId @@ -831,19 +1074,19 @@ paths: tags: - Feature Flag & Setting values using SDK Key summary: Get value - description: "This endpoint returns the value of a Feature Flag or Setting \n\ - in a specified Environment identified by the SDK key passed\ - \ in the `X-CONFIGCAT-SDKKEY` header.\n\nThe most important attributes in\ - \ the response are the `value`, `rolloutRules` and `percentageRules`.\nThe\ - \ `value` represents what the clients will get when the evaluation requests\ - \ of our SDKs \nare not matching to any of the defined Targeting or Percentage\ - \ Rules, or when there are no additional rules to evaluate.\n\nThe `rolloutRules`\ - \ and `percentageRules` attributes are representing the current \nTargeting\ + description: "This endpoint returns the value of a Feature Flag or Setting \r\ + \nin a specified Environment identified by the SDK key\ + \ passed in the `X-CONFIGCAT-SDKKEY` header.\r\n\r\nThe most important attributes\ + \ in the response are the `value`, `rolloutRules` and `percentageRules`.\r\ + \nThe `value` represents what the clients will get when the evaluation requests\ + \ of our SDKs \r\nare not matching to any of the defined Targeting or Percentage\ + \ Rules, or when there are no additional rules to evaluate.\r\n\r\nThe `rolloutRules`\ + \ and `percentageRules` attributes are representing the current \r\nTargeting\ \ and Percentage Rules configuration of the actual Feature Flag or Setting\ - \ \nin an **ordered** collection, which means the order of the returned rules\ - \ is matching to the\nevaluation order. You can read more about these rules\ - \ [here](https://configcat.com/docs/advanced/targeting/)." + \ \r\nin an **ordered** collection, which means the order of the returned\ + \ rules is matching to the\r\nevaluation order. You can read more about these\ + \ rules [here](https://configcat.com/docs/advanced/targeting/)." operationId: get-setting-value-by-sdkkey parameters: - name: settingKeyOrId @@ -886,21 +1129,22 @@ paths: - Feature Flag & Setting values using SDK Key summary: Replace value description: "This endpoint replaces the value of a Feature Flag or Setting\ - \ \nin a specified Environment identified by the SDK key\ - \ passed in the `X-CONFIGCAT-SDKKEY` header.\n\nOnly the `value`, `rolloutRules`\ - \ and `percentageRules` attributes are modifiable by this endpoint.\n\n**Important:**\ - \ As this endpoint is doing a complete replace, it's important to set every\ - \ other attribute that you don't \nwant to change to its original state. Not\ - \ listing one means that it will reset.\n\nFor example: We have the following\ - \ resource.\n```\n{\n\t\"rolloutPercentageItems\": [\n\t\t{\n\t\t\t\"percentage\"\ - : 30,\n\t\t\t\"value\": true\n\t\t},\n\t\t{\n\t\t\t\"percentage\": 70,\n\t\ - \t\t\"value\": false\n\t\t}\n\t],\n\t\"rolloutRules\": [],\n\t\"value\": false\n\ - }\n```\nIf we send a replace request body as below:\n```\n{\n\t\"value\":\ - \ true\n}\n```\nThen besides that the default served value is set to `true`,\ - \ all the Percentage Rules are deleted. \nSo we get a response like this:\n\ - ```\n{\n\t\"rolloutPercentageItems\": [],\n\t\"rolloutRules\": [],\n\t\"value\"\ - : true\n}\n```" + \ passed in the `X-CONFIGCAT-SDKKEY` header.\r\n\r\nOnly the `value`, `rolloutRules`\ + \ and `percentageRules` attributes are modifiable by this endpoint.\r\n\r\n\ + **Important:** As this endpoint is doing a complete replace, it's important\ + \ to set every other attribute that you don't \r\nwant to change to its original\ + \ state. Not listing one means that it will reset.\r\n\r\nFor example: We\ + \ have the following resource.\r\n```\r\n{\r\n\t\"rolloutPercentageItems\"\ + : [\r\n\t\t{\r\n\t\t\t\"percentage\": 30,\r\n\t\t\t\"value\": true\r\n\t\t\ + },\r\n\t\t{\r\n\t\t\t\"percentage\": 70,\r\n\t\t\t\"value\": false\r\n\t\t\ + }\r\n\t],\r\n\t\"rolloutRules\": [],\r\n\t\"value\": false\r\n}\r\n```\r\n\ + If we send a replace request body as below:\r\n```\r\n{\r\n\t\"value\": true\r\ + \n}\r\n```\r\nThen besides that the default served value is set to `true`,\ + \ all the Percentage Rules are deleted. \r\nSo we get a response like this:\r\ + \n```\r\n{\r\n\t\"rolloutPercentageItems\": [],\r\n\t\"rolloutRules\": [],\r\ + \n\t\"value\": true\r\n}\r\n```" operationId: replace-setting-value-by-sdkkey parameters: - name: settingKeyOrId @@ -1009,26 +1253,28 @@ paths: tags: - Feature Flag & Setting values using SDK Key summary: Update value - description: "This endpoint updates the value of a Feature Flag or Setting \n\ - with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified\ - \ Environment\nidentified by the SDK key passed in the `X-CONFIGCAT-SDKKEY`\ - \ header.\n\nOnly the `value`, `rolloutRules` and `percentageRules` attributes\ - \ are modifiable by this endpoint.\n\nThe advantage of using JSON Patch is\ - \ that you can describe individual update operations on a resource\nwithout\ - \ touching attributes that you don't want to change. It supports collection\ - \ reordering, so it also \ncan be used for reordering the targeting rules\ - \ of a Feature Flag or Setting.\n\nFor example: We have the following resource.\n\ - ```\n{\n\t\"rolloutPercentageItems\": [\n\t\t{\n\t\t\t\"percentage\": 30,\n\ - \t\t\t\"value\": true\n\t\t},\n\t\t{\n\t\t\t\"percentage\": 70,\n\t\t\t\"\ - value\": false\n\t\t}\n\t],\n\t\"rolloutRules\": [],\n\t\"value\": false\n\ - }\n```\nIf we send an update request body as below:\n```\n[\n\t{\n\t\t\"op\"\ - : \"replace\",\n\t\t\"path\": \"/value\",\n\t\t\"value\": true\n\t}\n]\n```\n\ - Only the default served value is going to be set to `true` and all the Percentage\ - \ Rules are remaining unchanged.\nSo we get a response like this:\n```\n{\n\ - \t\"rolloutPercentageItems\": [\n\t\t{\n\t\t\t\"percentage\": 30,\n\t\t\t\"\ - value\": true\n\t\t},\n\t\t{\n\t\t\t\"percentage\": 70,\n\t\t\t\"value\":\ - \ false\n\t\t}\n\t],\n\t\"rolloutRules\": [],\n\t\"value\": true\n}\n```" + description: "This endpoint updates the value of a Feature Flag or Setting \r\ + \nwith a collection of [JSON Patch](http://jsonpatch.com) operations in a\ + \ specified Environment\r\nidentified by the SDK key passed\ + \ in the `X-CONFIGCAT-SDKKEY` header.\r\n\r\nOnly the `value`, `rolloutRules`\ + \ and `percentageRules` attributes are modifiable by this endpoint.\r\n\r\n\ + The advantage of using JSON Patch is that you can describe individual update\ + \ operations on a resource\r\nwithout touching attributes that you don't want\ + \ to change. It supports collection reordering, so it also \r\ncan be used\ + \ for reordering the targeting rules of a Feature Flag or Setting.\r\n\r\n\ + For example: We have the following resource.\r\n```\r\n{\r\n\t\"rolloutPercentageItems\"\ + : [\r\n\t\t{\r\n\t\t\t\"percentage\": 30,\r\n\t\t\t\"value\": true\r\n\t\t\ + },\r\n\t\t{\r\n\t\t\t\"percentage\": 70,\r\n\t\t\t\"value\": false\r\n\t\t\ + }\r\n\t],\r\n\t\"rolloutRules\": [],\r\n\t\"value\": false\r\n}\r\n```\r\n\ + If we send an update request body as below:\r\n```\r\n[\r\n\t{\r\n\t\t\"op\"\ + : \"replace\",\r\n\t\t\"path\": \"/value\",\r\n\t\t\"value\": true\r\n\t}\r\ + \n]\r\n```\r\nOnly the default served value is going to be set to `true` and\ + \ all the Percentage Rules are remaining unchanged.\r\nSo we get a response\ + \ like this:\r\n```\r\n{\r\n\t\"rolloutPercentageItems\": [\r\n\t\t{\r\n\t\ + \t\t\"percentage\": 30,\r\n\t\t\t\"value\": true\r\n\t\t},\r\n\t\t{\r\n\t\t\ + \t\"percentage\": 70,\r\n\t\t\t\"value\": false\r\n\t\t}\r\n\t],\r\n\t\"rolloutRules\"\ + : [],\r\n\t\"value\": true\r\n}\r\n```" operationId: update-setting-value-by-sdkkey parameters: - name: settingKeyOrId @@ -1291,7 +1537,7 @@ paths: - Feature Flags & Settings summary: List Flags description: "This endpoint returns the list of the Feature Flags and Settings\ - \ defined in a \nspecified Config, identified by the `configId` parameter." + \ defined in a \r\nspecified Config, identified by the `configId` parameter." operationId: get-settings parameters: - name: configId @@ -1316,7 +1562,7 @@ paths: schema: type: array items: - $ref: '#/components/schemas/SettingModel' + $ref: '#/components/schemas/SettingModel-haljson' "400": description: Bad request. "404": @@ -1331,11 +1577,9 @@ paths: tags: - Feature Flags & Settings summary: Create Flag - description: |- - This endpoint creates a new Feature Flag or Setting in a specified Config - identified by the `configId` parameter. - - **Important:** The `key` attribute must be unique within the given Config. + description: "This endpoint creates a new Feature Flag or Setting in a specified\ + \ Config\r\nidentified by the `configId` parameter.\r\n\r\n**Important:**\ + \ The `key` attribute must be unique within the given Config." operationId: create-setting parameters: - name: configId @@ -1368,7 +1612,7 @@ paths: $ref: '#/components/schemas/SettingModel' application/hal+json: schema: - $ref: '#/components/schemas/SettingModel' + $ref: '#/components/schemas/SettingModel-haljson' "400": description: Bad request. "404": @@ -1385,7 +1629,7 @@ paths: - Feature Flags & Settings summary: Get Flag description: "This endpoint returns the metadata attributes of a Feature Flag\ - \ or Setting \nidentified by the `settingId` parameter." + \ or Setting \r\nidentified by the `settingId` parameter." operationId: get-setting parameters: - name: settingId @@ -1406,7 +1650,7 @@ paths: $ref: '#/components/schemas/SettingModel' application/hal+json: schema: - $ref: '#/components/schemas/SettingModel' + $ref: '#/components/schemas/SettingModel-haljson' "400": description: Bad request. "404": @@ -1422,7 +1666,7 @@ paths: - Feature Flags & Settings summary: Delete Flag description: "This endpoint removes a Feature Flag or Setting from a specified\ - \ Config, \nidentified by the `configId` parameter." + \ Config, \r\nidentified by the `configId` parameter." operationId: delete-setting parameters: - name: settingId @@ -1452,21 +1696,22 @@ paths: - Feature Flags & Settings summary: Update Flag description: "This endpoint updates the metadata of a Feature Flag or Setting\ - \ \nwith a collection of [JSON Patch](http://jsonpatch.com) operations in\ - \ a specified Config.\n\nOnly the `name` and `hint` attributes are modifiable\ - \ by this endpoint.\n\nThe advantage of using JSON Patch is that you can describe\ - \ individual update operations on a resource\nwithout touching attributes\ - \ that you don't want to change.\n\nFor example: We have the following resource.\n\ - ```\n{\n\t\"settingId\": 5345,\n\t\"key\": \"myAwesomeFeature\",\n\t\"name\"\ - : \"Tihs is a naem with soem typos.\",\n\t\"hint\": \"This Flag controls my\ - \ awesome feature.\",\n\t\"settingType\": \"boolean\"\n}\n```\nIf we send\ - \ an update request body as below:\n```\n[\n\t{\n\t\t\"op\": \"replace\",\n\ - \t\t\"path\": \"/name\",\n\t\t\"value\": \"This is the name without typos.\"\ - \n\t}\n]\n```\nOnly the name is going to be updated and all the other attributes\ - \ are remaining unchanged.\nSo we get a response like this:\n```\n{\n\t\"\ - settingId\": 5345,\n\t\"key\": \"myAwesomeFeature\",\n\t\"name\": \"This is\ - \ the name without typos.\",\n\t\"hint\": \"This Flag controls my awesome\ - \ feature.\",\n\t\"settingType\": \"boolean\"\n}\n```" + \ \r\nwith a collection of [JSON Patch](http://jsonpatch.com) operations in\ + \ a specified Config.\r\n\r\nOnly the `name` and `hint` attributes are modifiable\ + \ by this endpoint.\r\n\r\nThe advantage of using JSON Patch is that you can\ + \ describe individual update operations on a resource\r\nwithout touching\ + \ attributes that you don't want to change.\r\n\r\nFor example: We have the\ + \ following resource.\r\n```\r\n{\r\n\t\"settingId\": 5345,\r\n\t\"key\":\ + \ \"myAwesomeFeature\",\r\n\t\"name\": \"Tihs is a naem with soem typos.\"\ + ,\r\n\t\"hint\": \"This Flag controls my awesome feature.\",\r\n\t\"settingType\"\ + : \"boolean\"\r\n}\r\n```\r\nIf we send an update request body as below:\r\ + \n```\r\n[\r\n\t{\r\n\t\t\"op\": \"replace\",\r\n\t\t\"path\": \"/name\",\r\ + \n\t\t\"value\": \"This is the name without typos.\"\r\n\t}\r\n]\r\n```\r\n\ + Only the name is going to be updated and all the other attributes are remaining\ + \ unchanged.\r\nSo we get a response like this:\r\n```\r\n{\r\n\t\"settingId\"\ + : 5345,\r\n\t\"key\": \"myAwesomeFeature\",\r\n\t\"name\": \"This is the name\ + \ without typos.\",\r\n\t\"hint\": \"This Flag controls my awesome feature.\"\ + ,\r\n\t\"settingType\": \"boolean\"\r\n}\r\n```" operationId: update-setting parameters: - name: settingId @@ -1510,7 +1755,7 @@ paths: $ref: '#/components/schemas/SettingModel' application/hal+json: schema: - $ref: '#/components/schemas/SettingModel' + $ref: '#/components/schemas/SettingModel-haljson' "400": description: Bad request. "404": @@ -1718,6 +1963,34 @@ paths: "429": description: Too many requests. In case of the request rate exceeds the rate limits. + /v1/organizations: + get: + tags: + - Organizations + summary: List Organizations + description: This endpoint returns the list of the Organizations that belongs + to the user. + operationId: get-organizations + responses: + "200": + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/OrganizationModel' + x-content-type: application/json + application/hal+json: + schema: + type: array + items: + $ref: '#/components/schemas/OrganizationModel-haljson' + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. /v1/products: get: tags: @@ -1746,24 +2019,391 @@ paths: "429": description: Too many requests. In case of the request rate exceeds the rate limits. -components: - schemas: - AuditLogType: - type: string - enum: - - productCreated - - productChanged - - productOwnershipTransferred - - productDeleted - - teamMemberInvited - - teamMemberInvitationRevoked - - teamMemberJoined - - teamMemberPermissionGroupChanged - - teamMemberRemoved - - teamMemberLeft - - teamMemberInvitationChanged - - teamMemberInvitationResent - - teamMemberInvitationRejected + /v1/organizations/{organizationId}/products: + post: + tags: + - Products + summary: Create Product + description: "This endpoint creates a new Product in a specified Organization\ + \ \r\nidentified by the `organizationId` parameter, which can be obtained\ + \ from the [List Organizations](#operation/get-organizations) endpoint." + operationId: create-product + parameters: + - name: organizationId + in: path + description: The identifier of the Organization. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + requestBody: + content: + application/json: + schema: + $ref: '#/components/schemas/CreateProductRequest' + text/json: + schema: + $ref: '#/components/schemas/CreateProductRequest' + application/*+json: + schema: + $ref: '#/components/schemas/CreateProductRequest' + required: true + responses: + "201": + description: When the creation was successful. + content: + application/json: + schema: + $ref: '#/components/schemas/ProductModel' + application/hal+json: + schema: + $ref: '#/components/schemas/ProductModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + /v1/products/{productId}: + get: + tags: + - Products + summary: Get Product + description: "This endpoint returns the metadata of a Product \r\nidentified\ + \ by the `productId`." + operationId: get-product + parameters: + - name: productId + in: path + description: The identifier of the Product. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + responses: + "200": + description: When everything is ok, the product data returned. + content: + application/json: + schema: + $ref: '#/components/schemas/ProductModel' + application/hal+json: + schema: + $ref: '#/components/schemas/ProductModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + put: + tags: + - Products + summary: Update Product + description: This endpoint updates a Product identified by the `productId` parameter. + operationId: update-product + parameters: + - name: productId + in: path + description: The identifier of the Product. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + requestBody: + content: + application/json: + schema: + $ref: '#/components/schemas/UpdateProductRequest' + text/json: + schema: + $ref: '#/components/schemas/UpdateProductRequest' + application/*+json: + schema: + $ref: '#/components/schemas/UpdateProductRequest' + required: true + responses: + "200": + content: + application/json: + schema: + $ref: '#/components/schemas/ProductModel' + application/hal+json: + schema: + $ref: '#/components/schemas/ProductModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + delete: + tags: + - Products + summary: Delete Product + description: This endpoint removes a Product identified by the `productId` parameter. + operationId: delete-product + parameters: + - name: productId + in: path + description: The identifier of the Product. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + responses: + "204": + description: When the delete was successful. + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + /v1/products/{productId}/tags: + get: + tags: + - Tags + summary: List Tags + description: "This endpoint returns the list of the Tags in a \r\nspecified\ + \ Product, identified by the `productId` parameter." + operationId: get-tags + parameters: + - name: productId + in: path + description: The identifier of the Product. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + responses: + "200": + content: + application/json: + schema: + type: array + items: + $ref: '#/components/schemas/TagModel' + x-content-type: application/json + application/hal+json: + schema: + type: array + items: + $ref: '#/components/schemas/TagModel-haljson' + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + post: + tags: + - Tags + summary: Create Tag + description: "This endpoint creates a new Tag in a specified Product \r\nidentified\ + \ by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products)\ + \ endpoint." + operationId: create-tag + parameters: + - name: productId + in: path + description: The identifier of the Organization. + required: true + style: simple + explode: false + schema: + type: string + format: uuid + requestBody: + content: + application/json: + schema: + $ref: '#/components/schemas/CreateTagModel' + text/json: + schema: + $ref: '#/components/schemas/CreateTagModel' + application/*+json: + schema: + $ref: '#/components/schemas/CreateTagModel' + required: true + responses: + "201": + description: When the creation was successful. + content: + application/json: + schema: + $ref: '#/components/schemas/TagModel' + application/hal+json: + schema: + $ref: '#/components/schemas/TagModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + /v1/tags/{tagId}: + get: + tags: + - Tags + summary: Get Tag + description: "This endpoint returns the metadata of a Tag \r\nidentified by\ + \ the `tagId`." + operationId: get-tag + parameters: + - name: tagId + in: path + description: The identifier of the Tag. + required: true + style: simple + explode: false + schema: + type: integer + format: int64 + responses: + "200": + description: When everything is ok, the tag data returned. + content: + application/json: + schema: + $ref: '#/components/schemas/TagModel' + application/hal+json: + schema: + $ref: '#/components/schemas/TagModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + put: + tags: + - Tags + summary: Update Tag + description: This endpoint updates a Tag identified by the `tagId` parameter. + operationId: update-tag + parameters: + - name: tagId + in: path + description: The identifier of the Tag. + required: true + style: simple + explode: false + schema: + type: integer + format: int64 + requestBody: + content: + application/json: + schema: + $ref: '#/components/schemas/UpdateTagModel' + text/json: + schema: + $ref: '#/components/schemas/UpdateTagModel' + application/*+json: + schema: + $ref: '#/components/schemas/UpdateTagModel' + required: true + responses: + "200": + content: + application/json: + schema: + $ref: '#/components/schemas/TagModel' + application/hal+json: + schema: + $ref: '#/components/schemas/TagModel-haljson' + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. + delete: + tags: + - Tags + summary: Delete Tag + description: This endpoint removes a Tag identified by the `tagId` parameter. + operationId: delete-tag + parameters: + - name: tagId + in: path + description: The identifier of the Tag. + required: true + style: simple + explode: false + schema: + type: integer + format: int64 + responses: + "204": + description: When the delete was successful. + "400": + description: Bad request. + "404": + description: Not found. + "401": + description: Unauthorized. In case of the Public Management API credentials + are invalid. + "429": + description: Too many requests. In case of the request rate exceeds the + rate limits. +components: + schemas: + AuditLogType: + type: string + enum: + - productCreated + - productChanged + - productOwnershipTransferred + - productDeleted + - teamMemberInvited + - teamMemberInvitationRevoked + - teamMemberJoined + - teamMemberPermissionGroupChanged + - teamMemberRemoved + - teamMemberLeft + - teamMemberInvitationChanged + - teamMemberInvitationResent + - teamMemberInvitationRejected - configCreated - configChanged - configDeleted @@ -1869,6 +2509,36 @@ components: example: configId: 046b6c7f-0b8a-43b9-b35d-6489e6daee91 name: name + CreateConfigRequest: + required: + - name + type: object + properties: + name: + maxLength: 255 + minLength: 0 + type: string + additionalProperties: false + UpdateConfigRequest: + type: object + properties: + name: + maxLength: 255 + minLength: 0 + type: string + nullable: true + additionalProperties: false + EnvironmentModel-haljson: + type: object + properties: + environmentId: + type: string + format: uuid + name: + type: string + nullable: true + _links: + $ref: '#/components/schemas/EnvironmentModelhaljson__links' EnvironmentModel: type: object properties: @@ -2116,7 +2786,7 @@ components: description: The value to serve. It must respect the setting type. nullable: true _links: - $ref: '#/components/schemas/SettingValueModelhaljson__links' + $ref: '#/components/schemas/EnvironmentModelhaljson__links' SettingValueModel: type: object properties: @@ -2260,39 +2930,130 @@ components: type: string nullable: true additionalProperties: false + TagModel-haljson: + type: object + properties: + tagId: + type: integer + format: int64 + name: + type: string + nullable: true + color: + type: string + nullable: true + _links: + $ref: '#/components/schemas/EnvironmentModelhaljson__links' + TagModel: + type: object + properties: + tagId: + type: integer + format: int64 + name: + type: string + nullable: true + color: + type: string + nullable: true + additionalProperties: false + example: + color: color + tagId: 6 + name: name + SettingModel-haljson: + type: object + properties: + settingId: + type: integer + format: int32 + readOnly: true + key: + type: string + nullable: true + readOnly: true + name: + type: string + nullable: true + readOnly: true + hint: + type: string + nullable: true + readOnly: true + settingType: + $ref: '#/components/schemas/SettingType' + ownerUserEmail: + type: string + nullable: true + readOnly: true + ownerUserFullName: + type: string + nullable: true + readOnly: true + expirationWarningAt: + type: string + format: date-time + nullable: true + readOnly: true + configId: + type: string + format: uuid + readOnly: true + configName: + type: string + nullable: true + readOnly: true + _embedded: + $ref: '#/components/schemas/SettingModelhaljson__embedded' + _links: + $ref: '#/components/schemas/EnvironmentModelhaljson__links' SettingModel: type: object properties: settingId: type: integer format: int32 + readOnly: true key: type: string nullable: true + readOnly: true name: type: string nullable: true + readOnly: true hint: type: string nullable: true + readOnly: true settingType: $ref: '#/components/schemas/SettingType' ownerUserEmail: type: string nullable: true + readOnly: true ownerUserFullName: type: string nullable: true + readOnly: true expirationWarningAt: type: string format: date-time nullable: true + readOnly: true configId: type: string format: uuid + readOnly: true configName: type: string nullable: true + readOnly: true + tags: + type: array + nullable: true + items: + $ref: '#/components/schemas/TagModel' additionalProperties: false example: configName: configName @@ -2305,6 +3066,13 @@ components: ownerUserEmail: ownerUserEmail key: key settingId: 0 + tags: + - color: color + tagId: 6 + name: name + - color: color + tagId: 6 + name: name CreateSettingModel: required: - key @@ -2332,7 +3100,24 @@ components: description: A short description for the setting, shown on the Dashboard UI. nullable: true + tags: + type: array + description: The tags attached to the setting. + nullable: true + items: + $ref: '#/components/schemas/TagModel' additionalProperties: false + OrganizationModel-haljson: + type: object + properties: + organizationId: + type: string + format: uuid + name: + type: string + nullable: true + _links: + $ref: '#/components/schemas/OrganizationModelhaljson__links' OrganizationModel: type: object properties: @@ -2524,6 +3309,55 @@ components: example: fullName: fullName email: email + CreateProductRequest: + required: + - name + type: object + properties: + name: + maxLength: 1000 + minLength: 0 + type: string + additionalProperties: false + UpdateProductRequest: + type: object + properties: + name: + maxLength: 1000 + minLength: 0 + type: string + nullable: true + additionalProperties: false + CreateTagModel: + required: + - name + type: object + properties: + name: + maxLength: 255 + minLength: 0 + type: string + color: + maxLength: 255 + minLength: 0 + type: string + nullable: true + additionalProperties: false + UpdateTagModel: + required: + - name + type: object + properties: + name: + maxLength: 255 + minLength: 0 + type: string + color: + maxLength: 255 + minLength: 0 + type: string + nullable: true + additionalProperties: false auditLogType: nullable: true allOf: @@ -2531,8 +3365,15 @@ components: ConfigModelhaljson__links: type: object properties: + self: + type: string settings: type: string + EnvironmentModelhaljson__links: + type: object + properties: + self: + type: string SettingValueModelhaljson__embedded_setting: type: object properties: @@ -2597,6 +3438,8 @@ components: name: type: string nullable: true + _links: + $ref: '#/components/schemas/EnvironmentModelhaljson__links' SettingValueModelhaljson__embedded_integrationLinks: type: object properties: @@ -2643,10 +3486,31 @@ components: type: array items: $ref: '#/components/schemas/SettingValueModelhaljson__embedded_settingTags' - SettingValueModelhaljson__links: + SettingModelhaljson__embedded_tags: type: object properties: - self: + tagId: + type: integer + format: int64 + name: + type: string + nullable: true + color: + type: string + nullable: true + _links: + $ref: '#/components/schemas/EnvironmentModelhaljson__links' + SettingModelhaljson__embedded: + type: object + properties: + tags: + type: array + items: + $ref: '#/components/schemas/SettingModelhaljson__embedded_tags' + OrganizationModelhaljson__links: + type: object + properties: + products: type: string ProductModelhaljson__embedded_organization: type: object @@ -2657,6 +3521,8 @@ components: name: type: string nullable: true + _links: + $ref: '#/components/schemas/OrganizationModelhaljson__links' ProductModelhaljson__embedded: type: object properties: @@ -2665,17 +3531,21 @@ components: ProductModelhaljson__links: type: object properties: + self: + type: string configs: type: string environments: type: string + tags: + type: string securitySchemes: Basic: type: http description: |- To authenticate with the API you have to fill the `Authorization` HTTP request header with your Public API credentials. - You can create your credentials on the Public API credentials management page. + You can create your credentials on the Public API credentials management page. scheme: basic x-tagGroups: - name: Feature Flag values @@ -2685,8 +3555,10 @@ x-tagGroups: - name: Feature Flag metadata tags: - Feature Flags & Settings + - Tags - name: General tags: + - Organizations - Products - Configs - Environments diff --git a/api_audit_logs.go b/api_audit_logs.go index 7f17437..803207b 100644 --- a/api_audit_logs.go +++ b/api_audit_logs.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -29,7 +29,7 @@ type AuditLogsApiService service /* AuditLogsApiService List Audit logs -This endpoint returns the list of Audit logs for a given Product and the result can be optionally filtered by Config and/or Environment. +This endpoint returns the list of Audit logs for a given Product and the result can be optionally filtered by Config and/or Environment. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param productId The identifier of the Product. * @param optional nil or *AuditLogsApiGetAuditlogsOpts - Optional Parameters: diff --git a/api_configs.go b/api_configs.go index 1981fac..530707d 100644 --- a/api_configs.go +++ b/api_configs.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -25,9 +25,251 @@ var ( type ConfigsApiService service +/* +ConfigsApiService Create Config +This endpoint creates a new Config in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param body + * @param productId The identifier of the Product. +@return ConfigModel +*/ +func (a *ConfigsApiService) CreateConfig(ctx context.Context, body CreateConfigRequest, productId string) (ConfigModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Post") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue ConfigModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/products/{productId}/configs" + localVarPath = strings.Replace(localVarPath, "{"+"productId"+"}", fmt.Sprintf("%v", productId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{"application/json", "text/json", "application/_*+json"} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + // body params + localVarPostBody = &body + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 201 { + var v ConfigModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} + +/* +ConfigsApiService Delete Config +This endpoint removes a Config identified by the `configId` parameter. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param configId The identifier of the Config. + +*/ +func (a *ConfigsApiService) DeleteConfig(ctx context.Context, configId string) (*http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Delete") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/configs/{configId}" + localVarPath = strings.Replace(localVarPath, "{"+"configId"+"}", fmt.Sprintf("%v", configId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + return localVarHttpResponse, newErr + } + + return localVarHttpResponse, nil +} + +/* +ConfigsApiService Get Config +This endpoint returns the metadata of a Config identified by the `configId`. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param configId The identifier of the Config. +@return ConfigModel +*/ +func (a *ConfigsApiService) GetConfig(ctx context.Context, configId string) (ConfigModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Get") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue ConfigModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/configs/{configId}" + localVarPath = strings.Replace(localVarPath, "{"+"configId"+"}", fmt.Sprintf("%v", configId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 200 { + var v ConfigModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} + /* ConfigsApiService List Configs -This endpoint returns the list of the Configs that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. +This endpoint returns the list of the Configs that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param productId The identifier of the Product. @return []ConfigModel @@ -110,3 +352,92 @@ func (a *ConfigsApiService) GetConfigs(ctx context.Context, productId string) ([ return localVarReturnValue, localVarHttpResponse, nil } + +/* +ConfigsApiService Update Config +This endpoint updates a Config identified by the `configId` parameter. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param body + * @param configId The identifier of the Config. +@return ConfigModel +*/ +func (a *ConfigsApiService) UpdateConfig(ctx context.Context, body UpdateConfigRequest, configId string) (ConfigModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Put") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue ConfigModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/configs/{configId}" + localVarPath = strings.Replace(localVarPath, "{"+"configId"+"}", fmt.Sprintf("%v", configId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{"application/json", "text/json", "application/_*+json"} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + // body params + localVarPostBody = &body + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 200 { + var v ConfigModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} diff --git a/api_environments.go b/api_environments.go index 06cd9c4..9df4314 100644 --- a/api_environments.go +++ b/api_environments.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -27,7 +27,7 @@ type EnvironmentsApiService service /* EnvironmentsApiService Create Environment -This endpoint creates a new Environment in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. +This endpoint creates a new Environment in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param body * @param productId The identifier of the Product. @@ -93,6 +93,159 @@ func (a *EnvironmentsApiService) CreateEnvironment(ctx context.Context, body Cre } } + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 201 { + var v EnvironmentModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} + +/* +EnvironmentsApiService Delete Environment +This endpoint removes an Environment identified by the `environmentId` parameter. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param environmentId The identifier of the Environment. + +*/ +func (a *EnvironmentsApiService) DeleteEnvironment(ctx context.Context, environmentId string) (*http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Delete") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/environments/{environmentId}" + localVarPath = strings.Replace(localVarPath, "{"+"environmentId"+"}", fmt.Sprintf("%v", environmentId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + return localVarHttpResponse, newErr + } + + return localVarHttpResponse, nil +} + +/* +EnvironmentsApiService Get Environment +This endpoint returns the metadata of an Environment identified by the `environmentId`. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param environmentId The identifier of the Environment. +@return EnvironmentModel +*/ +func (a *EnvironmentsApiService) GetEnvironment(ctx context.Context, environmentId string) (EnvironmentModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Get") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue EnvironmentModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/environments/{environmentId}" + localVarPath = strings.Replace(localVarPath, "{"+"environmentId"+"}", fmt.Sprintf("%v", environmentId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + if localVarHttpResponse.StatusCode >= 300 { newErr := GenericSwaggerError{ body: localVarBody, @@ -116,7 +269,7 @@ func (a *EnvironmentsApiService) CreateEnvironment(ctx context.Context, body Cre /* EnvironmentsApiService List Environments -This endpoint returns the list of the Environments that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. +This endpoint returns the list of the Environments that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param productId The identifier of the Product. @return []EnvironmentModel @@ -205,7 +358,7 @@ EnvironmentsApiService Update Environment This endpoint updates an Environment identified by the `environmentId` parameter. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param body - * @param environmentId The identifier of the Product. + * @param environmentId The identifier of the Environment. @return EnvironmentModel */ func (a *EnvironmentsApiService) UpdateEnvironment(ctx context.Context, body UpdateEnvironmentModel, environmentId string) (EnvironmentModel, *http.Response, error) { diff --git a/api_feature_flag_setting_values.go b/api_feature_flag_setting_values.go index 4fe0f1d..3e35b6a 100644 --- a/api_feature_flag_setting_values.go +++ b/api_feature_flag_setting_values.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -29,7 +29,7 @@ type FeatureFlagSettingValuesApiService service /* FeatureFlagSettingValuesApiService Get value -This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the `environmentId` parameter. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/). +This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the `environmentId` parameter. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/). * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param environmentId The identifier of the Environment. * @param settingId The id of the Setting. @@ -117,7 +117,7 @@ func (a *FeatureFlagSettingValuesApiService) GetSettingValue(ctx context.Context /* FeatureFlagSettingValuesApiService Replace value -This endpoint replaces the whole value of a Feature Flag or Setting in a specified Environment. 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 that it will reset. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send a replace request body as below: ``` { \"value\": true } ``` Then besides that the default value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ``` { \"rolloutPercentageItems\": [], \"rolloutRules\": [], \"value\": true } ``` +This endpoint replaces the whole value of a Feature Flag or Setting in a specified Environment. 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 that it will reset. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send a replace request body as below: ``` { \"value\": true } ``` Then besides that the default value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ``` { \"rolloutPercentageItems\": [], \"rolloutRules\": [], \"value\": true } ``` * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param body * @param environmentId The identifier of the Environment. @@ -218,7 +218,7 @@ func (a *FeatureFlagSettingValuesApiService) ReplaceSettingValue(ctx context.Con /* FeatureFlagSettingValuesApiService Update value -This endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Environment. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. 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. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/value\", \"value\": true } ] ``` Only the default value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": true } ``` +This endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Environment. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. 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. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/value\", \"value\": true } ] ``` Only the default value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": true } ``` * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param body * @param environmentId The identifier of the Environment. diff --git a/api_feature_flag_setting_values_using_sdk_key.go b/api_feature_flag_setting_values_using_sdk_key.go index ddf91de..b190ac7 100644 --- a/api_feature_flag_setting_values_using_sdk_key.go +++ b/api_feature_flag_setting_values_using_sdk_key.go @@ -1,8 +1,7 @@ - /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -12,11 +11,12 @@ package configcatpublicapi import ( "context" + "fmt" "io/ioutil" "net/http" "net/url" "strings" - "fmt" + "github.com/antihax/optional" ) @@ -26,9 +26,10 @@ var ( ) type FeatureFlagSettingValuesUsingSDKKeyApiService service + /* FeatureFlagSettingValuesUsingSDKKeyApiService Get value -This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://app.configcat.com/sdkkey\">SDK key</a> passed in the `X-CONFIGCAT-SDKKEY` header. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/). +This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://app.configcat.com/sdkkey\">SDK key</a> passed in the `X-CONFIGCAT-SDKKEY` header. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/). * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param settingKeyOrId The key or id of the Setting. * @param xCONFIGCATSDKKEY The ConfigCat SDK Key. (https://app.configcat.com/sdkkey) @@ -36,10 +37,10 @@ This endpoint returns the value of a Feature Flag or Setting in a specified Env */ func (a *FeatureFlagSettingValuesUsingSDKKeyApiService) GetSettingValueBySdkkey(ctx context.Context, settingKeyOrId string, xCONFIGCATSDKKEY string) (SettingValueModel, *http.Response, error) { var ( - localVarHttpMethod = strings.ToUpper("Get") - localVarPostBody interface{} - localVarFileName string - localVarFileBytes []byte + localVarHttpMethod = strings.ToUpper("Get") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte localVarReturnValue SettingValueModel ) @@ -87,35 +88,36 @@ func (a *FeatureFlagSettingValuesUsingSDKKeyApiService) GetSettingValueBySdkkey( if localVarHttpResponse.StatusCode < 300 { // If we succeed, return the data, otherwise pass on to decode error. - err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")); - if err == nil { + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { return localVarReturnValue, localVarHttpResponse, err } } if localVarHttpResponse.StatusCode >= 300 { newErr := GenericSwaggerError{ - body: localVarBody, + body: localVarBody, error: localVarHttpResponse.Status, } if localVarHttpResponse.StatusCode == 200 { var v SettingValueModel - err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")); - if err != nil { - newErr.error = err.Error() - return localVarReturnValue, localVarHttpResponse, newErr - } - newErr.model = v + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr } return localVarReturnValue, localVarHttpResponse, newErr } return localVarReturnValue, localVarHttpResponse, nil } + /* FeatureFlagSettingValuesUsingSDKKeyApiService Replace value -This endpoint replaces the value of a Feature Flag or Setting in a specified Environment identified by the <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://app.configcat.com/sdkkey\">SDK key</a> passed in the `X-CONFIGCAT-SDKKEY` header. 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 to its original state. Not listing one means that it will reset. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send a replace request body as below: ``` { \"value\": true } ``` Then besides that the default served value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ``` { \"rolloutPercentageItems\": [], \"rolloutRules\": [], \"value\": true } ``` +This endpoint replaces the value of a Feature Flag or Setting in a specified Environment identified by the <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://app.configcat.com/sdkkey\">SDK key</a> passed in the `X-CONFIGCAT-SDKKEY` header. 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 to its original state. Not listing one means that it will reset. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send a replace request body as below: ``` { \"value\": true } ``` Then besides that the default served value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ``` { \"rolloutPercentageItems\": [], \"rolloutRules\": [], \"value\": true } ``` * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param body * @param xCONFIGCATSDKKEY The ConfigCat SDK Key. (https://app.configcat.com/sdkkey) @@ -126,15 +128,15 @@ This endpoint replaces the value of a Feature Flag or Setting in a specified En */ type FeatureFlagSettingValuesUsingSDKKeyApiReplaceSettingValueBySdkkeyOpts struct { - Reason optional.String + Reason optional.String } func (a *FeatureFlagSettingValuesUsingSDKKeyApiService) ReplaceSettingValueBySdkkey(ctx context.Context, body UpdateSettingValueModel, xCONFIGCATSDKKEY string, settingKeyOrId string, localVarOptionals *FeatureFlagSettingValuesUsingSDKKeyApiReplaceSettingValueBySdkkeyOpts) (SettingValueModel, *http.Response, error) { var ( - localVarHttpMethod = strings.ToUpper("Put") - localVarPostBody interface{} - localVarFileName string - localVarFileBytes []byte + localVarHttpMethod = strings.ToUpper("Put") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte localVarReturnValue SettingValueModel ) @@ -187,35 +189,36 @@ func (a *FeatureFlagSettingValuesUsingSDKKeyApiService) ReplaceSettingValueBySdk if localVarHttpResponse.StatusCode < 300 { // If we succeed, return the data, otherwise pass on to decode error. - err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")); - if err == nil { + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { return localVarReturnValue, localVarHttpResponse, err } } if localVarHttpResponse.StatusCode >= 300 { newErr := GenericSwaggerError{ - body: localVarBody, + body: localVarBody, error: localVarHttpResponse.Status, } if localVarHttpResponse.StatusCode == 200 { var v SettingValueModel - err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")); - if err != nil { - newErr.error = err.Error() - return localVarReturnValue, localVarHttpResponse, newErr - } - newErr.model = v + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr } return localVarReturnValue, localVarHttpResponse, newErr } return localVarReturnValue, localVarHttpResponse, nil } + /* FeatureFlagSettingValuesUsingSDKKeyApiService Update value -This endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Environment identified by the <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://app.configcat.com/sdkkey\">SDK key</a> passed in the `X-CONFIGCAT-SDKKEY` header. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. 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. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/value\", \"value\": true } ] ``` Only the default served value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": true } ``` +This endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Environment identified by the <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://app.configcat.com/sdkkey\">SDK key</a> passed in the `X-CONFIGCAT-SDKKEY` header. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. 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. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/value\", \"value\": true } ] ``` Only the default served value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": true } ``` * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param body * @param xCONFIGCATSDKKEY The ConfigCat SDK Key. (https://app.configcat.com/sdkkey) @@ -226,15 +229,15 @@ This endpoint updates the value of a Feature Flag or Setting with a collection */ type FeatureFlagSettingValuesUsingSDKKeyApiUpdateSettingValueBySdkkeyOpts struct { - Reason optional.String + Reason optional.String } func (a *FeatureFlagSettingValuesUsingSDKKeyApiService) UpdateSettingValueBySdkkey(ctx context.Context, body []Operation, xCONFIGCATSDKKEY string, settingKeyOrId string, localVarOptionals *FeatureFlagSettingValuesUsingSDKKeyApiUpdateSettingValueBySdkkeyOpts) (SettingValueModel, *http.Response, error) { var ( - localVarHttpMethod = strings.ToUpper("Patch") - localVarPostBody interface{} - localVarFileName string - localVarFileBytes []byte + localVarHttpMethod = strings.ToUpper("Patch") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte localVarReturnValue SettingValueModel ) @@ -287,26 +290,26 @@ func (a *FeatureFlagSettingValuesUsingSDKKeyApiService) UpdateSettingValueBySdkk if localVarHttpResponse.StatusCode < 300 { // If we succeed, return the data, otherwise pass on to decode error. - err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")); - if err == nil { + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { return localVarReturnValue, localVarHttpResponse, err } } if localVarHttpResponse.StatusCode >= 300 { newErr := GenericSwaggerError{ - body: localVarBody, + body: localVarBody, error: localVarHttpResponse.Status, } if localVarHttpResponse.StatusCode == 200 { var v SettingValueModel - err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")); - if err != nil { - newErr.error = err.Error() - return localVarReturnValue, localVarHttpResponse, newErr - } - newErr.model = v + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr } return localVarReturnValue, localVarHttpResponse, newErr } diff --git a/api_feature_flags_settings.go b/api_feature_flags_settings.go index 4b71fa1..90c82ad 100644 --- a/api_feature_flags_settings.go +++ b/api_feature_flags_settings.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -27,7 +27,7 @@ type FeatureFlagsSettingsApiService service /* FeatureFlagsSettingsApiService Create Flag -This endpoint creates a new Feature Flag or Setting in a specified Config identified by the `configId` parameter. **Important:** The `key` attribute must be unique within the given Config. +This endpoint creates a new Feature Flag or Setting in a specified Config identified by the `configId` parameter. **Important:** The `key` attribute must be unique within the given Config. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param body * @param configId The identifier of the Config. @@ -116,7 +116,7 @@ func (a *FeatureFlagsSettingsApiService) CreateSetting(ctx context.Context, body /* FeatureFlagsSettingsApiService Delete Flag -This endpoint removes a Feature Flag or Setting from a specified Config, identified by the `configId` parameter. +This endpoint removes a Feature Flag or Setting from a specified Config, identified by the `configId` parameter. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param settingId The identifier of the Setting. @@ -183,7 +183,7 @@ func (a *FeatureFlagsSettingsApiService) DeleteSetting(ctx context.Context, sett /* FeatureFlagsSettingsApiService Get Flag -This endpoint returns the metadata attributes of a Feature Flag or Setting identified by the `settingId` parameter. +This endpoint returns the metadata attributes of a Feature Flag or Setting identified by the `settingId` parameter. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param settingId The identifier of the Setting. @return SettingModel @@ -269,7 +269,7 @@ func (a *FeatureFlagsSettingsApiService) GetSetting(ctx context.Context, setting /* FeatureFlagsSettingsApiService List Flags -This endpoint returns the list of the Feature Flags and Settings defined in a specified Config, identified by the `configId` parameter. +This endpoint returns the list of the Feature Flags and Settings defined in a specified Config, identified by the `configId` parameter. * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param configId The identifier of the Config. @return []SettingModel @@ -355,7 +355,7 @@ func (a *FeatureFlagsSettingsApiService) GetSettings(ctx context.Context, config /* FeatureFlagsSettingsApiService Update Flag -This endpoint updates the metadata of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Config. Only the `name` and `hint` attributes are modifiable by this endpoint. 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. ``` { \"settingId\": 5345, \"key\": \"myAwesomeFeature\", \"name\": \"Tihs is a naem with soem typos.\", \"hint\": \"This Flag controls my awesome feature.\", \"settingType\": \"boolean\" } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/name\", \"value\": \"This is the name without typos.\" } ] ``` Only the name is going to be updated and all the other attributes are remaining unchanged. So we get a response like this: ``` { \"settingId\": 5345, \"key\": \"myAwesomeFeature\", \"name\": \"This is the name without typos.\", \"hint\": \"This Flag controls my awesome feature.\", \"settingType\": \"boolean\" } ``` +This endpoint updates the metadata of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Config. Only the `name` and `hint` attributes are modifiable by this endpoint. 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. ``` { \"settingId\": 5345, \"key\": \"myAwesomeFeature\", \"name\": \"Tihs is a naem with soem typos.\", \"hint\": \"This Flag controls my awesome feature.\", \"settingType\": \"boolean\" } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/name\", \"value\": \"This is the name without typos.\" } ] ``` Only the name is going to be updated and all the other attributes are remaining unchanged. So we get a response like this: ``` { \"settingId\": 5345, \"key\": \"myAwesomeFeature\", \"name\": \"This is the name without typos.\", \"hint\": \"This Flag controls my awesome feature.\", \"settingType\": \"boolean\" } ``` * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). * @param body * @param settingId The identifier of the Setting. diff --git a/api_integration_links.go b/api_integration_links.go index 070241e..b123a38 100644 --- a/api_integration_links.go +++ b/api_integration_links.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/api_me.go b/api_me.go index f1398f0..dc1021f 100644 --- a/api_me.go +++ b/api_me.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/api_organizations.go b/api_organizations.go new file mode 100644 index 0000000..341b48d --- /dev/null +++ b/api_organizations.go @@ -0,0 +1,109 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +import ( + "context" + "io/ioutil" + "net/http" + "net/url" + "strings" +) + +// Linger please +var ( + _ context.Context +) + +type OrganizationsApiService service + +/* +OrganizationsApiService List Organizations +This endpoint returns the list of the Organizations that belongs to the user. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). +@return []OrganizationModel +*/ +func (a *OrganizationsApiService) GetOrganizations(ctx context.Context) ([]OrganizationModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Get") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue []OrganizationModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/organizations" + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 200 { + var v []OrganizationModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} diff --git a/api_products.go b/api_products.go index f5ba073..a6f0bae 100644 --- a/api_products.go +++ b/api_products.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -11,6 +11,7 @@ package configcatpublicapi import ( "context" + "fmt" "io/ioutil" "net/http" "net/url" @@ -24,6 +25,248 @@ var ( type ProductsApiService service +/* +ProductsApiService Create Product +This endpoint creates a new Product in a specified Organization identified by the `organizationId` parameter, which can be obtained from the [List Organizations](#operation/get-organizations) endpoint. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param body + * @param organizationId The identifier of the Organization. +@return ProductModel +*/ +func (a *ProductsApiService) CreateProduct(ctx context.Context, body CreateProductRequest, organizationId string) (ProductModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Post") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue ProductModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/organizations/{organizationId}/products" + localVarPath = strings.Replace(localVarPath, "{"+"organizationId"+"}", fmt.Sprintf("%v", organizationId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{"application/json", "text/json", "application/_*+json"} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + // body params + localVarPostBody = &body + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 201 { + var v ProductModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} + +/* +ProductsApiService Delete Product +This endpoint removes a Product identified by the `productId` parameter. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param productId The identifier of the Product. + +*/ +func (a *ProductsApiService) DeleteProduct(ctx context.Context, productId string) (*http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Delete") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/products/{productId}" + localVarPath = strings.Replace(localVarPath, "{"+"productId"+"}", fmt.Sprintf("%v", productId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + return localVarHttpResponse, newErr + } + + return localVarHttpResponse, nil +} + +/* +ProductsApiService Get Product +This endpoint returns the metadata of a Product identified by the `productId`. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param productId The identifier of the Product. +@return ProductModel +*/ +func (a *ProductsApiService) GetProduct(ctx context.Context, productId string) (ProductModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Get") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue ProductModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/products/{productId}" + localVarPath = strings.Replace(localVarPath, "{"+"productId"+"}", fmt.Sprintf("%v", productId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 200 { + var v ProductModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} + /* ProductsApiService List Products This endpoint returns the list of the Products that belongs to the user. @@ -107,3 +350,92 @@ func (a *ProductsApiService) GetProducts(ctx context.Context) ([]ProductModel, * return localVarReturnValue, localVarHttpResponse, nil } + +/* +ProductsApiService Update Product +This endpoint updates a Product identified by the `productId` parameter. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param body + * @param productId The identifier of the Product. +@return ProductModel +*/ +func (a *ProductsApiService) UpdateProduct(ctx context.Context, body UpdateProductRequest, productId string) (ProductModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Put") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue ProductModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/products/{productId}" + localVarPath = strings.Replace(localVarPath, "{"+"productId"+"}", fmt.Sprintf("%v", productId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{"application/json", "text/json", "application/_*+json"} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + // body params + localVarPostBody = &body + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 200 { + var v ProductModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} diff --git a/api_tags.go b/api_tags.go new file mode 100644 index 0000000..2873da4 --- /dev/null +++ b/api_tags.go @@ -0,0 +1,443 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +import ( + "context" + "fmt" + "io/ioutil" + "net/http" + "net/url" + "strings" +) + +// Linger please +var ( + _ context.Context +) + +type TagsApiService service + +/* +TagsApiService Create Tag +This endpoint creates a new Tag in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param body + * @param productId The identifier of the Organization. +@return TagModel +*/ +func (a *TagsApiService) CreateTag(ctx context.Context, body CreateTagModel, productId string) (TagModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Post") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue TagModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/products/{productId}/tags" + localVarPath = strings.Replace(localVarPath, "{"+"productId"+"}", fmt.Sprintf("%v", productId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{"application/json", "text/json", "application/_*+json"} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + // body params + localVarPostBody = &body + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 201 { + var v TagModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} + +/* +TagsApiService Delete Tag +This endpoint removes a Tag identified by the `tagId` parameter. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param tagId The identifier of the Tag. + +*/ +func (a *TagsApiService) DeleteTag(ctx context.Context, tagId int64) (*http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Delete") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/tags/{tagId}" + localVarPath = strings.Replace(localVarPath, "{"+"tagId"+"}", fmt.Sprintf("%v", tagId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + return localVarHttpResponse, newErr + } + + return localVarHttpResponse, nil +} + +/* +TagsApiService Get Tag +This endpoint returns the metadata of a Tag identified by the `tagId`. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param tagId The identifier of the Tag. +@return TagModel +*/ +func (a *TagsApiService) GetTag(ctx context.Context, tagId int64) (TagModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Get") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue TagModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/tags/{tagId}" + localVarPath = strings.Replace(localVarPath, "{"+"tagId"+"}", fmt.Sprintf("%v", tagId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 200 { + var v TagModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} + +/* +TagsApiService List Tags +This endpoint returns the list of the Tags in a specified Product, identified by the `productId` parameter. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param productId The identifier of the Product. +@return []TagModel +*/ +func (a *TagsApiService) GetTags(ctx context.Context, productId string) ([]TagModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Get") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue []TagModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/products/{productId}/tags" + localVarPath = strings.Replace(localVarPath, "{"+"productId"+"}", fmt.Sprintf("%v", productId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 200 { + var v []TagModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} + +/* +TagsApiService Update Tag +This endpoint updates a Tag identified by the `tagId` parameter. + * @param ctx context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background(). + * @param body + * @param tagId The identifier of the Tag. +@return TagModel +*/ +func (a *TagsApiService) UpdateTag(ctx context.Context, body UpdateTagModel, tagId int64) (TagModel, *http.Response, error) { + var ( + localVarHttpMethod = strings.ToUpper("Put") + localVarPostBody interface{} + localVarFileName string + localVarFileBytes []byte + localVarReturnValue TagModel + ) + + // create path and map variables + localVarPath := a.client.cfg.BasePath + "/v1/tags/{tagId}" + localVarPath = strings.Replace(localVarPath, "{"+"tagId"+"}", fmt.Sprintf("%v", tagId), -1) + + localVarHeaderParams := make(map[string]string) + localVarQueryParams := url.Values{} + localVarFormParams := url.Values{} + + // to determine the Content-Type header + localVarHttpContentTypes := []string{"application/json", "text/json", "application/_*+json"} + + // set Content-Type header + localVarHttpContentType := selectHeaderContentType(localVarHttpContentTypes) + if localVarHttpContentType != "" { + localVarHeaderParams["Content-Type"] = localVarHttpContentType + } + + // to determine the Accept header + localVarHttpHeaderAccepts := []string{"application/json", "application/hal+json"} + + // set Accept header + localVarHttpHeaderAccept := selectHeaderAccept(localVarHttpHeaderAccepts) + if localVarHttpHeaderAccept != "" { + localVarHeaderParams["Accept"] = localVarHttpHeaderAccept + } + // body params + localVarPostBody = &body + r, err := a.client.prepareRequest(ctx, localVarPath, localVarHttpMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFileName, localVarFileBytes) + if err != nil { + return localVarReturnValue, nil, err + } + + localVarHttpResponse, err := a.client.callAPI(r) + if err != nil || localVarHttpResponse == nil { + return localVarReturnValue, localVarHttpResponse, err + } + + localVarBody, err := ioutil.ReadAll(localVarHttpResponse.Body) + localVarHttpResponse.Body.Close() + if err != nil { + return localVarReturnValue, localVarHttpResponse, err + } + + if localVarHttpResponse.StatusCode < 300 { + // If we succeed, return the data, otherwise pass on to decode error. + err = a.client.decode(&localVarReturnValue, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err == nil { + return localVarReturnValue, localVarHttpResponse, err + } + } + + if localVarHttpResponse.StatusCode >= 300 { + newErr := GenericSwaggerError{ + body: localVarBody, + error: localVarHttpResponse.Status, + } + if localVarHttpResponse.StatusCode == 200 { + var v TagModel + err = a.client.decode(&v, localVarBody, localVarHttpResponse.Header.Get("Content-Type")) + if err != nil { + newErr.error = err.Error() + return localVarReturnValue, localVarHttpResponse, newErr + } + newErr.model = v + return localVarReturnValue, localVarHttpResponse, newErr + } + return localVarReturnValue, localVarHttpResponse, newErr + } + + return localVarReturnValue, localVarHttpResponse, nil +} diff --git a/client.go b/client.go index c1400f2..ca6df24 100644 --- a/client.go +++ b/client.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -61,7 +61,11 @@ type APIClient struct { MeApi *MeApiService + OrganizationsApi *OrganizationsApiService + ProductsApi *ProductsApiService + + TagsApi *TagsApiService } type service struct { @@ -88,7 +92,9 @@ func NewAPIClient(cfg *Configuration) *APIClient { c.FeatureFlagsSettingsApi = (*FeatureFlagsSettingsApiService)(&c.common) c.IntegrationLinksApi = (*IntegrationLinksApiService)(&c.common) c.MeApi = (*MeApiService)(&c.common) + c.OrganizationsApi = (*OrganizationsApiService)(&c.common) c.ProductsApi = (*ProductsApiService)(&c.common) + c.TagsApi = (*TagsApiService)(&c.common) return c } diff --git a/configuration.go b/configuration.go index da01971..b0ef15d 100644 --- a/configuration.go +++ b/configuration.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -60,7 +60,7 @@ type Configuration struct { func NewConfiguration() *Configuration { cfg := &Configuration{ - BasePath: "https://api.configcat.com", + BasePath: "https://localhost", DefaultHeader: make(map[string]string), UserAgent: "Swagger-Codegen/1.0.0/go", } diff --git a/docs/AuditLogsApi.md b/docs/AuditLogsApi.md index 88bbfa6..23dbcea 100644 --- a/docs/AuditLogsApi.md +++ b/docs/AuditLogsApi.md @@ -1,6 +1,6 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- @@ -10,7 +10,7 @@ Method | HTTP request | Description > []AuditLogItemModel GetAuditlogs(ctx, productId, optional) List Audit logs -This endpoint returns the list of Audit logs for a given Product and the result can be optionally filtered by Config and/or Environment. +This endpoint returns the list of Audit logs for a given Product and the result can be optionally filtered by Config and/or Environment. ### Required Parameters diff --git a/docs/ConfigModelhaljsonLinks.md b/docs/ConfigModelhaljsonLinks.md index 0d5b9b8..65a231e 100644 --- a/docs/ConfigModelhaljsonLinks.md +++ b/docs/ConfigModelhaljsonLinks.md @@ -3,6 +3,7 @@ ## Properties Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- +**Self** | **string** | | [optional] [default to null] **Settings** | **string** | | [optional] [default to null] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/docs/ConfigsApi.md b/docs/ConfigsApi.md index e394f30..7ea34ff 100644 --- a/docs/ConfigsApi.md +++ b/docs/ConfigsApi.md @@ -1,16 +1,105 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- +[**CreateConfig**](ConfigsApi.md#CreateConfig) | **Post** /v1/products/{productId}/configs | Create Config +[**DeleteConfig**](ConfigsApi.md#DeleteConfig) | **Delete** /v1/configs/{configId} | Delete Config +[**GetConfig**](ConfigsApi.md#GetConfig) | **Get** /v1/configs/{configId} | Get Config [**GetConfigs**](ConfigsApi.md#GetConfigs) | **Get** /v1/products/{productId}/configs | List Configs +[**UpdateConfig**](ConfigsApi.md#UpdateConfig) | **Put** /v1/configs/{configId} | Update Config + +# **CreateConfig** +> ConfigModel CreateConfig(ctx, body, productId) +Create Config + +This endpoint creates a new Config in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **body** | [**CreateConfigRequest**](CreateConfigRequest.md)| | + **productId** | [**string**](.md)| The identifier of the Product. | + +### Return type + +[**ConfigModel**](ConfigModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: application/json, text/json, application/_*+json + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **DeleteConfig** +> DeleteConfig(ctx, configId) +Delete Config + +This endpoint removes a Config identified by the `configId` parameter. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **configId** | [**string**](.md)| The identifier of the Config. | + +### Return type + + (empty response body) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: Not defined + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **GetConfig** +> ConfigModel GetConfig(ctx, configId) +Get Config + +This endpoint returns the metadata of a Config identified by the `configId`. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **configId** | [**string**](.md)| The identifier of the Config. | + +### Return type + +[**ConfigModel**](ConfigModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) # **GetConfigs** > []ConfigModel GetConfigs(ctx, productId) List Configs -This endpoint returns the list of the Configs that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. +This endpoint returns the list of the Configs that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. ### Required Parameters @@ -34,3 +123,32 @@ Name | Type | Description | Notes [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) +# **UpdateConfig** +> ConfigModel UpdateConfig(ctx, body, configId) +Update Config + +This endpoint updates a Config identified by the `configId` parameter. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **body** | [**UpdateConfigRequest**](UpdateConfigRequest.md)| | + **configId** | [**string**](.md)| The identifier of the Config. | + +### Return type + +[**ConfigModel**](ConfigModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: application/json, text/json, application/_*+json + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + diff --git a/docs/CreateConfigRequest.md b/docs/CreateConfigRequest.md new file mode 100644 index 0000000..91e0f94 --- /dev/null +++ b/docs/CreateConfigRequest.md @@ -0,0 +1,9 @@ +# CreateConfigRequest + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Name** | **string** | | [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/CreateProductRequest.md b/docs/CreateProductRequest.md new file mode 100644 index 0000000..06395eb --- /dev/null +++ b/docs/CreateProductRequest.md @@ -0,0 +1,9 @@ +# CreateProductRequest + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Name** | **string** | | [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/CreateSettingModel.md b/docs/CreateSettingModel.md index be131d1..872cf31 100644 --- a/docs/CreateSettingModel.md +++ b/docs/CreateSettingModel.md @@ -7,6 +7,7 @@ Name | Type | Description | Notes **Name** | **string** | The name of the setting, shown on the Dashboard UI. | [default to null] **SettingType** | [***SettingType**](SettingType.md) | | [default to null] **Hint** | **string** | A short description for the setting, shown on the Dashboard UI. | [optional] [default to null] +**Tags** | [**[]TagModel**](TagModel.md) | The tags attached to the setting. | [optional] [default to null] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/docs/CreateTagModel.md b/docs/CreateTagModel.md new file mode 100644 index 0000000..f147aa6 --- /dev/null +++ b/docs/CreateTagModel.md @@ -0,0 +1,10 @@ +# CreateTagModel + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Name** | **string** | | [default to null] +**Color** | **string** | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/EnvironmentModelHaljson.md b/docs/EnvironmentModelHaljson.md new file mode 100644 index 0000000..caf62b8 --- /dev/null +++ b/docs/EnvironmentModelHaljson.md @@ -0,0 +1,11 @@ +# EnvironmentModelHaljson + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**EnvironmentId** | **string** | | [optional] [default to null] +**Name** | **string** | | [optional] [default to null] +**Links** | [***EnvironmentModelhaljsonLinks**](EnvironmentModelhaljson__links.md) | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/EnvironmentModelhaljsonLinks.md b/docs/EnvironmentModelhaljsonLinks.md new file mode 100644 index 0000000..380b3c4 --- /dev/null +++ b/docs/EnvironmentModelhaljsonLinks.md @@ -0,0 +1,9 @@ +# EnvironmentModelhaljsonLinks + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Self** | **string** | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/EnvironmentsApi.md b/docs/EnvironmentsApi.md index 6431283..5da0618 100644 --- a/docs/EnvironmentsApi.md +++ b/docs/EnvironmentsApi.md @@ -1,10 +1,12 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- [**CreateEnvironment**](EnvironmentsApi.md#CreateEnvironment) | **Post** /v1/products/{productId}/environments | Create Environment +[**DeleteEnvironment**](EnvironmentsApi.md#DeleteEnvironment) | **Delete** /v1/environments/{environmentId} | Delete Environment +[**GetEnvironment**](EnvironmentsApi.md#GetEnvironment) | **Get** /v1/environments/{environmentId} | Get Environment [**GetEnvironments**](EnvironmentsApi.md#GetEnvironments) | **Get** /v1/products/{productId}/environments | List Environments [**UpdateEnvironment**](EnvironmentsApi.md#UpdateEnvironment) | **Put** /v1/environments/{environmentId} | Update Environment @@ -12,7 +14,7 @@ Method | HTTP request | Description > EnvironmentModel CreateEnvironment(ctx, body, productId) Create Environment -This endpoint creates a new Environment in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. +This endpoint creates a new Environment in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. ### Required Parameters @@ -37,11 +39,67 @@ Name | Type | Description | Notes [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) +# **DeleteEnvironment** +> DeleteEnvironment(ctx, environmentId) +Delete Environment + +This endpoint removes an Environment identified by the `environmentId` parameter. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **environmentId** | [**string**](.md)| The identifier of the Environment. | + +### Return type + + (empty response body) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: Not defined + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **GetEnvironment** +> EnvironmentModel GetEnvironment(ctx, environmentId) +Get Environment + +This endpoint returns the metadata of an Environment identified by the `environmentId`. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **environmentId** | [**string**](.md)| The identifier of the Environment. | + +### Return type + +[**EnvironmentModel**](EnvironmentModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + # **GetEnvironments** > []EnvironmentModel GetEnvironments(ctx, productId) List Environments -This endpoint returns the list of the Environments that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. +This endpoint returns the list of the Environments that belongs to the given Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. ### Required Parameters @@ -77,7 +135,7 @@ Name | Type | Description | Notes ------------- | ------------- | ------------- | ------------- **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. **body** | [**UpdateEnvironmentModel**](UpdateEnvironmentModel.md)| | - **environmentId** | [**string**](.md)| The identifier of the Product. | + **environmentId** | [**string**](.md)| The identifier of the Environment. | ### Return type diff --git a/docs/FeatureFlagSettingValuesApi.md b/docs/FeatureFlagSettingValuesApi.md index 3ce7bdf..6939e1f 100644 --- a/docs/FeatureFlagSettingValuesApi.md +++ b/docs/FeatureFlagSettingValuesApi.md @@ -1,6 +1,6 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- @@ -12,7 +12,7 @@ Method | HTTP request | Description > SettingValueModel GetSettingValue(ctx, environmentId, settingId) Get value -This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the `environmentId` parameter. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/). +This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the `environmentId` parameter. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/). ### Required Parameters @@ -41,7 +41,7 @@ Name | Type | Description | Notes > SettingValueModel ReplaceSettingValue(ctx, body, environmentId, settingId, optional) Replace value -This endpoint replaces the whole value of a Feature Flag or Setting in a specified Environment. 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 that it will reset. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send a replace request body as below: ``` { \"value\": true } ``` Then besides that the default value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ``` { \"rolloutPercentageItems\": [], \"rolloutRules\": [], \"value\": true } ``` +This endpoint replaces the whole value of a Feature Flag or Setting in a specified Environment. 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 that it will reset. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send a replace request body as below: ``` { \"value\": true } ``` Then besides that the default value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ``` { \"rolloutPercentageItems\": [], \"rolloutRules\": [], \"value\": true } ``` ### Required Parameters @@ -81,7 +81,7 @@ Name | Type | Description | Notes > SettingValueModel UpdateSettingValue(ctx, body, environmentId, settingId, optional) Update value -This endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Environment. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. 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. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/value\", \"value\": true } ] ``` Only the default value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": true } ``` +This endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Environment. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. 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. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/value\", \"value\": true } ] ``` Only the default value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": true } ``` ### Required Parameters diff --git a/docs/FeatureFlagSettingValuesUsingSDKKeyApi.md b/docs/FeatureFlagSettingValuesUsingSDKKeyApi.md index c1ba3fb..820a674 100644 --- a/docs/FeatureFlagSettingValuesUsingSDKKeyApi.md +++ b/docs/FeatureFlagSettingValuesUsingSDKKeyApi.md @@ -1,6 +1,6 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- @@ -12,7 +12,7 @@ Method | HTTP request | Description > SettingValueModel GetSettingValueBySdkkey(ctx, settingKeyOrId, xCONFIGCATSDKKEY) Get value -This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the SDK key passed in the `X-CONFIGCAT-SDKKEY` header. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/). +This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the SDK key passed in the `X-CONFIGCAT-SDKKEY` header. The most important attributes in the response are the `value`, `rolloutRules` and `percentageRules`. The `value` represents what the clients will get when the evaluation requests of our SDKs are not matching to any of the defined Targeting or Percentage Rules, or when there are no additional rules to evaluate. The `rolloutRules` and `percentageRules` attributes are representing the current Targeting and Percentage Rules configuration of the actual Feature Flag or Setting in an **ordered** collection, which means the order of the returned rules is matching to the evaluation order. You can read more about these rules [here](https://configcat.com/docs/advanced/targeting/). ### Required Parameters @@ -41,7 +41,7 @@ Name | Type | Description | Notes > SettingValueModel ReplaceSettingValueBySdkkey(ctx, body, settingKeyOrId, xCONFIGCATSDKKEY, optional) Replace value -This endpoint replaces the value of a Feature Flag or Setting in a specified Environment identified by the SDK key passed in the `X-CONFIGCAT-SDKKEY` header. 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 to its original state. Not listing one means that it will reset. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send a replace request body as below: ``` { \"value\": true } ``` Then besides that the default served value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ``` { \"rolloutPercentageItems\": [], \"rolloutRules\": [], \"value\": true } ``` +This endpoint replaces the value of a Feature Flag or Setting in a specified Environment identified by the SDK key passed in the `X-CONFIGCAT-SDKKEY` header. 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 to its original state. Not listing one means that it will reset. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send a replace request body as below: ``` { \"value\": true } ``` Then besides that the default served value is set to `true`, all the Percentage Rules are deleted. So we get a response like this: ``` { \"rolloutPercentageItems\": [], \"rolloutRules\": [], \"value\": true } ``` ### Required Parameters @@ -81,7 +81,7 @@ Name | Type | Description | Notes > SettingValueModel UpdateSettingValueBySdkkey(ctx, body, settingKeyOrId, xCONFIGCATSDKKEY, optional) Update value -This endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Environment identified by the SDK key passed in the `X-CONFIGCAT-SDKKEY` header. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. 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. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/value\", \"value\": true } ] ``` Only the default served value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": true } ``` +This endpoint updates the value of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Environment identified by the SDK key passed in the `X-CONFIGCAT-SDKKEY` header. Only the `value`, `rolloutRules` and `percentageRules` attributes are modifiable by this endpoint. 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. It supports collection reordering, so it also can be used for reordering the targeting rules of a Feature Flag or Setting. For example: We have the following resource. ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": false } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/value\", \"value\": true } ] ``` Only the default served value is going to be set to `true` and all the Percentage Rules are remaining unchanged. So we get a response like this: ``` { \"rolloutPercentageItems\": [ { \"percentage\": 30, \"value\": true }, { \"percentage\": 70, \"value\": false } ], \"rolloutRules\": [], \"value\": true } ``` ### Required Parameters diff --git a/docs/FeatureFlagsSettingsApi.md b/docs/FeatureFlagsSettingsApi.md index f7c549d..323a60d 100644 --- a/docs/FeatureFlagsSettingsApi.md +++ b/docs/FeatureFlagsSettingsApi.md @@ -1,6 +1,6 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- @@ -14,7 +14,7 @@ Method | HTTP request | Description > SettingModel CreateSetting(ctx, body, configId) Create Flag -This endpoint creates a new Feature Flag or Setting in a specified Config identified by the `configId` parameter. **Important:** The `key` attribute must be unique within the given Config. +This endpoint creates a new Feature Flag or Setting in a specified Config identified by the `configId` parameter. **Important:** The `key` attribute must be unique within the given Config. ### Required Parameters @@ -43,7 +43,7 @@ Name | Type | Description | Notes > DeleteSetting(ctx, settingId) Delete Flag -This endpoint removes a Feature Flag or Setting from a specified Config, identified by the `configId` parameter. +This endpoint removes a Feature Flag or Setting from a specified Config, identified by the `configId` parameter. ### Required Parameters @@ -71,7 +71,7 @@ Name | Type | Description | Notes > SettingModel GetSetting(ctx, settingId) Get Flag -This endpoint returns the metadata attributes of a Feature Flag or Setting identified by the `settingId` parameter. +This endpoint returns the metadata attributes of a Feature Flag or Setting identified by the `settingId` parameter. ### Required Parameters @@ -99,7 +99,7 @@ Name | Type | Description | Notes > []SettingModel GetSettings(ctx, configId) List Flags -This endpoint returns the list of the Feature Flags and Settings defined in a specified Config, identified by the `configId` parameter. +This endpoint returns the list of the Feature Flags and Settings defined in a specified Config, identified by the `configId` parameter. ### Required Parameters @@ -127,7 +127,7 @@ Name | Type | Description | Notes > SettingModel UpdateSetting(ctx, body, settingId) Update Flag -This endpoint updates the metadata of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Config. Only the `name` and `hint` attributes are modifiable by this endpoint. 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. ``` { \"settingId\": 5345, \"key\": \"myAwesomeFeature\", \"name\": \"Tihs is a naem with soem typos.\", \"hint\": \"This Flag controls my awesome feature.\", \"settingType\": \"boolean\" } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/name\", \"value\": \"This is the name without typos.\" } ] ``` Only the name is going to be updated and all the other attributes are remaining unchanged. So we get a response like this: ``` { \"settingId\": 5345, \"key\": \"myAwesomeFeature\", \"name\": \"This is the name without typos.\", \"hint\": \"This Flag controls my awesome feature.\", \"settingType\": \"boolean\" } ``` +This endpoint updates the metadata of a Feature Flag or Setting with a collection of [JSON Patch](http://jsonpatch.com) operations in a specified Config. Only the `name` and `hint` attributes are modifiable by this endpoint. 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. ``` { \"settingId\": 5345, \"key\": \"myAwesomeFeature\", \"name\": \"Tihs is a naem with soem typos.\", \"hint\": \"This Flag controls my awesome feature.\", \"settingType\": \"boolean\" } ``` If we send an update request body as below: ``` [ { \"op\": \"replace\", \"path\": \"/name\", \"value\": \"This is the name without typos.\" } ] ``` Only the name is going to be updated and all the other attributes are remaining unchanged. So we get a response like this: ``` { \"settingId\": 5345, \"key\": \"myAwesomeFeature\", \"name\": \"This is the name without typos.\", \"hint\": \"This Flag controls my awesome feature.\", \"settingType\": \"boolean\" } ``` ### Required Parameters diff --git a/docs/IntegrationLinksApi.md b/docs/IntegrationLinksApi.md index fbdca48..31ae666 100644 --- a/docs/IntegrationLinksApi.md +++ b/docs/IntegrationLinksApi.md @@ -1,6 +1,6 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- diff --git a/docs/MeApi.md b/docs/MeApi.md index d82c5cd..04f64af 100644 --- a/docs/MeApi.md +++ b/docs/MeApi.md @@ -1,6 +1,6 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- diff --git a/docs/OrganizationModelHaljson.md b/docs/OrganizationModelHaljson.md new file mode 100644 index 0000000..18b30cc --- /dev/null +++ b/docs/OrganizationModelHaljson.md @@ -0,0 +1,11 @@ +# OrganizationModelHaljson + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**OrganizationId** | **string** | | [optional] [default to null] +**Name** | **string** | | [optional] [default to null] +**Links** | [***OrganizationModelhaljsonLinks**](OrganizationModelhaljson__links.md) | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/OrganizationModelhaljsonLinks.md b/docs/OrganizationModelhaljsonLinks.md new file mode 100644 index 0000000..deeffd9 --- /dev/null +++ b/docs/OrganizationModelhaljsonLinks.md @@ -0,0 +1,9 @@ +# OrganizationModelhaljsonLinks + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Products** | **string** | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/OrganizationsApi.md b/docs/OrganizationsApi.md new file mode 100644 index 0000000..349002e --- /dev/null +++ b/docs/OrganizationsApi.md @@ -0,0 +1,32 @@ +# {{classname}} + +All URIs are relative to *https://localhost* + +Method | HTTP request | Description +------------- | ------------- | ------------- +[**GetOrganizations**](OrganizationsApi.md#GetOrganizations) | **Get** /v1/organizations | List Organizations + +# **GetOrganizations** +> []OrganizationModel GetOrganizations(ctx, ) +List Organizations + +This endpoint returns the list of the Organizations that belongs to the user. + +### Required Parameters +This endpoint does not need any parameter. + +### Return type + +[**[]OrganizationModel**](OrganizationModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + diff --git a/docs/ProductModelhaljsonEmbeddedOrganization.md b/docs/ProductModelhaljsonEmbeddedOrganization.md index c0622eb..d9964f6 100644 --- a/docs/ProductModelhaljsonEmbeddedOrganization.md +++ b/docs/ProductModelhaljsonEmbeddedOrganization.md @@ -5,6 +5,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **OrganizationId** | **string** | | [optional] [default to null] **Name** | **string** | | [optional] [default to null] +**Links** | [***OrganizationModelhaljsonLinks**](OrganizationModelhaljson__links.md) | | [optional] [default to null] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/docs/ProductModelhaljsonLinks.md b/docs/ProductModelhaljsonLinks.md index 8b0e913..9881387 100644 --- a/docs/ProductModelhaljsonLinks.md +++ b/docs/ProductModelhaljsonLinks.md @@ -3,8 +3,10 @@ ## Properties Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- +**Self** | **string** | | [optional] [default to null] **Configs** | **string** | | [optional] [default to null] **Environments** | **string** | | [optional] [default to null] +**Tags** | **string** | | [optional] [default to null] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/docs/ProductsApi.md b/docs/ProductsApi.md index d1bc08f..7590097 100644 --- a/docs/ProductsApi.md +++ b/docs/ProductsApi.md @@ -1,10 +1,99 @@ # {{classname}} -All URIs are relative to *https://api.configcat.com* +All URIs are relative to *https://localhost* Method | HTTP request | Description ------------- | ------------- | ------------- +[**CreateProduct**](ProductsApi.md#CreateProduct) | **Post** /v1/organizations/{organizationId}/products | Create Product +[**DeleteProduct**](ProductsApi.md#DeleteProduct) | **Delete** /v1/products/{productId} | Delete Product +[**GetProduct**](ProductsApi.md#GetProduct) | **Get** /v1/products/{productId} | Get Product [**GetProducts**](ProductsApi.md#GetProducts) | **Get** /v1/products | List Products +[**UpdateProduct**](ProductsApi.md#UpdateProduct) | **Put** /v1/products/{productId} | Update Product + +# **CreateProduct** +> ProductModel CreateProduct(ctx, body, organizationId) +Create Product + +This endpoint creates a new Product in a specified Organization identified by the `organizationId` parameter, which can be obtained from the [List Organizations](#operation/get-organizations) endpoint. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **body** | [**CreateProductRequest**](CreateProductRequest.md)| | + **organizationId** | [**string**](.md)| The identifier of the Organization. | + +### Return type + +[**ProductModel**](ProductModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: application/json, text/json, application/_*+json + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **DeleteProduct** +> DeleteProduct(ctx, productId) +Delete Product + +This endpoint removes a Product identified by the `productId` parameter. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **productId** | [**string**](.md)| The identifier of the Product. | + +### Return type + + (empty response body) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: Not defined + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **GetProduct** +> ProductModel GetProduct(ctx, productId) +Get Product + +This endpoint returns the metadata of a Product identified by the `productId`. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **productId** | [**string**](.md)| The identifier of the Product. | + +### Return type + +[**ProductModel**](ProductModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) # **GetProducts** > []ProductModel GetProducts(ctx, ) @@ -30,3 +119,32 @@ This endpoint does not need any parameter. [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) +# **UpdateProduct** +> ProductModel UpdateProduct(ctx, body, productId) +Update Product + +This endpoint updates a Product identified by the `productId` parameter. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **body** | [**UpdateProductRequest**](UpdateProductRequest.md)| | + **productId** | [**string**](.md)| The identifier of the Product. | + +### Return type + +[**ProductModel**](ProductModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: application/json, text/json, application/_*+json + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + diff --git a/docs/SettingModel.md b/docs/SettingModel.md index 709c212..1609942 100644 --- a/docs/SettingModel.md +++ b/docs/SettingModel.md @@ -13,6 +13,7 @@ Name | Type | Description | Notes **ExpirationWarningAt** | [**time.Time**](time.Time.md) | | [optional] [default to null] **ConfigId** | **string** | | [optional] [default to null] **ConfigName** | **string** | | [optional] [default to null] +**Tags** | [**[]TagModel**](TagModel.md) | | [optional] [default to null] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/docs/SettingModelHaljson.md b/docs/SettingModelHaljson.md new file mode 100644 index 0000000..02bf900 --- /dev/null +++ b/docs/SettingModelHaljson.md @@ -0,0 +1,20 @@ +# SettingModelHaljson + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**SettingId** | **int32** | | [optional] [default to null] +**Key** | **string** | | [optional] [default to null] +**Name** | **string** | | [optional] [default to null] +**Hint** | **string** | | [optional] [default to null] +**SettingType** | [***SettingType**](SettingType.md) | | [optional] [default to null] +**OwnerUserEmail** | **string** | | [optional] [default to null] +**OwnerUserFullName** | **string** | | [optional] [default to null] +**ExpirationWarningAt** | [**time.Time**](time.Time.md) | | [optional] [default to null] +**ConfigId** | **string** | | [optional] [default to null] +**ConfigName** | **string** | | [optional] [default to null] +**Embedded** | [***SettingModelhaljsonEmbedded**](SettingModelhaljson__embedded.md) | | [optional] [default to null] +**Links** | [***EnvironmentModelhaljsonLinks**](EnvironmentModelhaljson__links.md) | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/SettingModelhaljsonEmbedded.md b/docs/SettingModelhaljsonEmbedded.md new file mode 100644 index 0000000..e72e79f --- /dev/null +++ b/docs/SettingModelhaljsonEmbedded.md @@ -0,0 +1,9 @@ +# SettingModelhaljsonEmbedded + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Tags** | [**[]SettingModelhaljsonEmbeddedTags**](SettingModelhaljson__embedded_tags.md) | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/SettingModelhaljsonEmbeddedTags.md b/docs/SettingModelhaljsonEmbeddedTags.md new file mode 100644 index 0000000..6d2aca7 --- /dev/null +++ b/docs/SettingModelhaljsonEmbeddedTags.md @@ -0,0 +1,12 @@ +# SettingModelhaljsonEmbeddedTags + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**TagId** | **int64** | | [optional] [default to null] +**Name** | **string** | | [optional] [default to null] +**Color** | **string** | | [optional] [default to null] +**Links** | [***EnvironmentModelhaljsonLinks**](EnvironmentModelhaljson__links.md) | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/SettingValueModelHaljson.md b/docs/SettingValueModelHaljson.md index 9a9701a..319a609 100644 --- a/docs/SettingValueModelHaljson.md +++ b/docs/SettingValueModelHaljson.md @@ -11,7 +11,7 @@ Name | Type | Description | Notes **RolloutRules** | [**[]RolloutRuleModel**](RolloutRuleModel.md) | The targeting rule collection. | [optional] [default to null] **RolloutPercentageItems** | [**[]RolloutPercentageItemModel**](RolloutPercentageItemModel.md) | The percentage rule collection. | [optional] [default to null] **Value** | [***interface{}**](interface{}.md) | The value to serve. It must respect the setting type. | [optional] [default to null] -**Links** | [***SettingValueModelhaljsonLinks**](SettingValueModelhaljson__links.md) | | [optional] [default to null] +**Links** | [***EnvironmentModelhaljsonLinks**](EnvironmentModelhaljson__links.md) | | [optional] [default to null] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/docs/SettingValueModelhaljsonEmbeddedEnvironment.md b/docs/SettingValueModelhaljsonEmbeddedEnvironment.md index c30e956..bbed2fb 100644 --- a/docs/SettingValueModelhaljsonEmbeddedEnvironment.md +++ b/docs/SettingValueModelhaljsonEmbeddedEnvironment.md @@ -5,6 +5,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **EnvironmentId** | **string** | | [optional] [default to null] **Name** | **string** | | [optional] [default to null] +**Links** | [***EnvironmentModelhaljsonLinks**](EnvironmentModelhaljson__links.md) | | [optional] [default to null] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/docs/TagModel.md b/docs/TagModel.md new file mode 100644 index 0000000..b85b16f --- /dev/null +++ b/docs/TagModel.md @@ -0,0 +1,11 @@ +# TagModel + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**TagId** | **int64** | | [optional] [default to null] +**Name** | **string** | | [optional] [default to null] +**Color** | **string** | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/TagModelHaljson.md b/docs/TagModelHaljson.md new file mode 100644 index 0000000..18e1b41 --- /dev/null +++ b/docs/TagModelHaljson.md @@ -0,0 +1,12 @@ +# TagModelHaljson + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**TagId** | **int64** | | [optional] [default to null] +**Name** | **string** | | [optional] [default to null] +**Color** | **string** | | [optional] [default to null] +**Links** | [***EnvironmentModelhaljsonLinks**](EnvironmentModelhaljson__links.md) | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/TagsApi.md b/docs/TagsApi.md new file mode 100644 index 0000000..11c0954 --- /dev/null +++ b/docs/TagsApi.md @@ -0,0 +1,154 @@ +# {{classname}} + +All URIs are relative to *https://localhost* + +Method | HTTP request | Description +------------- | ------------- | ------------- +[**CreateTag**](TagsApi.md#CreateTag) | **Post** /v1/products/{productId}/tags | Create Tag +[**DeleteTag**](TagsApi.md#DeleteTag) | **Delete** /v1/tags/{tagId} | Delete Tag +[**GetTag**](TagsApi.md#GetTag) | **Get** /v1/tags/{tagId} | Get Tag +[**GetTags**](TagsApi.md#GetTags) | **Get** /v1/products/{productId}/tags | List Tags +[**UpdateTag**](TagsApi.md#UpdateTag) | **Put** /v1/tags/{tagId} | Update Tag + +# **CreateTag** +> TagModel CreateTag(ctx, body, productId) +Create Tag + +This endpoint creates a new Tag in a specified Product identified by the `productId` parameter, which can be obtained from the [List Products](#operation/get-products) endpoint. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **body** | [**CreateTagModel**](CreateTagModel.md)| | + **productId** | [**string**](.md)| The identifier of the Organization. | + +### Return type + +[**TagModel**](TagModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: application/json, text/json, application/_*+json + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **DeleteTag** +> DeleteTag(ctx, tagId) +Delete Tag + +This endpoint removes a Tag identified by the `tagId` parameter. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **tagId** | **int64**| The identifier of the Tag. | + +### Return type + + (empty response body) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: Not defined + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **GetTag** +> TagModel GetTag(ctx, tagId) +Get Tag + +This endpoint returns the metadata of a Tag identified by the `tagId`. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **tagId** | **int64**| The identifier of the Tag. | + +### Return type + +[**TagModel**](TagModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **GetTags** +> []TagModel GetTags(ctx, productId) +List Tags + +This endpoint returns the list of the Tags in a specified Product, identified by the `productId` parameter. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **productId** | [**string**](.md)| The identifier of the Product. | + +### Return type + +[**[]TagModel**](TagModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **UpdateTag** +> TagModel UpdateTag(ctx, body, tagId) +Update Tag + +This endpoint updates a Tag identified by the `tagId` parameter. + +### Required Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc. + **body** | [**UpdateTagModel**](UpdateTagModel.md)| | + **tagId** | **int64**| The identifier of the Tag. | + +### Return type + +[**TagModel**](TagModel.md) + +### Authorization + +[Basic](../README.md#Basic) + +### HTTP request headers + + - **Content-Type**: application/json, text/json, application/_*+json + - **Accept**: application/json, application/hal+json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + diff --git a/docs/UpdateConfigRequest.md b/docs/UpdateConfigRequest.md new file mode 100644 index 0000000..36185c2 --- /dev/null +++ b/docs/UpdateConfigRequest.md @@ -0,0 +1,9 @@ +# UpdateConfigRequest + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Name** | **string** | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/UpdateProductRequest.md b/docs/UpdateProductRequest.md new file mode 100644 index 0000000..cacde78 --- /dev/null +++ b/docs/UpdateProductRequest.md @@ -0,0 +1,9 @@ +# UpdateProductRequest + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Name** | **string** | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/docs/UpdateTagModel.md b/docs/UpdateTagModel.md new file mode 100644 index 0000000..6ff3bc4 --- /dev/null +++ b/docs/UpdateTagModel.md @@ -0,0 +1,10 @@ +# UpdateTagModel + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**Name** | **string** | | [default to null] +**Color** | **string** | | [optional] [default to null] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + diff --git a/model_add_or_update_integration_link_model.go b/model_add_or_update_integration_link_model.go index 610e613..8d87d10 100644 --- a/model_add_or_update_integration_link_model.go +++ b/model_add_or_update_integration_link_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -11,5 +11,5 @@ package configcatpublicapi type AddOrUpdateIntegrationLinkModel struct { Description string `json:"description,omitempty"` - Url string `json:"url,omitempty"` + Url string `json:"url,omitempty"` } diff --git a/model_audit_log_item_model.go b/model_audit_log_item_model.go index 3e8fcd3..bc3cc50 100644 --- a/model_audit_log_item_model.go +++ b/model_audit_log_item_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_audit_log_type.go b/model_audit_log_type.go index 5a055f5..9cb3b87 100644 --- a/model_audit_log_type.go +++ b/model_audit_log_type.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_config_model.go b/model_config_model.go index 55c69d3..8118a38 100644 --- a/model_config_model.go +++ b/model_config_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_config_model_haljson.go b/model_config_model_haljson.go index 49e0cec..8d373b7 100644 --- a/model_config_model_haljson.go +++ b/model_config_model_haljson.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_config_modelhaljson__links.go b/model_config_modelhaljson__links.go index 11a9e2a..04964d8 100644 --- a/model_config_modelhaljson__links.go +++ b/model_config_modelhaljson__links.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -10,5 +10,6 @@ package configcatpublicapi type ConfigModelhaljsonLinks struct { + Self string `json:"self,omitempty"` Settings string `json:"settings,omitempty"` } diff --git a/model_create_config_request.go b/model_create_config_request.go new file mode 100644 index 0000000..7e52c3c --- /dev/null +++ b/model_create_config_request.go @@ -0,0 +1,14 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type CreateConfigRequest struct { + Name string `json:"name"` +} diff --git a/model_create_environment_model.go b/model_create_environment_model.go index a953e12..653eb8b 100644 --- a/model_create_environment_model.go +++ b/model_create_environment_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_create_product_request.go b/model_create_product_request.go new file mode 100644 index 0000000..22a15fc --- /dev/null +++ b/model_create_product_request.go @@ -0,0 +1,14 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type CreateProductRequest struct { + Name string `json:"name"` +} diff --git a/model_create_setting_model.go b/model_create_setting_model.go index 68114bf..96fb196 100644 --- a/model_create_setting_model.go +++ b/model_create_setting_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -17,4 +17,6 @@ type CreateSettingModel struct { SettingType *SettingType `json:"settingType"` // A short description for the setting, shown on the Dashboard UI. Hint string `json:"hint,omitempty"` + // The tags attached to the setting. + Tags []TagModel `json:"tags,omitempty"` } diff --git a/model_create_tag_model.go b/model_create_tag_model.go new file mode 100644 index 0000000..8847a37 --- /dev/null +++ b/model_create_tag_model.go @@ -0,0 +1,15 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type CreateTagModel struct { + Name string `json:"name"` + Color string `json:"color,omitempty"` +} diff --git a/model_delete_integration_link_model.go b/model_delete_integration_link_model.go index ee490ae..5b5a0d7 100644 --- a/model_delete_integration_link_model.go +++ b/model_delete_integration_link_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_environment_model.go b/model_environment_model.go index 652627d..4e45fff 100644 --- a/model_environment_model.go +++ b/model_environment_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_environment_model_haljson.go b/model_environment_model_haljson.go new file mode 100644 index 0000000..6f0f0b8 --- /dev/null +++ b/model_environment_model_haljson.go @@ -0,0 +1,16 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type EnvironmentModelHaljson struct { + EnvironmentId string `json:"environmentId,omitempty"` + Name string `json:"name,omitempty"` + Links *EnvironmentModelhaljsonLinks `json:"_links,omitempty"` +} diff --git a/model_environment_modelhaljson__links.go b/model_environment_modelhaljson__links.go new file mode 100644 index 0000000..e3718e2 --- /dev/null +++ b/model_environment_modelhaljson__links.go @@ -0,0 +1,14 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type EnvironmentModelhaljsonLinks struct { + Self string `json:"self,omitempty"` +} diff --git a/model_integration_link_detail.go b/model_integration_link_detail.go index 332eee0..3063ee1 100644 --- a/model_integration_link_detail.go +++ b/model_integration_link_detail.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_integration_link_details_model.go b/model_integration_link_details_model.go index d1c6b63..edd2bf3 100644 --- a/model_integration_link_details_model.go +++ b/model_integration_link_details_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_integration_link_model.go b/model_integration_link_model.go index e83ac54..595d9eb 100644 --- a/model_integration_link_model.go +++ b/model_integration_link_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_integration_link_type.go b/model_integration_link_type.go index d49729d..09474fe 100644 --- a/model_integration_link_type.go +++ b/model_integration_link_type.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_me_model.go b/model_me_model.go index 4b3a0d4..bc097f8 100644 --- a/model_me_model.go +++ b/model_me_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_operation.go b/model_operation.go index c6c7d76..1e5cdf7 100644 --- a/model_operation.go +++ b/model_operation.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_organization_model.go b/model_organization_model.go index 9f5746a..ed34796 100644 --- a/model_organization_model.go +++ b/model_organization_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_organization_model_haljson.go b/model_organization_model_haljson.go new file mode 100644 index 0000000..802f039 --- /dev/null +++ b/model_organization_model_haljson.go @@ -0,0 +1,16 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type OrganizationModelHaljson struct { + OrganizationId string `json:"organizationId,omitempty"` + Name string `json:"name,omitempty"` + Links *OrganizationModelhaljsonLinks `json:"_links,omitempty"` +} diff --git a/model_organization_modelhaljson__links.go b/model_organization_modelhaljson__links.go new file mode 100644 index 0000000..0cc8cb9 --- /dev/null +++ b/model_organization_modelhaljson__links.go @@ -0,0 +1,14 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type OrganizationModelhaljsonLinks struct { + Products string `json:"products,omitempty"` +} diff --git a/model_product_model.go b/model_product_model.go index 9ed48a7..3b6d71e 100644 --- a/model_product_model.go +++ b/model_product_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_product_model_haljson.go b/model_product_model_haljson.go index 0465ef0..89c8f95 100644 --- a/model_product_model_haljson.go +++ b/model_product_model_haljson.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_product_modelhaljson__embedded.go b/model_product_modelhaljson__embedded.go index 9610bb1..f86955c 100644 --- a/model_product_modelhaljson__embedded.go +++ b/model_product_modelhaljson__embedded.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_product_modelhaljson__embedded_organization.go b/model_product_modelhaljson__embedded_organization.go index 266e0b4..436fb2d 100644 --- a/model_product_modelhaljson__embedded_organization.go +++ b/model_product_modelhaljson__embedded_organization.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -12,4 +12,5 @@ package configcatpublicapi type ProductModelhaljsonEmbeddedOrganization struct { OrganizationId string `json:"organizationId,omitempty"` Name string `json:"name,omitempty"` + Links *OrganizationModelhaljsonLinks `json:"_links,omitempty"` } diff --git a/model_product_modelhaljson__links.go b/model_product_modelhaljson__links.go index 0b99b2b..e76dd29 100644 --- a/model_product_modelhaljson__links.go +++ b/model_product_modelhaljson__links.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -10,6 +10,8 @@ package configcatpublicapi type ProductModelhaljsonLinks struct { + Self string `json:"self,omitempty"` Configs string `json:"configs,omitempty"` Environments string `json:"environments,omitempty"` + Tags string `json:"tags,omitempty"` } diff --git a/model_rollout_percentage_item_model.go b/model_rollout_percentage_item_model.go index c8878ec..a7eba25 100644 --- a/model_rollout_percentage_item_model.go +++ b/model_rollout_percentage_item_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_rollout_rule_comparator.go b/model_rollout_rule_comparator.go index 6b1937e..051209f 100644 --- a/model_rollout_rule_comparator.go +++ b/model_rollout_rule_comparator.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_rollout_rule_model.go b/model_rollout_rule_model.go index 64dc6c1..a95a43e 100644 --- a/model_rollout_rule_model.go +++ b/model_rollout_rule_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_data_model.go b/model_setting_data_model.go index 88dbc6d..86b8768 100644 --- a/model_setting_data_model.go +++ b/model_setting_data_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_model.go b/model_setting_model.go index 681df06..61ae6c6 100644 --- a/model_setting_model.go +++ b/model_setting_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -19,4 +19,5 @@ type SettingModel struct { OwnerUserFullName string `json:"ownerUserFullName,omitempty"` ConfigId string `json:"configId,omitempty"` ConfigName string `json:"configName,omitempty"` + Tags []TagModel `json:"tags,omitempty"` } diff --git a/model_setting_model_haljson.go b/model_setting_model_haljson.go new file mode 100644 index 0000000..3d92f0d --- /dev/null +++ b/model_setting_model_haljson.go @@ -0,0 +1,24 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type SettingModelHaljson struct { + SettingId int32 `json:"settingId,omitempty"` + Key string `json:"key,omitempty"` + Name string `json:"name,omitempty"` + Hint string `json:"hint,omitempty"` + SettingType *SettingType `json:"settingType,omitempty"` + OwnerUserEmail string `json:"ownerUserEmail,omitempty"` + OwnerUserFullName string `json:"ownerUserFullName,omitempty"` + ConfigId string `json:"configId,omitempty"` + ConfigName string `json:"configName,omitempty"` + Embedded *SettingModelhaljsonEmbedded `json:"_embedded,omitempty"` + Links *EnvironmentModelhaljsonLinks `json:"_links,omitempty"` +} diff --git a/model_setting_modelhaljson__embedded.go b/model_setting_modelhaljson__embedded.go new file mode 100644 index 0000000..fa4c00a --- /dev/null +++ b/model_setting_modelhaljson__embedded.go @@ -0,0 +1,14 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type SettingModelhaljsonEmbedded struct { + Tags []SettingModelhaljsonEmbeddedTags `json:"tags,omitempty"` +} diff --git a/model_setting_modelhaljson__embedded_tags.go b/model_setting_modelhaljson__embedded_tags.go new file mode 100644 index 0000000..a79573d --- /dev/null +++ b/model_setting_modelhaljson__embedded_tags.go @@ -0,0 +1,17 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type SettingModelhaljsonEmbeddedTags struct { + TagId int64 `json:"tagId,omitempty"` + Name string `json:"name,omitempty"` + Color string `json:"color,omitempty"` + Links *EnvironmentModelhaljsonLinks `json:"_links,omitempty"` +} diff --git a/model_setting_tag_model.go b/model_setting_tag_model.go index b887a8a..6a96f1c 100644 --- a/model_setting_tag_model.go +++ b/model_setting_tag_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_type.go b/model_setting_type.go index 1e62e75..0d98adc 100644 --- a/model_setting_type.go +++ b/model_setting_type.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_value_model.go b/model_setting_value_model.go index 98c4492..473fb2e 100644 --- a/model_setting_value_model.go +++ b/model_setting_value_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_value_model_haljson.go b/model_setting_value_model_haljson.go index f4dede4..aaf1c3e 100644 --- a/model_setting_value_model_haljson.go +++ b/model_setting_value_model_haljson.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -19,6 +19,6 @@ type SettingValueModelHaljson struct { // The percentage rule collection. RolloutPercentageItems []RolloutPercentageItemModel `json:"rolloutPercentageItems,omitempty"` // The value to serve. It must respect the setting type. - Value *interface{} `json:"value,omitempty"` - Links *SettingValueModelhaljsonLinks `json:"_links,omitempty"` + Value *interface{} `json:"value,omitempty"` + Links *EnvironmentModelhaljsonLinks `json:"_links,omitempty"` } diff --git a/model_setting_value_modelhaljson__embedded.go b/model_setting_value_modelhaljson__embedded.go index 172f53d..73ef67f 100644 --- a/model_setting_value_modelhaljson__embedded.go +++ b/model_setting_value_modelhaljson__embedded.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_value_modelhaljson__embedded_config.go b/model_setting_value_modelhaljson__embedded_config.go index 9da5089..5c9f25a 100644 --- a/model_setting_value_modelhaljson__embedded_config.go +++ b/model_setting_value_modelhaljson__embedded_config.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_value_modelhaljson__embedded_environment.go b/model_setting_value_modelhaljson__embedded_environment.go index abf3166..fc12d29 100644 --- a/model_setting_value_modelhaljson__embedded_environment.go +++ b/model_setting_value_modelhaljson__embedded_environment.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com @@ -12,4 +12,5 @@ package configcatpublicapi type SettingValueModelhaljsonEmbeddedEnvironment struct { EnvironmentId string `json:"environmentId,omitempty"` Name string `json:"name,omitempty"` + Links *EnvironmentModelhaljsonLinks `json:"_links,omitempty"` } diff --git a/model_setting_value_modelhaljson__embedded_integration_links.go b/model_setting_value_modelhaljson__embedded_integration_links.go index fe15e83..a96b89b 100644 --- a/model_setting_value_modelhaljson__embedded_integration_links.go +++ b/model_setting_value_modelhaljson__embedded_integration_links.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_value_modelhaljson__embedded_setting.go b/model_setting_value_modelhaljson__embedded_setting.go index 9aa52fc..f325c7a 100644 --- a/model_setting_value_modelhaljson__embedded_setting.go +++ b/model_setting_value_modelhaljson__embedded_setting.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_setting_value_modelhaljson__embedded_setting_tags.go b/model_setting_value_modelhaljson__embedded_setting_tags.go index cc070a4..83d31b6 100644 --- a/model_setting_value_modelhaljson__embedded_setting_tags.go +++ b/model_setting_value_modelhaljson__embedded_setting_tags.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_tag_model.go b/model_tag_model.go new file mode 100644 index 0000000..e4288ed --- /dev/null +++ b/model_tag_model.go @@ -0,0 +1,16 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type TagModel struct { + TagId int64 `json:"tagId,omitempty"` + Name string `json:"name,omitempty"` + Color string `json:"color,omitempty"` +} diff --git a/model_tag_model_haljson.go b/model_tag_model_haljson.go new file mode 100644 index 0000000..72bc901 --- /dev/null +++ b/model_tag_model_haljson.go @@ -0,0 +1,17 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type TagModelHaljson struct { + TagId int64 `json:"tagId,omitempty"` + Name string `json:"name,omitempty"` + Color string `json:"color,omitempty"` + Links *EnvironmentModelhaljsonLinks `json:"_links,omitempty"` +} diff --git a/model_update_config_request.go b/model_update_config_request.go new file mode 100644 index 0000000..f67bd0f --- /dev/null +++ b/model_update_config_request.go @@ -0,0 +1,14 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type UpdateConfigRequest struct { + Name string `json:"name,omitempty"` +} diff --git a/model_update_environment_model.go b/model_update_environment_model.go index 30d37cd..693cf82 100644 --- a/model_update_environment_model.go +++ b/model_update_environment_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_update_product_request.go b/model_update_product_request.go new file mode 100644 index 0000000..e3ac276 --- /dev/null +++ b/model_update_product_request.go @@ -0,0 +1,14 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type UpdateProductRequest struct { + Name string `json:"name,omitempty"` +} diff --git a/model_update_setting_value_model.go b/model_update_setting_value_model.go index d3d66da..cdcf018 100644 --- a/model_update_setting_value_model.go +++ b/model_update_setting_value_model.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com diff --git a/model_update_tag_model.go b/model_update_tag_model.go new file mode 100644 index 0000000..18d432a --- /dev/null +++ b/model_update_tag_model.go @@ -0,0 +1,15 @@ +/* + * ConfigCat Public Management API + * + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * + * API version: v1 + * Contact: support@configcat.com + * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) + */ +package configcatpublicapi + +type UpdateTagModel struct { + Name string `json:"name"` + Color string `json:"color,omitempty"` +} diff --git a/response.go b/response.go index 964241a..3768671 100644 --- a/response.go +++ b/response.go @@ -1,7 +1,7 @@ /* * ConfigCat Public Management API * - * **Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. + * **Base API URL**: https://localhost If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based on HTTP REST, uses resource-oriented URLs, status codes and supports JSON and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the [SDKs instead](https://configcat.com/docs/sdk-reference/overview). # OpenAPI Specification The complete specification is publicly available here: [swagger.json](v1/swagger.json). You can use it to generate client libraries in various languages with [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) or [Swagger Codegen](https://swagger.io/tools/swagger-codegen/) to interact with this API. # Authentication This API uses the [Basic HTTP Authentication Scheme](https://en.wikipedia.org/wiki/Basic_access_authentication). # Throttling and rate limits All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers: | Header | Description | | :- | :- | | X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. | | X-Rate-Limit-Reset | The time when the current rate limit period resets. | When the rate limit is exceeded by a request, the API returns with a `HTTP 429 - Too many requests` status along with a `Retry-After` HTTP header. * * API version: v1 * Contact: support@configcat.com