mirror of
https://github.com/Unleash/unleash.git
synced 2025-08-09 13:47:13 +02:00
docs: change absolute url to relative (#10432)
This makes it easier to navigate inside the preview site (cause it stays in the preview instead of jumping to the docs website), and it also helps detecting broken links if we change the landing page (since the one in docs.getunleash.io will still exist).
This commit is contained in:
Gastón Fournier
GitHub
parent
7830fbb75f
commit
3479aa8b2c
@ -378,7 +378,7 @@ Read our documentation on [Event Log](/reference/events#event-log) and [APIs](/r
|
||||
|
||||
## Flag Automation and Workflow Integration for Django Apps
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
|
||||
It’s common for teams to have a development phase, QA/testing, and then a production release. Let’s say the changes we’ve made in our Django project must go through a typical development workflow.
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ description: "How to use Unleash feature flags with Django."
|
||||
slug: /feature-flag-tutorials/django
|
||||
---
|
||||
|
||||
Hello! In this tutorial, we’ll show you how to add feature flags to your Django app, using [Unleash](https://www.getunleash.io/) and the official [Unleash Python SDK](https://docs.getunleash.io/reference/sdks/python). With Unleash, an open-source feature flag service, you can use our tooling to add feature flags to your application and release new features faster.
|
||||
Hello! In this tutorial, we’ll show you how to add feature flags to your Django app, using [Unleash](https://www.getunleash.io/) and the official [Unleash Python SDK](/reference/sdks/python). With Unleash, an open-source feature flag service, you can use our tooling to add feature flags to your application and release new features faster.
|
||||
|
||||
In a classic tutorial fashion, we’ll add feature flags to a blog app made with Django. We’ll use feature flags to decide how many blog posts to show on the index page.
|
||||
|
||||
@ -157,7 +157,7 @@ def post_list(request):
|
||||
|
||||
Reload your browser and check that you see three blog posts displayed. Turn off the flag in your Unleash instance and reload the page. You should see all the blog posts again.
|
||||
|
||||
See additional use cases in our [Python SDK documentation](https://docs.getunleash.io/reference/sdks/python).
|
||||
See additional use cases in our [Python SDK documentation](/reference/sdks/python).
|
||||
|
||||
## Conclusion
|
||||
|
||||
|
||||
@ -342,7 +342,7 @@ Read our documentation on [Event Log](/reference/events#event-log) and [APIs](/r
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is automating them as part of your development workflow.
|
||||
|
||||
It’s common for teams to have a development phase, then QA/testing, and then a production release. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) can connect to your Jira server or cloud to create feature flags automatically during the project phases.
|
||||
It’s common for teams to have a development phase, then QA/testing, and then a production release. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) can connect to your Jira server or cloud to create feature flags automatically during the project phases.
|
||||
|
||||
As your code progresses through development and Jira tickets are updated, the relevant flag can turn on in a development environment. The next stage could be Canary deployments for testing with certain groups, like a QA team or beta users. The flag could be automatically turned on in QA and/or rolled out to target audiences in production.
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ description: "How to use Unleash feature flags with .NET."
|
||||
slug: /feature-flag-tutorials/dotnet
|
||||
---
|
||||
|
||||
Hello! In this tutorial we’ll show you how to add feature flags to your .NET app, using [Unleash](https://www.getunleash.io/) and the official [Unleash .NET SDK](https://docs.getunleash.io/reference/sdks/dotnet). With Unleash, an open-source feature management service, you can use our tooling to add feature flags to your application and release new features faster.
|
||||
Hello! In this tutorial we’ll show you how to add feature flags to your .NET app, using [Unleash](https://www.getunleash.io/) and the official [Unleash .NET SDK](/reference/sdks/dotnet). With Unleash, an open-source feature management service, you can use our tooling to add feature flags to your application and release new features faster.
|
||||
|
||||
We’ll keep with the sci-fi theme of our previous tutorials and use the [Rick and Morty API](https://rickandmortyapi.com/documentation/#introduction), with a .NET web API project. We’ll use feature flags to decide whether to call the REST or the GraphQL version of the API.
|
||||
|
||||
@ -65,7 +65,7 @@ Select the ‘New API token’ button.
|
||||
|
||||
|
||||
|
||||
Name the API token and select the “Server-side SDK (Client)” token type. You can read more about [Unleash API tokens in our documentation](https://docs.getunleash.io/reference/api-tokens-and-client-keys#client-tokens).
|
||||
Name the API token and select the “Server-side SDK (Client)” token type. You can read more about [Unleash API tokens in our documentation](/reference/api-tokens-and-client-keys#client-tokens).
|
||||
|
||||
.
|
||||
|
||||
@ -258,7 +258,7 @@ builder.Services.AddEndpointsApiExplorer();
|
||||
builder.Services.AddSwaggerGen();
|
||||
```
|
||||
|
||||
You can check our [API token and client keys documentation](https://docs.getunleash.io/reference/api-tokens-and-client-keys) for more specifics.
|
||||
You can check our [API token and client keys documentation](/reference/api-tokens-and-client-keys) for more specifics.
|
||||
|
||||
Now, let’s add our client to our project, grab the feature flag from Unleash, and update our conditional statement. Don't forget to also update the config with your API key.
|
||||
|
||||
@ -273,7 +273,7 @@ Now, let’s add our client to our project, grab the feature flag from Unleash,
|
||||
|
||||
```
|
||||
|
||||
See additional use cases in our [.NET SDK](https://docs.getunleash.io/reference/sdks/dotnet) documentation.
|
||||
See additional use cases in our [.NET SDK](/reference/sdks/dotnet) documentation.
|
||||
|
||||
## 5. Verify the toggle experience
|
||||
|
||||
|
||||
@ -18,11 +18,11 @@ Here’s a screenshot of the application:
|
||||
|
||||
## Setup variants in Unleash
|
||||
|
||||
In your Unleash instance, create a new feature flag called `likeOptionExperiment`. Choose the flag type called `Experiment` and enable the [impression data](https://docs.getunleash.io/reference/impression-data). By default, the flag will be set to false.
|
||||
In your Unleash instance, create a new feature flag called `likeOptionExperiment`. Choose the flag type called `Experiment` and enable the [impression data](/reference/impression-data). By default, the flag will be set to false.
|
||||
|
||||
|
||||
|
||||
Now that you have created your feature flag, let’s create two new [variants](https://docs.getunleash.io/reference/feature-toggle-variants) `gridTile` and `imageDetails` respectively. These variants will help you position your **like image** button.
|
||||
Now that you have created your feature flag, let’s create two new [variants](/reference/feature-toggle-variants) `gridTile` and `imageDetails` respectively. These variants will help you position your **like image** button.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -260,7 +260,7 @@ func main() {
|
||||
}
|
||||
```
|
||||
|
||||
See additional use cases in our [Server-Side SDK with Go](https://docs.getunleash.io/reference/sdks/go) documentation.
|
||||
See additional use cases in our [Server-Side SDK with Go](/reference/sdks/go) documentation.
|
||||
|
||||
## 6. Verify the toggle experience
|
||||
|
||||
|
||||
@ -308,7 +308,7 @@ Learn more about [how to configure your change requests](/reference/change-reque
|
||||
|
||||
## Flag Automation & Workflow Integration for iOS Apps
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
|
||||
Let’s say the changes we’ve made in our iOS tutorial project need to go through a typical development workflow.
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@ title: How to Implement Feature Flags in iOS
|
||||
slug: /feature-flag-tutorials/ios
|
||||
---
|
||||
|
||||
iOS is a mobile operating system developed by Apple for their mostly used mobile device: the iPhone. [Swift](https://www.swift.org/) is a programming language designed for Apple iOS devices. Unleash offers an [iOS SDK](https://docs.getunleash.io/reference/sdks/ios-proxy) for connecting SwiftUI with your iOS application to use feature flags. We will be using the open-source iOS Swift project called [Open Meteo](https://github.com/ighiba/open-meteo)!
|
||||
iOS is a mobile operating system developed by Apple for their mostly used mobile device: the iPhone. [Swift](https://www.swift.org/) is a programming language designed for Apple iOS devices. Unleash offers an [iOS SDK](/reference/sdks/ios-proxy) for connecting SwiftUI with your iOS application to use feature flags. We will be using the open-source iOS Swift project called [Open Meteo](https://github.com/ighiba/open-meteo)!
|
||||
|
||||
Leveraging feature flags allows developers to toggle new features on and off, whether you’re experimenting in your local environment, testing for QA purposes, or rolling out changes to users in production. With Unleash, an open-source feature flag service, you can use our tooling to implement feature flags into your application and release new features faster, strategically, and safely. But how can you do this in iOS with Swift?
|
||||
|
||||
@ -97,7 +97,7 @@ Select the ‘New API token’ button.
|
||||
|
||||
|
||||
|
||||
Name the API token and select the “Client-side SDK” token type, since we’ll be doing our flag evaluation on the client using the iOS SDK. You can read more about [Unleash API tokens in our documentation](https://docs.getunleash.io/reference/api-tokens-and-client-keys#client-tokens).
|
||||
Name the API token and select the “Client-side SDK” token type, since we’ll be doing our flag evaluation on the client using the iOS SDK. You can read more about [Unleash API tokens in our documentation](/reference/api-tokens-and-client-keys#client-tokens).
|
||||
|
||||
The token should have access to the “development” environment, as shown in the platform screenshot below.
|
||||
|
||||
|
||||
@ -157,7 +157,7 @@ In the main function of that file on line 21, set up the Unleash Client configur
|
||||
Unleash unleash = new DefaultUnleash(config);
|
||||
```
|
||||
|
||||
Read more on our [configuration examples in our Java SDK documentation](https://docs.getunleash.io/reference/sdks/java#example-configurations).
|
||||
Read more on our [configuration examples in our Java SDK documentation](/reference/sdks/java#example-configurations).
|
||||
|
||||
The `unleashAPI` will point your app to your local Unleash instance.
|
||||
|
||||
@ -165,7 +165,7 @@ Replace the `<API_KEY>` string in the configuration’s apiKey with the API toke
|
||||
|
||||
While the app is running, it will log the enabled status of the endpoint flag we created in our Unleash instance.
|
||||
|
||||
You can check our [API token and client keys documentation](https://docs.getunleash.io/reference/api-tokens-and-client-keys) for more specifics and see additional use cases in our [Server-Side SDK with Java](https://docs.getunleash.io/reference/sdks/java) documentation.
|
||||
You can check our [API token and client keys documentation](/reference/api-tokens-and-client-keys) for more specifics and see additional use cases in our [Server-Side SDK with Java](/reference/sdks/java) documentation.
|
||||
|
||||
To run the app, use the following command:
|
||||
|
||||
|
||||
@ -228,7 +228,7 @@ You can also retrieve events by using an API command. Read our documentation on
|
||||
|
||||
## Flag Automation & Workflow Integration for Java Apps
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
|
||||
It’s common for teams to have a development phase, QA/testing, and then a production release. Let’s say the changes we’ve made in our Java project must go through a typical development workflow.
|
||||
|
||||
|
||||
@ -377,7 +377,7 @@ Read our documentation on [Event Log](/reference/events#event-log) and [APIs](/r
|
||||
|
||||
## Flag Automation & Workflow Integration for Python Apps
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
|
||||
It’s common for teams to have a development phase, QA/testing, and then a production release. Let’s say the changes we’ve made in our Python project must go through a typical development workflow.
|
||||
|
||||
|
||||
@ -109,7 +109,7 @@ Select the ‘New API token’ button.
|
||||
|
||||
|
||||
|
||||
Name the API token and select the “Server-side SDK” token type, since we’ll be doing our flag evaluation on the server using the Python SDK. You can read more about [Unleash API tokens in our documentation](https://docs.getunleash.io/reference/api-tokens-and-client-keys#client-tokens).
|
||||
Name the API token and select the “Server-side SDK” token type, since we’ll be doing our flag evaluation on the server using the Python SDK. You can read more about [Unleash API tokens in our documentation](/reference/api-tokens-and-client-keys#client-tokens).
|
||||
|
||||
The token should have access to the “development” environment, as shown in the platform screenshot below.
|
||||
|
||||
@ -167,7 +167,7 @@ The URL will point your app to your Unleash instance through your Docker contain
|
||||
|
||||
Replace the `<API token>` string in the Authorization header with the API token we created on our Unleash instance. This will allow the app to communicate with the Unleash API to use the feature flag we created.
|
||||
|
||||
You can check our [API token and client keys documentation](https://docs.getunleash.io/reference/api-tokens-and-client-keys) for more specifics and see additional use cases in our [Server-Side SDK with Python](https://docs.getunleash.io/reference/sdks/python) documentation.
|
||||
You can check our [API token and client keys documentation](/reference/api-tokens-and-client-keys) for more specifics and see additional use cases in our [Server-Side SDK with Python](/reference/sdks/python) documentation.
|
||||
|
||||
Next, go to your terminal and build the app using this command:
|
||||
|
||||
|
||||
@ -339,7 +339,7 @@ Read our documentation on [Event Log](/reference/events#event-log) and [APIs](/r
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is automating them as part of your development workflow.
|
||||
|
||||
It’s common for teams to have a development phase, then QA/testing, and then a production release. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) can connect to your Jira server or cloud to create feature flags automatically during the project phases.
|
||||
It’s common for teams to have a development phase, then QA/testing, and then a production release. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) can connect to your Jira server or cloud to create feature flags automatically during the project phases.
|
||||
|
||||
As your code progresses through development and Jira tickets are updated, the relevant flag can turn on in a development environment. The next stage could be Canary deployments for testing with certain groups, like a QA team or beta users. The flag could be automatically turned on in QA and/or rolled out to target audiences in production.
|
||||
|
||||
|
||||
@ -434,7 +434,7 @@ Learn more about [how to configure your change requests](/reference/change-reque
|
||||
|
||||
## Flag Automation & Workflow Integration for React Apps
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
An advanced use case for leveraging feature flags at scale is flag automation in your development workflow. Many organizations use tools like Jira for managing projects and tracking releases across teams. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) helps to manage feature flag lifecycles associated with your projects.
|
||||
|
||||
Let’s say the changes we’ve made in our React tutorial project need to go through a typical development workflow.
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ slug: /feature-flag-tutorials/ruby
|
||||
|
||||
import VideoContent from '@site/src/components/VideoContent.jsx';
|
||||
|
||||
Hello! In this tutorial we’ll show you how to add feature flags to your Ruby app , using [Unleash](https://www.getunleash.io/) and the official [Unleash Ruby SDK](https://docs.getunleash.io/reference/sdks/ruby). With Unleash, an open-source feature flag service, you can use our tooling to add feature flags to your application and release new features faster.
|
||||
Hello! In this tutorial we’ll show you how to add feature flags to your Ruby app , using [Unleash](https://www.getunleash.io/) and the official [Unleash Ruby SDK](/reference/sdks/ruby). With Unleash, an open-source feature flag service, you can use our tooling to add feature flags to your application and release new features faster.
|
||||
|
||||
In a classic tutorial fashion, we’ll get a list of planets from the [Star Wars API](https://swapi.py4e.com), with just Ruby (i.e., not Ruby on Rails). We’ll use feature flags to decide whether to call the REST or the GraphQL version of the API.
|
||||
|
||||
@ -194,7 +194,7 @@ With these 2, you can initialize your Unleash client as follows:
|
||||
})
|
||||
```
|
||||
|
||||
You can check our [API token and client keys documentation](https://docs.getunleash.io/reference/api-tokens-and-client-keys) for more specifics.
|
||||
You can check our [API token and client keys documentation](/reference/api-tokens-and-client-keys) for more specifics.
|
||||
|
||||
Now, let’s add our client to our project, grab the feature flag from Unleash, and update our conditional statement. Don't forget to also update the config with your API key.
|
||||
|
||||
@ -217,7 +217,7 @@ require 'unleash'
|
||||
|
||||
```
|
||||
|
||||
See additional use cases in our [Server-Side SDK with Ruby](https://docs.getunleash.io/reference/sdks/ruby) documentation.
|
||||
See additional use cases in our [Server-Side SDK with Ruby](/reference/sdks/ruby) documentation.
|
||||
|
||||
## 6. Verify the toggle experience
|
||||
|
||||
|
||||
@ -338,7 +338,7 @@ Read our documentation on [Event Log](/reference/events#event-log) and [APIs](/r
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is automating them as part of your development workflow.
|
||||
|
||||
It’s common for teams to have a development phase, then QA/testing, and then a production release. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) can connect to your Jira server or cloud to create feature flags automatically during the project phases.
|
||||
It’s common for teams to have a development phase, then QA/testing, and then a production release. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) can connect to your Jira server or cloud to create feature flags automatically during the project phases.
|
||||
|
||||
As your code progresses through development and Jira tickets are updated, the relevant flag can turn on in a development environment. The next stage could be Canary deployments for testing with certain groups, like a QA team or beta users. The flag could be automatically turned on in QA and/or rolled out to target audiences in production.
|
||||
|
||||
|
||||
@ -4,9 +4,9 @@ description: "How to use Unleash feature flags with Rust."
|
||||
slug: /feature-flag-tutorials/rust
|
||||
---
|
||||
|
||||
Hello! In this tutorial we’ll show you how to add feature flags to your Rust app, using [Unleash](https://www.getunleash.io/) and the official [Unleash Rust SDK](https://docs.getunleash.io/reference/sdks/rust). With Unleash, an open-source feature management service, you can add feature flags to your applications and release new features faster.
|
||||
Hello! In this tutorial we’ll show you how to add feature flags to your Rust app, using [Unleash](https://www.getunleash.io/) and the official [Unleash Rust SDK](/reference/sdks/rust). With Unleash, an open-source feature management service, you can add feature flags to your applications and release new features faster.
|
||||
|
||||
We love Rust here at Unleash, our own [Unleash Edge](https://docs.getunleash.io/reference/unleash-edge) is built with Rust and it's a core part of our product.
|
||||
We love Rust here at Unleash, our own [Unleash Edge](/reference/unleash-edge) is built with Rust and it's a core part of our product.
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [1. Install a local feature flag provider](#1-install-a-local-feature-flag-provider)
|
||||
@ -69,7 +69,7 @@ Select the ‘New API token’ button or copy an existing token.
|
||||
|
||||
|
||||
|
||||
Name the API token and select the “Server-side SDK (Client)” token type. You can read more about [Unleash API tokens in our documentation](https://docs.getunleash.io/reference/api-tokens-and-client-keys#client-tokens).
|
||||
Name the API token and select the “Server-side SDK (Client)” token type. You can read more about [Unleash API tokens in our documentation](/reference/api-tokens-and-client-keys#client-tokens).
|
||||
|
||||
|
||||
|
||||
|
||||
@ -412,7 +412,7 @@ Read our documentation on [Event Log](/reference/events#event-log) and [APIs](/r
|
||||
|
||||
An advanced use case for leveraging feature flags at scale is automating them as part of your development workflow.
|
||||
|
||||
It’s common for teams to have a development phase, then QA/testing, and then a production release. Our [Unleash Jira plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) can connect to your Jira server or cloud to create feature flags automatically during the project phases.
|
||||
It’s common for teams to have a development phase, then QA/testing, and then a production release. Our [Unleash Jira plugin](/reference/integrations/jira-cloud-plugin-installation) can connect to your Jira server or cloud to create feature flags automatically during the project phases.
|
||||
|
||||
As your code progresses through development and Jira tickets are updated, the relevant flag can turn on in a development environment. The next stage could be Canary deployments for testing with certain groups, like a QA team or beta users. The flag could be automatically turned on in QA and/or rolled out to target audiences in production.
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ description: "How to use Unleash feature flags with SvelteKit."
|
||||
slug: /feature-flag-tutorials/sveltekit
|
||||
---
|
||||
|
||||
Hello and welcome to another tutorial. This is about adding feature flags to an app made with [SvelteKit](https://kit.svelte.dev/), [Unleash](https://www.getunleash.io/) and the official [Unleash Svelte SDK](https://docs.getunleash.io/reference/sdks/svelte).
|
||||
Hello and welcome to another tutorial. This is about adding feature flags to an app made with [SvelteKit](https://kit.svelte.dev/), [Unleash](https://www.getunleash.io/) and the official [Unleash Svelte SDK](/reference/sdks/svelte).
|
||||
|
||||
We'll make a paired-down habits app to keep track of your new year's resolutions. The feature flag will be used to change the number of habits a user can add.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ import SearchPriority from '@site/src/components/SearchPriority';
|
||||
|
||||
:::caution Removal notice
|
||||
|
||||
Api admin state is deprecated from version 5 and removed in version 6. We recommend using the new [Environment Import & Export](https://docs.getunleash.io/reference/deploy/environment-import-export).
|
||||
Api admin state is deprecated from version 5 and removed in version 6. We recommend using the new [Environment Import & Export](/how-to/how-to-environment-import-export).
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ import SearchPriority from '@site/src/components/SearchPriority';
|
||||
|
||||
:::caution Removal notice
|
||||
|
||||
Api admin state is deprecated from version 5 and removed from version 6. We recommend using the new [Environment Import & Export](https://docs.getunleash.io/reference/deploy/environment-import-export).
|
||||
Api admin state is deprecated from version 5 and removed from version 6. We recommend using the new [Environment Import & Export](/how-to/how-to-environment-import-export).
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ import SearchPriority from '@site/src/components/SearchPriority';
|
||||
|
||||
## Overview
|
||||
|
||||
The Unleash [Frontend API](/reference/api/unleash/frontend-api) simplifies connecting client-side applications to Unleash. [Unleash Edge](https://docs.getunleash.io/reference/unleash-edge) also implements this API allowing you to scale from development environments, low-traffic applications, or internal dashboards to a production-ready scalable solution.
|
||||
The Unleash [Frontend API](/reference/api/unleash/frontend-api) simplifies connecting client-side applications to Unleash. [Unleash Edge](/reference/unleash-edge) also implements this API allowing you to scale from development environments, low-traffic applications, or internal dashboards to a production-ready scalable solution.
|
||||
|
||||
The Frontend API has a straightforward setup, and since it is built directly into Unleash, you don't need to manage it. However, unlike Unleash Edge, it cannot be scaled horizontally and isn’t designed for high request volumes.
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ import SearchPriority from '@site/src/components/SearchPriority';
|
||||
|
||||
:::info Deprecated
|
||||
|
||||
The Jira Server plugin is **deprecated**, please use the [Unleash Jira Cloud plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) instead
|
||||
The Jira Server plugin is **deprecated**, please use the [Unleash Jira Cloud plugin](/reference/integrations/jira-cloud-plugin-installation) instead
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ import SearchPriority from '@site/src/components/SearchPriority';
|
||||
|
||||
:::info Deprecated
|
||||
|
||||
The Jira Server plugin is **deprecated**, please use the [Unleash Jira Cloud plugin](https://docs.getunleash.io/reference/integrations/jira-cloud-plugin-installation) instead
|
||||
The Jira Server plugin is **deprecated**, please use the [Unleash Jira Cloud plugin](/reference/integrations/jira-cloud-plugin-installation) instead
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@ -16,4 +16,4 @@ You can have only one active invite token at any given time. If an active token
|
||||
|
||||
As an Admin, you can create, update, and delete invite tokens through the Unleash Admin UI in **Admin settings > User config > Users > Create invite link**.
|
||||
|
||||
Alternatively, you can use the [Admin API](../reference/api/unleash/public-signup-tokens.tag.mdx) to manage the public invite token.
|
||||
Alternatively, you can use the [Admin API](../reference/api/unleash/public-signup-tokens.tag.mdx) to manage the public invite token.
|
||||
|
||||
@ -162,7 +162,7 @@ A good rule of thumb is that if the data is static (you don't expect it to chang
|
||||
|
||||
Feature flag names need to be [globally unique](https://docs.getunleash.io/topics/feature-flags/unique-names). In an ideal world, all flag references would be removed from the codebase as soon as a flag is archived—but in reality, that rarely happens. Using unique names helps protect new features from accidentally linking to old, unused flags that could unintentionally re-enable outdated behavior.
|
||||
|
||||
To avoid this risk, enforce a [naming pattern](https://docs.getunleash.io/reference/feature-toggles#set-a-naming-pattern) at flag creation.
|
||||
To avoid this risk, enforce a [naming pattern](/reference/feature-toggles#set-a-naming-pattern) at flag creation.
|
||||
|
||||
### Using large targeting lists
|
||||
|
||||
@ -228,7 +228,7 @@ Avoid putting all flags into one large group. While it might seem simpler, it qu
|
||||
|
||||
Modern applications are composed of multiple services with many complex dependencies. While organizing flags by applications, teams, or business units is a good starting point, real-world services often exist across these organizational boundaries.
|
||||
|
||||
Just because a user doesn't normally work with a flag doesn't mean they won't need to find it. However, you don't need to show every flag by default—especially those outside a user's main scope. What matters is that all flags are [searchable](https://docs.getunleash.io/reference/api/unleash/search-features). When someone searches for a flag, they should be able to view its configuration and ownership, so they can request access or submit a [change request](../../reference/change-requests) if needed.
|
||||
Just because a user doesn't normally work with a flag doesn't mean they won't need to find it. However, you don't need to show every flag by default—especially those outside a user's main scope. What matters is that all flags are [searchable](/reference/api/unleash/search-features). When someone searches for a flag, they should be able to view its configuration and ownership, so they can request access or submit a [change request](../../reference/change-requests) if needed.
|
||||
|
||||
This is why feature flag systems should be [open by default](./feature-flag-best-practices#5-choose-open-by-default).
|
||||
|
||||
|
||||
@ -110,7 +110,7 @@ Cross-Origin Resource Sharing (CORS) issues can prevent your client-side applica
|
||||
- Define the allowed origins (e.g., `https://your-app.com`).
|
||||
- **For troubleshooting:** You can temporarily set the allowed origin to `*` (a single asterisk) to allow all origins. This helps confirm if CORS is the root cause.
|
||||
- **Important Security Note:** Using `*` in production is generally discouraged. Always restrict origins to only those that require access.
|
||||
- These settings can also be managed via the [Unleash API](https://docs.getunleash.io/reference/api/unleash).
|
||||
- These settings can also be managed via the [Unleash API](/api-overview).
|
||||
|
||||
### Configuring CORS for Unleash Edge
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ As part of our commitment to maintaining a clean and robust codebase, several de
|
||||
|
||||
- **GET, PATCH, and PUT `/api/admin/projects/{projectId}/features/{featureName}/variants`**
|
||||
|
||||
Deprecated in: v4.21.0, use [strategy variants](https://docs.getunleash.io/reference/strategy-variants) instead.
|
||||
Deprecated in: v4.21.0, use [strategy variants](/reference/strategy-variants) instead.
|
||||
You can create or update variants when creating or adding a strategy to a feature flag.
|
||||
For example: `/api/admin/projects/{projectId}/features/{featureName}/environments/{environment}/strategies`.
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user