docs: add in gradual rollout use case doc #8172
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files |
There was a problem hiding this comment.
Thank you @nnennandukwe! 🚀 🤩 Left a few suggestions, mostly to align the casing of the headings
|
|
||
| The key benefits of gradual rollouts are that you can experiment rapidly on a controlled group and roll back quickly if the experiment goes wrong. This reduces the risk of failure, improves software quality, improves user experience, and optimizes resource utilization. | ||
|
|
||
| ## How to Perform a Gradual Rollout with Unleash |
There was a problem hiding this comment.
Suggested change
| ## How to Perform a Gradual Rollout with Unleash | |
| ## How to perform a gradual rollout with Unleash |
|
|
||
| With your feature flag management service, your application, an API token, and an Unleash SDK added to your application, you are now able to set up and manage a gradual rollout with a feature flag. | ||
|
|
||
| ## Configuring Gradual Rollouts in Unleash |
There was a problem hiding this comment.
Suggested change
| ## Configuring Gradual Rollouts in Unleash | |
| ## Configuring gradual rollouts in Unleash |
|
|
||
| Next, we will configure the gradual rollout strategy for your new flag. | ||
|
|
||
| ## Implementing Gradual Rollout Activation Strategy |
There was a problem hiding this comment.
Suggested change
| ## Implementing Gradual Rollout Activation Strategy | |
| ## Implementing a gradual rollout activation strategy |
|
|
||
| In the next section, we’ll explore how to apply a strategy constraint on top of a gradual rollout for more advanced use cases. | ||
|
|
||
| ## Applying Strategy Constraints |
There was a problem hiding this comment.
Suggested change
| ## Applying Strategy Constraints | |
| ## Applying strategy constraints |
| 1. [Strategy Constraints](/reference/strategy-constraints) | ||
| 2. [How to add strategy constraints](/how-to/how-to-add-strategy-constraints) | ||
|
|
||
| ### Define Custom Context Fields for Strategy Constraints |
There was a problem hiding this comment.
Suggested change
| ### Define Custom Context Fields for Strategy Constraints | |
| ### Define custom context fields for strategy constraints |
website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md
Outdated
Show resolved
Hide resolved
|
|
||
| When utilizing an activation strategy such as a gradual rollout, it may be necessary to further define which subset of users get access to a feature and when the rollout takes place, depending on the complexity of your use case. Unleash provides [Strategy Constraints](/reference/strategy-constraints) as a way to fine-tune conditions under which a feature flag is evaluated. Within a gradual rollout activation strategy, you can use strategy constraints to, for example: | ||
|
|
||
| - roll out a feature only to users in a specific region |
There was a problem hiding this comment.
I think it would be nice to uppercase these for consistency with other lists on the page, but that might mean a rewrite for the last bullet point
website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md
Outdated
Show resolved
Hide resolved
website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md
Outdated
Show resolved
Hide resolved
website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the changes
Adding in 1 of 7 use cases to our feature flag tutorials docs.
Upcoming additions to this PR:
Closes #
Important files
Discussion points