Update license requirements (#3296)

DMallare · web-flow · commit 794497d2435c · 2025-09-02T12:21:42.000-04:00
Updates documentation to reflect feature tiering changes made in the [recent router release](https://github.com/apollographql/router/releases/tag/v2.6.0). References: - [Product's feature tiering matrix](https://docs.google.com/document/d/13wh3NBmBnSPKBCH1f19eir-caWbz6Y9wKEHItXq6l1c/edit?tab=t.7kwmpu4gs3p#heading=h.37ncslwgnmfs) - [Additional feedback from product](https://docs.google.com/document/d/1ea30pyaIAaBg4xTUXuUDDa3w16fhhR7KvEm3QQNE-D8/edit?tab=t.pyvj315sx3ne#heading=h.gx3p2h7ez2ov) ### Testing Ran the docs site locally using `librarian.local.config.mts` file with override for the `federation` repository. Specifically, the following pages were checked: - http://localhost:3000/docs/graphos/connectors/reference/directives - http://localhost:3000/docs/graphos/schema-design/federated-schemas/entities/use-contexts - http://localhost:3000/docs/graphos/schema-design/federated-schemas/entities/migrate-fields#incremental-migration-with-progressive-override
diff --git a/docs/shared/licensed-directive.mdx b/docs/shared/licensed-directive.mdx
@@ -0,0 +1,5 @@
+<PlanRequired plans={["Free", "Developer", "Standard", "Enterprise"]}>
+
+Rate limits apply on the Free plan.
+
+</PlanRequired>
diff --git a/docs/shared/progressive-override-enterprise.mdx b/docs/shared/progressive-override-enterprise.mdx
diff --git a/docs/source/schema-design/federated-schemas/entities/migrate-fields.mdx b/docs/source/schema-design/federated-schemas/entities/migrate-fields.mdx
@@ -4,8 +4,6 @@ subtitle: Transfer entity fields from one subgraph to another
 description: Learn how to safely move parts of one subgraph to another subgraph in a federated GraphQL architecture using the @override directive.
 ---
 
-import ProgressiveOverrideEnterprise from '../../../../shared/progressive-override-enterprise.mdx';
-
 As your supergraph grows, you might want to move parts of one subgraph to another subgraph.
 For example, suppose your Payments subgraph defines a `Bill` entity:
 
@@ -160,8 +158,6 @@ After you deploy the Billing subgraph and publish this final schema change, you'
 
 <MinVersionBadge version="Federation v2.7" />
 
-<ProgressiveOverrideEnterprise/>
-
 Follow these steps to incrementally migrate a field from one subgraph to another.
 These steps use the `amount` field in the example Payments and Billing subgraphs described at the top of the page, but you can them with any entity field(s).
 
diff --git a/docs/source/schema-design/federated-schemas/entities/use-contexts.mdx b/docs/source/schema-design/federated-schemas/entities/use-contexts.mdx
@@ -5,12 +5,6 @@ description: Use the @context and @fromContext directives to enable a subgraph t
 minVersion: Federation v2.8
 ---
 
-<EnterpriseFeature>
-
-The `@context` and `@fromContext` directives are [Enterprise features](https://www.apollographql.com/pricing) of the Apollo Router and require an organization with a [GraphOS Enterprise plan](https://www.apollographql.com/pricing/). If your organization doesn't have an Enterprise plan, you can test it out by signing up for a free [Enterprise trial](https://studio.apollographql.com/signup?referrer=docs).
-
-</EnterpriseFeature>
-
 In an entity, a nested object may have a dependency on an ancestor type and thus need access to that ancestor's field(s).
 
 To enable a descendant to access an ancestor's field, you could add it as a `@key` field to every entity along the chain of nested types, but that can become problematic. Deeply nested types can change the `@key` fields of many entities. The added field may be irrelevant to the entities it's added to. Most importantly, overloading `@key` fields often breaks the separation of concerns between different subgraphs.
diff --git a/docs/source/schema-design/federated-schemas/reference/directives.mdx b/docs/source/schema-design/federated-schemas/reference/directives.mdx
@@ -4,8 +4,8 @@ subtitle: Reference for Apollo Federation specific GraphQL directives
 description: Reference for GraphQL federation directives including @key, @extends, @sharable, @override, @requires and more.
 ---
 
-import ProgressiveOverrideEnterprise from '../../../../shared/progressive-override-enterprise.mdx';
 import EnterpriseDirective from '../../../../shared/enterprise-directive.mdx';
+import LicensedDirective from '../../../../shared/licensed-directive.mdx';
 import LinkDirective from '../../../../shared/link-directive.mdx';
 
 Apollo Federation defines a collection of directives that you use in your subgraph schemas to enable certain features.
@@ -379,8 +379,6 @@ For more information, see [Migrating entity and root fields](/graphos/schema-des
 
 <MinVersionBadge version="Federation v2.7" />
 
-<ProgressiveOverrideEnterprise/>
-
 Rolling out any change to a production subgraph, including field migration, risks degrading the performance of your graph. Rerouting all traffic from one subgraph to another all at once could overload the overriding subgraph.
 
 The _progressive `@override`_ feature enables the gradual, progressive deployment of a subgraph with an `@override` field. As a subgraph developer, you can customize the percentage of traffic that the overriding and overridden subgraphs each resolve for a field. You apply a label to an `@override` field to set the percentage of traffic for the field that should be resolved by the overriding subgraph, with the remaining percentage resolved by the overridden subgraph. You can then monitor the performance of the subgraphs in Studio, resolve any issues, and iteratively and progressively increase the percentage until all traffic is resolved by the overriding subgraph.
@@ -426,12 +424,6 @@ To learn more, see the [Incremental migration with `@override`](/graphos/schema-
 </td>
 <td>
 
-<EnterpriseFeature>
-
-This argument is available in Apollo Federation 2.7 and later. It is an [Enterprise feature](https://www.apollographql.com/pricing) of the GraphOS Router and requires an organization with a [GraphOS Enterprise plan](https://www.apollographql.com/pricing/). You can test it out by signing up for a free [Enterprise trial](https://studio.apollographql.com/signup?referrer=docs).
-
-</EnterpriseFeature>
-
 **Optional.** A string of arbitrary arguments. Supported in this release:
 - `percent(<percent-value>)` - The percentage of traffic for the field that's resolved by this subgraph. The remaining percentage is resolved by the other ([from](#from)) subgraph. To learn more, see [Incremental migration with `@override`](/graphos/schema-design/federated-schemas/entities/migrate-fields#incremental-migration-with-progressive-override).
 
@@ -447,7 +439,7 @@ This argument is available in Apollo Federation 2.7 and later. It is an [Enterpr
 
 <MinVersionBadge version="Federation v2.5" />
 
-<EnterpriseDirective />
+<LicensedDirective />
 
 
 ```graphql
@@ -465,7 +457,7 @@ Indicates to composition that the target element is accessible only to the authe
 
 <MinVersionBadge version="Federation v2.5" />
 
-<EnterpriseDirective />
+<LicensedDirective />
 
 ```graphql
 directive @requiresScopes(scopes: [[federation__Scope!]!]!) on
@@ -895,8 +887,6 @@ If different subgraphs use different versions of a directive's corresponding spe
 
 <MinVersionBadge version="Federation v2.8" />
 
-<EnterpriseFeature />
-
 The `@context` directive defines a named context from which a field of the annotated type can be passed to a receiver of the context. The receiver must be a field annotated with the `@fromContext` directive. 
 
 ```graphql
@@ -928,8 +918,6 @@ type U @key(fields: "id") {
 
 <MinVersionBadge version="Federation v2.8" />
 
-<EnterpriseFeature />
-
 The `@fromContext` directive sets the context from which to receive the value of the annotated field. The context must have been defined with the `@context` directive.
 
 ```graphql
@@ -958,7 +946,7 @@ For examples using `@context` and `@fromContext`, see [Using contexts to share d
 
 <MinVersionBadge version="Federation v2.9" />
 
-<EnterpriseFeature />
+<LicensedDirective />
 
 ```graphql
 directive @cost(weight: Int!) on ARGUMENT_DEFINITION | ENUM | FIELD_DEFINITION | INPUT_FIELD_DEFINITION | OBJECT | SCALAR
@@ -1163,6 +1151,4 @@ The default value is `true`.
 
 <MinVersionBadge version="Federation v2.10" />
 
-<EnterpriseFeature />
-
 Directives for Connectors like `@connect` and `@source` are documented in [Connector Directives Reference](/graphos/schema-design/connectors/directives).
