Skip to content

Commit 3d579fa

Browse files
authored
docs: no router redeploy required when updating percent label (#3192)
Clarify that no router redeploy is required to update percent label for progressive override
1 parent 9a2eaf2 commit 3d579fa

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/source/schema-design/federated-schemas/entities/migrate-fields.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -286,10 +286,10 @@ A few strategies to mitigate this concern:
286286

287287
### Customizing progressive `@override` behavior with a feature flag service
288288

289-
Out of the box, the router supports the `percent(x)` syntax for resolving labels based on a given percentage. Unfortunately, updating this number requires a subgraph publish and router redeploy.
289+
Out of the box, the router supports the `percent(x)` syntax for resolving labels based on a given percentage. Updating this number requires publishing the subgraph.
290290
To avoid this, you can use a feature flag service to dynamically update the label value.
291291

292-
The router provides an interface for coprocessors and rhai scripts to resolve arbitrary labels.
292+
The router provides an interface for coprocessors and Rhai scripts to resolve arbitrary labels.
293293
This lets you dial up or disable a label's rollout status without requiring a subgraph publish.
294294
A coprocessor or Rhai script that implements this should take the following steps:
295295

0 commit comments

Comments
 (0)