mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-18 20:09:08 +02:00
d5fbd0b743
## What This (admittedly massive) PR updates the "physical" documentation structure and fixes url inconsistencies and SEO problems reported by marketing. The main points are: - remove or move directories : advanced, user_guide, deploy, api - move the files contained within to the appropriate one of topics, how-to, tutorials, or reference - update internal doc links and product links to the content - create client-side redirects for all the urls that have changed. A number of the files have been renamed in small ways to better match their url and to make them easier to find. Additionally, the top-level api directory has been moved to /reference/api/legacy/unleash (see the discussion points section for more on this). ## Why When moving our doc structure to diataxis a while back, we left the "physical' files lying where they were, because it didn't matter much to the new structure. However, that did introduce some inconsistencies with where you place docs and how we organize them. There's also the discrepancies in whether urls us underscores or hyphens (which isn't necessarily the same as their file name), which has been annoying me for a while, but now has also been raised by marketing as an issue in terms of SEO. ## Discussion points The old, hand-written API docs have been moved from /api to /reference/api/legacy/unleash. There _is_ a /reference/api/unleash directory, but this is being populated by the OpenAPI plugin, and mixing those could only cause trouble. However, I'm unsure about putting /legacy/ in the title, because the API isn't legacy, the docs are. Maybe we could use another path? Like /old-docs/ or something? I'd appreciate some input on this.
142 lines
3.7 KiB
Markdown
142 lines
3.7 KiB
Markdown
---
|
|
id: state
|
|
title: /api/admin/state
|
|
---
|
|
|
|
> In order to access the admin API endpoints you need to identify yourself. Unless you're using the `none` authentication method, you'll need to [create an ADMIN token](/how-to/how-to-create-api-tokens) and add an Authorization header using the token.
|
|
|
|
### Export Feature Toggles & Strategies {#export-feature-toggles--strategies}
|
|
|
|
`GET: http://unleash.host.com/api/admin/state/export`
|
|
|
|
The api endpoint `/api/admin/state/export` will export feature-toggles and strategies as json by default.\
|
|
You can customize the export with query parameters:
|
|
|
|
| Parameter | Default | Description |
|
|
| --- | --- | --- |
|
|
| format | `json` | Export format, either `json` or `yaml` |
|
|
| download | `false` | If the exported data should be downloaded as a file |
|
|
| featureToggles | `true` | Include feature-toggles in the exported data |
|
|
| strategies | `true` | Include strategies in the exported data |
|
|
|
|
**Example response:**
|
|
|
|
`GET /api/admin/state/export?format=yaml&featureToggles=1&strategies=1`
|
|
|
|
```yaml
|
|
version: 1
|
|
features:
|
|
- name: Feature.A
|
|
description: lorem ipsum
|
|
enabled: false
|
|
strategies:
|
|
- name: default
|
|
parameters: {}
|
|
variants:
|
|
- name: variant1
|
|
weight: 50
|
|
- name: variant2
|
|
weight: 50
|
|
- name: Feature.B
|
|
description: lorem ipsum
|
|
enabled: true
|
|
strategies:
|
|
- name: ActiveForUserWithId
|
|
parameters:
|
|
userIdList: '123,221,998'
|
|
- name: GradualRolloutRandom
|
|
parameters:
|
|
percentage: '10'
|
|
variants: []
|
|
strategies:
|
|
- name: country
|
|
description: Enable feature for certain countries
|
|
parameters:
|
|
- name: countries
|
|
type: list
|
|
description: List of countries
|
|
required: true
|
|
```
|
|
|
|
### Import Feature Toggles & Strategies {#import-feature-toggles--strategies}
|
|
|
|
`POST: http://unleash.host.com/api/admin/state/import`
|
|
|
|
You can import feature-toggles and strategies by POSTing to the `/api/admin/state/import` endpoint.\
|
|
You can either send the data as JSON in the POST-body or send a `file` parameter with `multipart/form-data` (YAML files are also accepted here).
|
|
|
|
**Query Paramters**
|
|
|
|
- **drop** - Use this parameter if you want the database to be cleaned before import (all strategies and features will be removed).
|
|
- **keep** - Use this query parameter if you want to keep all exiting feature toggle (and strategy) configurations as is (no override), and only insert missing feature toggles from the data provided.
|
|
|
|
> You should be careful using the `drop` parameter in production environments.
|
|
|
|
Success: `202 Accepted`\
|
|
Error: `400 Bad Request`
|
|
|
|
**Example body:**
|
|
|
|
```json
|
|
{
|
|
"version": 1,
|
|
"features": [
|
|
{
|
|
"name": "Feature.A",
|
|
"description": "lorem ipsum",
|
|
"enabled": false,
|
|
"strategies": [
|
|
{
|
|
"name": "default",
|
|
"parameters": {}
|
|
}
|
|
],
|
|
"variants": [
|
|
{
|
|
"name": "variant1",
|
|
"weight": 50
|
|
},
|
|
{
|
|
"name": "variant2",
|
|
"weight": 50
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"name": "Feature.B",
|
|
"description": "lorem ipsum",
|
|
"enabled": true,
|
|
"strategies": [
|
|
{
|
|
"name": "ActiveForUserWithId",
|
|
"parameters": {
|
|
"userIdList": "123,221,998"
|
|
}
|
|
},
|
|
{
|
|
"name": "GradualRolloutRandom",
|
|
"parameters": {
|
|
"percentage": "10"
|
|
}
|
|
}
|
|
],
|
|
"variants": []
|
|
}
|
|
],
|
|
"strategies": [
|
|
{
|
|
"name": "country",
|
|
"description": "Enable feature for certain countries",
|
|
"parameters": [
|
|
{
|
|
"name": "countries",
|
|
"type": "list",
|
|
"description": "List of countries",
|
|
"required": true
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|
|
```
|