docs: Update many references to "FRS" with "AFR" (#23231)

Josmithr · web-flow · commit 26bb1e191528 · 2024-12-03T10:49:36.000-08:00
The repo has many lingering references to the old "FRS" terminology.
This PR replaces some trivial (mostly documentation) usages with "AFR".

We still have a number of usages of "FRS" terminology in code, which I
am not tackling here. Those should be done separately.
diff --git a/azure/packages/test/scenario-runner/README.md b/azure/packages/test/scenario-runner/README.md
@@ -2,7 +2,7 @@
 
 ## Azure Scenario Runner
 
-This package provides a reference application that executes pre-set scenarios with the intent of measuring the Fluid Framework's performance and reliability. We primarily use this package as part of a pipeline scheduled to run periodically to measure, log, and report various performance and reliability metrics. These metrics can then be used to gauge an undrestanding of the expected behavior/performance of the Fluid Framework in these various scenarios, which can help define the SLA.
+This package provides a reference application that executes pre-set scenarios with the intent of measuring the Fluid Framework's performance and reliability. We primarily use this package as part of a pipeline scheduled to run periodically to measure, log, and report various performance and reliability metrics. These metrics can then be used to gauge an understanding of the expected behavior/performance of the Fluid Framework in these various scenarios, which can help define the SLA.
 
 <!-- AUTO-GENERATED-CONTENT:START (LIBRARY_README_HEADER) -->
 
@@ -66,11 +66,11 @@ This scenario creates/loads a document and attempts to add many nested `SharedMa
 
 ## Running the perf tests locally
 
-1. Set the `azure__fluid__relay__service__tenantId` environment variable to equal your FRS TenantID
-2. Set the `azure__fluid__relay__service__tenantKey` environment variable to equal your FRS Tenant's Primary Key
-3. Set the `azure__fluid__relay__service__function__url` environment variable to equal your FRS Service Function URL
-4. Set the `azure__fluid__relay__service__endpoint` environment variable to equal the Alfred endpoint of your FRS tenant
-5. (Optional) Set the `azure__fluid__relay__service__region` environment variable to equal the region of your FRS tenant (eg. `westus2`, `westus3`, `eastus`, `westeurope`)
+1. Set the `azure__fluid__relay__service__tenantId` environment variable to equal your Azure Fluid Relay (AFR) TenantID
+2. Set the `azure__fluid__relay__service__tenantKey` environment variable to equal your AFR Tenant's Primary Key
+3. Set the `azure__fluid__relay__service__function__url` environment variable to equal your AFR Service Function URL
+4. Set the `azure__fluid__relay__service__endpoint` environment variable to equal the Alfred endpoint of your AFR tenant
+5. (Optional) Set the `azure__fluid__relay__service__region` environment variable to equal the region of your AFR tenant (eg. `westus2`, `westus3`, `eastus`, `westeurope`)
 6. Run the test with `npm run start`
 
 ## Configuring the test configuration
@@ -81,7 +81,7 @@ The test configuration file `testConfig_v1.yml` can be configured to modify the
 
 [TBD]
 
-Scenario runnner for FRS and Azure Local Service. This package can be used to create and execute various scenarios involving azure-client, IFluidContainer and a range of distributed data structures (DDSes), while collecting telemetry and validating state in the process. Scenarios are sourced via yaml config files.
+Scenario runner for AFR and Azure Local Service. This package can be used to create and execute various scenarios involving azure-client, IFluidContainer and a range of distributed data structures (DDSes), while collecting telemetry and validating state in the process. Scenarios are sourced via yaml config files.
 
 You can add new scenarios by following existing patterns (see `MapTrafficRunner` or `DocLoaderRunner` for examples) and adding additional test configs to the `configs` directory. Then, run your scenario with the command: `npm run start:scenario ./configs/<config-name>.yml`.
 
diff --git a/azure/packages/test/scenario-runner/src/utils.ts b/azure/packages/test/scenario-runner/src/utils.ts
@@ -116,21 +116,21 @@ export async function createAzureClient(config: AzureClientConfig): Promise<Azur
 	const useAzure = connectionConfig.type === "remote";
 
 	if (!connectionConfig.endpoint) {
-		throw new Error("Missing FRS configuration: Relay Service Endpoint URL.");
+		throw new Error("Missing AFR configuration: Relay Service Endpoint URL.");
 	}
 
 	let connectionProps: AzureRemoteConnectionConfig | AzureLocalConnectionConfig;
 
 	if (useAzure) {
 		if (!connectionConfig.tenantId) {
-			throw new Error("Missing FRS configuration: Tenant ID.");
+			throw new Error("Missing AFR configuration: Tenant ID.");
 		}
 
 		let tokenProvider: ITokenProvider;
 		/* Insecure Token Provider */
 		if (!connectionConfig.useSecureTokenProvider) {
 			if (!connectionConfig.key) {
-				throw new Error("Missing FRS configuration: Tenant Primary Key.");
+				throw new Error("Missing AFR configuration: Tenant Primary Key.");
 			}
 			tokenProvider = createInsecureTokenProvider(
 				connectionConfig.key,
@@ -140,7 +140,7 @@ export async function createAzureClient(config: AzureClientConfig): Promise<Azur
 		} else {
 			/* Secure Token Provider (Azure Function) */
 			if (!connectionConfig.functionUrl) {
-				throw new Error("Missing FRS configuration: Function URL.");
+				throw new Error("Missing AFR configuration: Function URL.");
 			}
 			tokenProvider = createAzureTokenProvider(
 				connectionConfig.functionUrl,
diff --git a/docs/api/fallback/routes.js b/docs/api/fallback/routes.js
@@ -32,6 +32,13 @@ const routes = [
 	// Counter DDS document was removed in v2.
 	// Redirect legacy URL to v1 document.
 	{ from: "/docs/data-structures/counter", to: "/docs/v1/data-structures/counter" },
+
+	// Legacy file name
+	{ from: "/docs/deployment/azure-frs", to: "/docs/deployment/azure-fluid-relay" },
+	{
+		from: "/versioned_docs/v1/deployment/azure-frs",
+		to: "/versioned_docs/v1/deployment/azure-fluid-relay",
+	},
 ];
 
 module.exports = routes;
diff --git a/docs/docs/api/index.mdx b/docs/docs/api/index.mdx
@@ -11,7 +11,7 @@ To get started with the Fluid Framework, you'll want to take a dependency on our
 You'll then want to pair that with the appropriate service client implementation based on your service.
 These include:
 
--   [@fluidframework/azure-client](./azure-client.md) (for use with [Azure Fluid Relay](../deployment/azure-frs))
+-   [@fluidframework/azure-client](./azure-client.md) (for use with [Azure Fluid Relay](../deployment/azure-fluid-relay))
 -   [@fluidframework/odsp-client](./odsp-client.md) (for use with [SharePoint Embedded](../deployment/sharepoint-embedded))
 -   [@fluidframework/tinylicious-client](./tinylicious-client) (for testing with [Tinylicious](../testing/tinylicious))
 
diff --git a/docs/docs/build/overview.mdx b/docs/docs/build/overview.mdx
@@ -25,7 +25,7 @@ See [Service-specific client libraries](#service-specific-client-libraries) for
 
 #### Azure Fluid Relay
 
-[Azure Fluid Relay](../deployment/azure-frs) is a cloud service that enables real-time collaboration on shared data models. It is a fully managed service that provides a secure, scalable, and reliable way to connect clients to each other and to the data models they share.
+[Azure Fluid Relay](../deployment/azure-fluid-relay) is a cloud service that enables real-time collaboration on shared data models. It is a fully managed service that provides a secure, scalable, and reliable way to connect clients to each other and to the data models they share.
 
 #### SharePoint Embedded
 
@@ -72,6 +72,6 @@ Fluid works with multiple service implementations. Each service has a correspond
 For specifics about each service-specific client implementation see their corresponding documentation.
 
 -   The client library for the [Tinylicious](/docs/testing/tinylicious) service is in the package [@fluidframework/tinylicious-client](https://www.npmjs.com/package/@fluidframework/tinylicious-client).
--   The client library for the [Azure Fluid Relay](../deployment/azure-frs) is in the package [@fluidframework/azure-client](https://www.npmjs.com/package/@fluidframework/azure-client).
+-   The client library for the [Azure Fluid Relay](../deployment/azure-fluid-relay) is in the package [@fluidframework/azure-client](https://www.npmjs.com/package/@fluidframework/azure-client).
 
 For more information see [Packages](./packages).
diff --git a/docs/docs/deployment/azure-fluid-relay.mdx b/docs/docs/deployment/azure-fluid-relay.mdx
diff --git a/docs/docs/start/tutorial.mdx b/docs/docs/start/tutorial.mdx
@@ -49,7 +49,7 @@ const root = document.getElementById("content");
 
 :::note
 
-To create a Fluid application that can be deployed to Azure, check out the [Azure Fluid Relay](../deployment/azure-frs).
+To create a Fluid application that can be deployed to Azure, check out the [Azure Fluid Relay](../deployment/azure-fluid-relay).
 
 :::
 
diff --git a/docs/docs/testing/testing.mdx b/docs/docs/testing/testing.mdx
@@ -8,7 +8,7 @@ slug: /testing/testing
 
 ## Overview
 
-Testing and automation are crucial to maintaining the quality and longevity of your code. Internally, Fluid has a range of unit and integration tests powered by [Mocha](https://mochajs.org/), [Jest](https://jestjs.io/), [Puppeteer](https://github.com/puppeteer/puppeteer), and [webpack](https://webpack.js.org/). Tests that need to run against a service are backed by [Tinylicious](./tinylicious) or a test tenant of a [live service](../deployment/service-options) such as [Azure Fluid Relay](../deployment/azure-frs).
+Testing and automation are crucial to maintaining the quality and longevity of your code. Internally, Fluid has a range of unit and integration tests powered by [Mocha](https://mochajs.org/), [Jest](https://jestjs.io/), [Puppeteer](https://github.com/puppeteer/puppeteer), and [webpack](https://webpack.js.org/). Tests that need to run against a service are backed by [Tinylicious](./tinylicious) or a test tenant of a [live service](../deployment/service-options) such as [Azure Fluid Relay](../deployment/azure-fluid-relay).
 
 This document will explain how to use these tools to get started with writing automation for Fluid applications against a service. It will focus on interactions with the service rather than automation in general, and will not cover the automation tools themselves or scenarios that do not require a service.
 
@@ -38,7 +38,7 @@ The `test:tinylicious` script will start Tinylicious, wait until port 7070 respo
 
 ## Automation against Azure Fluid Relay
 
-Your automation can connect to a test tenant for Azure Fluid Relay in the same way as your production tenant and only needs the appropriate connection configuration. See [Connect to Azure Fluid Relay](../deployment/azure-frs) for more details.
+Your automation can connect to a test tenant for Azure Fluid Relay in the same way as your production tenant and only needs the appropriate connection configuration. See [Connect to Azure Fluid Relay](../deployment/azure-fluid-relay) for more details.
 
 ### Azure Fluid Relay as an abstraction for Tinylicious
 
diff --git a/docs/versioned_docs/version-1/api/fluid-framework.mdx b/docs/versioned_docs/version-1/api/fluid-framework.mdx
@@ -5,7 +5,7 @@ sidebar_label: fluid-framework
 
 # fluid-framework Package
 
-The fluid-framework package bundles a collection of Fluid Framework client libraries for easy use when paired with a corresponding service client package (for example, [@fluidframework/azure-client](/docs/deployment/azure-frs) or [@fluidframework/tinylicious-client](/docs/testing/tinylicious)).
+The fluid-framework package bundles a collection of Fluid Framework client libraries for easy use when paired with a corresponding service client package (for example, [@fluidframework/azure-client](/docs/deployment/azure-fluid-relay) or [@fluidframework/tinylicious-client](/docs/testing/tinylicious)).
 
 The `fluid-framework` packages surfaces APIs from the following sub-packages.
 The following APIs can be referenced independently, but they can all be imported directly from the `fluid-framework` package:
diff --git a/docs/versioned_docs/version-1/api/index.mdx b/docs/versioned_docs/version-1/api/index.mdx
@@ -11,7 +11,7 @@ To get started with the Fluid Framework, you'll want to take a dependency on our
 You'll then want to pair that with the appropriate service client implementation based on your service.
 These include:
 
--   [@fluidframework/azure-client](./azure-client) (for use with [Azure Fluid Relay](../deployment/azure-frs))
+-   [@fluidframework/azure-client](./azure-client) (for use with [Azure Fluid Relay](../deployment/azure-fluid-relay))
 -   [@fluidframework/tinylicious-client](./tinylicious-client) (for testing with [Tinylicious](../testing/tinylicious))
 
 For more information on our service client implementations, see [Fluid Services](../deployment/service-options).
diff --git a/docs/versioned_docs/version-1/build/overview.mdx b/docs/versioned_docs/version-1/build/overview.mdx
@@ -25,7 +25,7 @@ See [Service-specific client libraries](#service-specific-client-libraries) for
 
 #### Azure Fluid Relay
 
-[Azure Fluid Relay](../deployment/azure-frs) is a cloud service that enables real-time collaboration on shared data models. It is a fully managed service that provides a secure, scalable, and reliable way to connect clients to each other and to the data models they share.
+[Azure Fluid Relay](../deployment/azure-fluid-relay) is a cloud service that enables real-time collaboration on shared data models. It is a fully managed service that provides a secure, scalable, and reliable way to connect clients to each other and to the data models they share.
 
 #### Tinylicious
 
@@ -68,6 +68,6 @@ Fluid works with multiple service implementations. Each service has a correspond
 For specifics about each service-specific client implementation see their corresponding documentation.
 
 -   The client library for the [Tinylicious](/docs/testing/tinylicious) service is in the package [@fluidframework/tinylicious-client](https://www.npmjs.com/package/@fluidframework/tinylicious-client).
--   The client library for the [Azure Fluid Relay](../deployment/azure-frs) is in the package [@fluidframework/azure-client](https://www.npmjs.com/package/@fluidframework/azure-client).
+-   The client library for the [Azure Fluid Relay](../deployment/azure-fluid-relay) is in the package [@fluidframework/azure-client](https://www.npmjs.com/package/@fluidframework/azure-client).
 
 For more information see [Packages](./packages).
diff --git a/docs/versioned_docs/version-1/deployment/azure-fluid-relay.mdx b/docs/versioned_docs/version-1/deployment/azure-fluid-relay.mdx
diff --git a/docs/versioned_docs/version-1/start/tutorial.mdx b/docs/versioned_docs/version-1/start/tutorial.mdx
@@ -47,7 +47,7 @@ const root = document.getElementById("content");
 
 :::note
 
-To create a Fluid application that can be deployed to Azure, check out the [Azure Fluid Relay](../deployment/azure-frs).
+To create a Fluid application that can be deployed to Azure, check out the [Azure Fluid Relay](../deployment/azure-fluid-relay).
 
 :::
 
diff --git a/docs/versioned_docs/version-1/testing/testing.mdx b/docs/versioned_docs/version-1/testing/testing.mdx
@@ -8,7 +8,7 @@ slug: /testing/testing
 
 ## Overview
 
-Testing and automation are crucial to maintaining the quality and longevity of your code. Internally, Fluid has a range of unit and integration tests powered by [Mocha](https://mochajs.org/), [Jest](https://jestjs.io/), [Puppeteer](https://github.com/puppeteer/puppeteer), and [webpack](https://webpack.js.org/). Tests that need to run against a service are backed by [Tinylicious](./tinylicious) or a test tenant of a [live service](../deployment/service-options) such as [Azure Fluid Relay](../deployment/azure-frs).
+Testing and automation are crucial to maintaining the quality and longevity of your code. Internally, Fluid has a range of unit and integration tests powered by [Mocha](https://mochajs.org/), [Jest](https://jestjs.io/), [Puppeteer](https://github.com/puppeteer/puppeteer), and [webpack](https://webpack.js.org/). Tests that need to run against a service are backed by [Tinylicious](./tinylicious) or a test tenant of a [live service](../deployment/service-options) such as [Azure Fluid Relay](../deployment/azure-fluid-relay).
 
 This document will explain how to use these tools to get started with writing automation for Fluid applications against a service. It will focus on interactions with the service rather than automation in general, and will not cover the automation tools themselves or scenarios that do not require a service.
 
@@ -38,7 +38,7 @@ The `test:tinylicious` script will start Tinylicious, wait until port 7070 respo
 
 ## Automation against Azure Fluid Relay
 
-Your automation can connect to a test tenant for Azure Fluid Relay in the same way as your production tenant and only needs the appropriate connection configuration. See [Connect to Azure Fluid Relay](../deployment/azure-frs) for more details.
+Your automation can connect to a test tenant for Azure Fluid Relay in the same way as your production tenant and only needs the appropriate connection configuration. See [Connect to Azure Fluid Relay](../deployment/azure-fluid-relay) for more details.
 
 ### Azure Fluid Relay as an abstraction for Tinylicious
 
diff --git a/packages/service-clients/end-to-end-tests/azure-client/README.md b/packages/service-clients/end-to-end-tests/azure-client/README.md
@@ -1,10 +1,11 @@
 # @fluidframework/azure-end-to-end-tests
 
-Functional end-to-end tests for FRS and Azure Local Service. Here we evaluate various scenarios that involving azure-client, IFluidContainer and a range of distributed data structures (DDSes).
+Functional end-to-end tests for Azure Fluid Relay (AFR) and Azure Local Service.
+Here we evaluate various scenarios involving `azure-client`, `IFluidContainer` and a range of distributed data structures (DDSes).
 
-To run FRS e2e tests: `test:realsvc:azure`.
+To run AFR end-to-end tests: `test:realsvc:azure`.
 
-To run Azure Local Service e2e tests: `test:realsvc`.
+To run Azure Local Service end-to-end tests: `test:realsvc`.
 
 <!-- AUTO-GENERATED-CONTENT:START (README_FOOTER) -->
 
diff --git a/packages/service-clients/end-to-end-tests/azure-client/src/test/AzureClientFactory.ts b/packages/service-clients/end-to-end-tests/azure-client/src/test/AzureClientFactory.ts
@@ -59,7 +59,7 @@ export function createAzureClient(
 	};
 	const endPoint = process.env.azure__fluid__relay__service__endpoint as string;
 	if (useAzure && endPoint === undefined) {
-		throw new Error("Azure FRS endpoint is missing");
+		throw new Error("Azure Fluid Relay service endpoint is missing");
 	}
 
 	// use AzureClient remote mode will run against live Azure Fluid Relay.
@@ -122,7 +122,7 @@ export function createAzureClientLegacy(
 	};
 	const endPoint = process.env.azure__fluid__relay__service__endpoint as string;
 	if (useAzure && endPoint === undefined) {
-		throw new Error("Azure FRS endpoint is missing");
+		throw new Error("Azure Azure Fluid Relay service endpoint is missing");
 	}
 
 	// use AzureClient remote mode will run against live Azure Fluid Relay.
@@ -189,7 +189,7 @@ export async function createContainerFromPayload(
 		? (process.env.azure__fluid__relay__service__endpoint as string)
 		: "http://localhost:7071";
 	if (useAzure && endPoint === undefined) {
-		throw new Error("Azure FRS endpoint is missing");
+		throw new Error("Azure Fluid Relay service endpoint is missing");
 	}
 
 	const tokenProvider = useAzure
diff --git a/packages/test/test-end-to-end-tests/src/test/blobs.spec.ts b/packages/test/test-end-to-end-tests/src/test/blobs.spec.ts
@@ -99,7 +99,7 @@ describeCompat("blobs", "FullCompat", (getTestObjectProvider, apis) => {
 	let provider: ITestObjectProvider;
 	beforeEach("getTestObjectProvider", async function () {
 		provider = getTestObjectProvider();
-		// Currently FRS does not support blob API.
+		// Currently, AFR does not support blob API.
 		if (provider.driver.type === "routerlicious" && provider.driver.endpointName === "frs") {
 			this.skip();
 		}
@@ -295,7 +295,7 @@ describeCompat("blobs", "NoCompat", (getTestObjectProvider, apis) => {
 	beforeEach("getTestObjectProvider", async function () {
 		testPersistedCache = new TestPersistedCache();
 		provider = getTestObjectProvider({ persistedCache: testPersistedCache });
-		// Currently FRS does not support blob API.
+		// Currently AFR does not support blob API.
 		if (provider.driver.type === "routerlicious" && provider.driver.endpointName === "frs") {
 			this.skip();
 		}
diff --git a/packages/test/test-end-to-end-tests/src/test/idCompressor.spec.ts b/packages/test/test-end-to-end-tests/src/test/idCompressor.spec.ts
@@ -902,7 +902,7 @@ describeCompat("IdCompressor Summaries", "NoCompat", (getTestObjectProvider, com
 	});
 
 	it("Newly connected container synchronizes from summary", async function () {
-		// TODO: This test is consistently failing when ran against FRS. See ADO:7931
+		// TODO: This test is consistently failing when ran against AFR. See ADO:7931
 		if (provider.driver.type === "routerlicious" && provider.driver.endpointName === "frs") {
 			this.skip();
 		}
diff --git a/packages/test/test-end-to-end-tests/src/test/refreshSerializedStateManager.spec.ts b/packages/test/test-end-to-end-tests/src/test/refreshSerializedStateManager.spec.ts
@@ -75,7 +75,7 @@ describeCompat("Snapshot refresh at loading", "NoCompat", (getTestObjectProvider
 
 	it("snapshot was refreshed", async function () {
 		const provider = getTestObjectProvider();
-		// TODO: This test is consistently failing when ran against FRS. See ADO:7893
+		// TODO: This test is consistently failing when ran against AFR. See ADO:7893
 		if (provider.driver.type === "routerlicious" && provider.driver.endpointName === "frs") {
 			this.skip();
 		}
@@ -141,7 +141,7 @@ describeCompat("Snapshot refresh at loading", "NoCompat", (getTestObjectProvider
 
 	it("snapshot was refreshed after some time", async function () {
 		const provider = getTestObjectProvider();
-		// TODO: This test is consistently failing when ran against FRS. See ADO:7893
+		// TODO: This test is consistently failing when ran against AFR. See ADO:7893
 		if (provider.driver.type === "routerlicious" && provider.driver.endpointName === "frs") {
 			this.skip();
 		}
diff --git a/packages/test/test-end-to-end-tests/src/test/stashedOps.spec.ts b/packages/test/test-end-to-end-tests/src/test/stashedOps.spec.ts
diff --git a/packages/test/test-service-load/README.md b/packages/test/test-service-load/README.md
diff --git a/tools/pipelines/test-real-service-stress.yml b/tools/pipelines/test-real-service-stress.yml
diff --git a/tools/pipelines/test-real-service.yml b/tools/pipelines/test-real-service.yml
diff --git a/tools/pipelines/test-service-clients.yml b/tools/pipelines/test-service-clients.yml

Original file line number	Diff line number	Diff line change
`@@ -902,7 +902,7 @@ describeCompat("IdCompressor Summaries", "NoCompat", (getTestObjectProvider, com`
`902`	`902`	`});`
`903`	`903`
`904`	`904`	`it("Newly connected container synchronizes from summary", async function () {`
`905`		`- // TODO: This test is consistently failing when ran against FRS. See ADO:7931`
	`905`	`+ // TODO: This test is consistently failing when ran against AFR. See ADO:7931`
`906`	`906`	`if (provider.driver.type === "routerlicious" && provider.driver.endpointName === "frs") {`
`907`	`907`	`this.skip();`
`908`	`908`	`}`