Merge branch 'MicrosoftDocs:main' into main

Author: christineruana

.github/workflows/whats-new.yml

@@ -18,7 +18,7 @@ jobs:
       pull-requests: write
 
     steps:
-      - uses: actions/checkout@3df4ab11eba7bda6032a0b82a6bb43b11571feac
+      - uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608
 
       - name: "Print manual run reason"
         if: ${{ github.event_name == 'workflow_dispatch' }}

.openpublishing.redirection.json

@@ -12,7 +12,7 @@ description: Learn how to use Bridge to Kubernetes to connect your development c
 
 # Use Bridge to Kubernetes with AKS
 
-In this tutorial, you'll use a specific AKS sample microservices web app to learn how to use Bridge to Kubernetes to debug locally in a single pod that's part of an Azure Kubernetes Service (AKS) cluster.
+In this tutorial, you use a specific AKS sample microservices web app to learn how to use Bridge to Kubernetes to debug locally in a single pod that's part of an Azure Kubernetes Service (AKS) cluster.
 
 ## Before you begin
 
@@ -27,7 +27,7 @@ This guide uses the [Todo App sample application](https://github.com/Azure/Bridg
 
 ## Create a Kubernetes cluster
 
-Create an AKS cluster in a [supported region][supported-regions]. The below commands create a resource group called `MyResourceGroup` and an AKS cluster called `MyAKS`.
+Create an AKS cluster in a [supported region][supported-regions]. The following commands create a resource group called `MyResourceGroup` and an AKS cluster called `MyAKS`.
 
 ```azurecli-interactive
 az group create \
@@ -46,14 +46,14 @@ az aks create \
 Download the code and install dependencies
 
 ```azurecli-interactive
-git clone https://github.com/Microsoft/mindaro
-cd mindaro/samples/todo-app
+git clone https://github.com/Azure/Bridge-To-Kubernetes
+cd Bridge-To-Kubernetes/samples/todo-app
 npm install stats-api\
 ```
 
 ## Connect to your cluster and deploy the app
 
-On your development computer, download and configure the Kubernetes CLI to connect to your Kubernetes cluster using [az aks get-credentials][az-aks-get-credentials].
+On your development computer, download and configure the Kubernetes CLI to connect to your Kubernetes cluster using [`az aks get-credentials`][az-aks-get-credentials].
 
 ```azurecli
 az aks get-credentials --resource-group MyResourceGroup --name MyAKS
@@ -64,18 +64,18 @@ kubectl apply -f deployment.yaml --namespace todo-app
 
 ## Try out the app
 
-On the same terminal you were using earlier run below command and copy the IP for front end service under the External IP columnd.
+On the same terminal you were using earlier, run the following command and copy the IP for front end service under the External IP column.
 
 ```azurecli
 kubectl get services
 ```
 
 To try out the app, open the url:
-(your external IP from above command goes here).nip.io
+`{your external IP from above command goes here}.nip.io`
 
 ## Debug stats-api service
 
-On the same terminal you were using earlier type below ot open stats-api in vscode.
+On the same terminal you were using earlier, type the following command to open stats-api in VS Code.
 
 ```azurecli
 code ./stats-api
@@ -91,7 +91,7 @@ Next, configure bridge: open the Command Palette (**CTRL**+**SHIFT**+**P** or **
 
 ![Screenshot showing the Bridge to Kubernetes Configure command window.](media/bridge-to-kubernetes-sample/bridge-configure.png)
 
-You are prompted to configure the service you want to replace, the port to forward from your development computer, and the launch task to use.
+You're prompted to configure the service you want to replace, the port to forward from your development computer, and the launch task to use.
 
 Choose the `stats-api` service.
 
@@ -100,15 +100,15 @@ Choose the `stats-api` service.
 > [!IMPORTANT]
 > You can only redirect services that have a single pod.
 
-After you select your service, you are prompted to enter the TCP port for your local application. For this example, enter 3001.
+After you select your service, you're prompted to enter the TCP port for your local application. For this example, enter 3001.
 
 ![Screenshot showing the enter the port number window.](media/bridge-to-kubernetes-sample/enter-port.png)
 
 Choose **Run Script: dev** as the launch task.
 
 ![Screenshot showing the choose the debugger launch task window.](media/bridge-to-kubernetes-sample/launch-task.png)
 
-You have the option of running isolated or not isolated. If you run isolated, only your requests are routed to your local process; other developers can use the cluster without being affected. If you don't run isolated, all traffic is redirected to your local process. For more information on this option, see [Using routing capabilities for developing in isolation](overview-bridge-to-kubernetes.md#using-routing-capabilities-for-developing-in-isolation). For this example, we will proceed with non-isolated. If you chose isolation, task.json will have the prefix you should use to route request to your machine.
+You have the option of running isolated or not isolated. If you run isolated, only your requests are routed to your local process; other developers can use the cluster without being affected. If you don't run isolated, all traffic is redirected to your local process. For more information on this option, see [Using routing capabilities for developing in isolation](overview-bridge-to-kubernetes.md#using-routing-capabilities-for-developing-in-isolation). For this example, we proceed with non-isolated. If you chose isolation, task.json has the prefix you should use to route request to your machine.
 
 ![Screenshot showing the choose isolation option window.](media/bridge-to-kubernetes-sample/isolation.png)
 
@@ -124,11 +124,11 @@ To start debugging, select the Debug icon on the left and select **Run Script: d
 > [!NOTE]
 > You will be prompted to allow the EndpointManager to run elevated and modify your hosts file.
 
-Your development computer is connected when the VS Code status bar turns orange and the Kubernetes extension shows you are connected. Once your development computer is connected, traffic starts redirecting to your development computer for the stats-api you are replacing.
+Your development computer is connected when the VS Code status bar turns orange and the Kubernetes extension shows you're connected. Once your development computer is connected, traffic starts redirecting to your development computer for the stats-api you're replacing.
 
 ![Screenshot showing the choose the debugging with Bridge to Kubernetes window.](media/bridge-to-kubernetes-sample/debugging.png)
 
-Navigate to the frontend entry point of your todo-app. Using that external IP you found earlier (your external IP from get services command).nip.io. Note, if you selected isolation mode, you will need to use (your prefix - can be found in task.json).(your external IP from get services command).nip.io.
+Navigate to the frontend entry point of your todo-app. Using that external IP you found earlier `{your external IP from get services command}.nip.io`. Note, if you selected isolation mode, you need to use `{your prefix - can be found in task.json}.{your external IP from get services command}.nip.io`.
 
 Make a request to the stats-api by choosing the **stats** link.
 
@@ -140,9 +140,9 @@ Press play and let the request continue complete transparently.
 
 ## Clean up
 
-When you stop the debugger all changes to the cluster are reverted. Note, if you were running with isolation on, the routing manager pod will be left there to expedite the start of the debugger the next time around.
+When you stop the debugger, all changes to the cluster are reverted. Note, if you were running with isolation on, the routing manager pod will be left there to expedite the start of the debugger the next time around.
 
-You can leave your AKS cluster on for future debugging or you can delete it with below command.
+You can leave your AKS cluster on for future debugging or you can delete it with following command.
 
 ```azurecli-interactive
 az aks delete --name MyAKS --resource-group MyResourceGroup
@@ -160,9 +160,7 @@ Learn more about Bridge to Kubernetes at [How Bridge to Kubernetes works][btk-ho
 [azure-cloud-shell]: /azure/cloud-shell/overview
 [az-aks-get-credentials]: /cli/azure/aks?view=azure-cli-latest&preserve-view=true#az-aks-get-credentials
 [az-aks-vs-code]: https://marketplace.visualstudio.com/items?itemName=ms-kubernetes-tools.vscode-aks-tools
-[bike-sharing-github]: https://github.com/Microsoft/mindaro
 [preview-terms]: https://azure.microsoft.com/support/legal/preview-supplemental-terms/
-[server-js-breakpoint]: https://github.com/Microsoft/mindaro/blob/master/samples/BikeSharingApp/Bikes/server.js#L233
 [supported-regions]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service
 [troubleshooting]: /azure/dev-spaces/troubleshooting#fail-to-restore-original-configuration-of-deployment-on-cluster
 [vs-code]: https://code.visualstudio.com/download

.openpublishing.redirection.vs2017.json

@@ -6,7 +6,7 @@ manager: jmartens
 ms.technology: bridge
 ms.custom: "contperf-fy22q1"
 title: Use Bridge to Kubernetes to run and debug locally with Kubernetes (VS Code)
-ms.date: 08/11/2022
+ms.date: 09/14/2023
 description: Learn how to use Bridge to Kubernetes to connect your development computer to a Kubernetes cluster and use local tunnel debugging to debug Kubernetes services on your local machine.
 ---
 
@@ -146,7 +146,7 @@ var response = await client.SendAsync(request);
 > [!NOTE]
 > To avoid affecting code at every request, you can create a class that inherits from [System.Net.Http.DelegatingHandler](/dotnet/api/system.net.http.delegatinghandler) and override the `SendAsync` method with code similar to the preceding example. You can find code using this technique on the web; one example is [Properly Propagating "kubernetes-route-as" in Bridge to Kubernetes](https://blogs.u2u.be/lander/post/2020/11/25/properly-propagating-kubernetes-route-as-in-bridge-to-kubernetes).
 
-For Node.js services, you can use code similar to the following, taken from the todo-app sample in the [mindaro repo](https://github.com/Microsoft/mindaro):
+For Node.js services, you can use code similar to the following, taken from the todo-app sample in the [Bridge to Kubernetes repo](https://github.com/Azure/Bridge-To-Kubernetes):
 
 ```js
     server.get("/api/stats", function (req, res) {

bridge/articles/bridge-to-kubernetes-aks.md

@@ -17,7 +17,9 @@ landingContent:
     linkLists:
       - linkListType: overview
         links:
-          - text: Develop Azure applications with Visual Studio
+          - text: Develop Azure applications
+            url: overview.md
+          - text: Work with Azure
             url: overview-azure-integration.md
           - text: Azure SDK for .NET
             url: /dotnet/azure

bridge/articles/bridge-to-kubernetes-vs-code.md

@@ -1,6 +1,6 @@
 ---
-title: Azure development with Visual Studio
-description: Learn about how you can connect your apps to Azure services in Visual Studio and deploy them to the cloud.
+title: Work with Azure with Visual Studio
+description: Learn about how you can provision Azure resources, browse existing Azure resources, and deploy applications to Azure services with Visual Studio.
 author: ghogen
 manager: jmartens
 ms.technology: vs-azure
@@ -11,7 +11,7 @@ ms.date: 10/19/2021
 ms.author: ghogen
 monikerRange: ">=vs-2019"
 ---
-# About Azure development in Visual Studio
+# Work with Azure in Visual Studio
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 

docs/azure/index.yml

@@ -34,6 +34,7 @@ Get started by right-clicking on the project node, and choosing **Add > Connecte
 Supported project types vary by the type of service. You'll see the options that apply to your project type in the listed selections.
 
 <a name="azure"/>
+
 ## Connect your app to Azure services
 
 Use Connected Services to connect your application to live Azure services emulators and other local alternatives to Azure services. Visual Studio currently supports the following:
@@ -55,20 +56,21 @@ Use Connected Services to connect your application to live Azure services emulat
 > [!NOTE]
 > Using Publish you can deploy your application to Azure hosting services like Azure VMs, Azure App Service, Azure Functions and Azure Container Registry
 
-### Support for Azure emulators and local alternatives
-
-Visual Studio makes it easier to develop Azure applications locally by easing the transition from locally emulated services to services running in the cloud. You can use Connected Services to connect your application to local emulators, some of which run in a local container, and other local alternatives to Azure services. Visual Studio currently supports the following:
+## Databases and data providers
 
+Visual Studio provides options to connect to on-premises databases, locally emulated versions of data providers, as well as Azure database services.
 
-## Connect your app to gRPC, OpenAPI and WCF endpoints
+| Name | Description |
+| - | - |
+| [Azure Cosmos DB Emulator on container](/azure/cosmos-db/introduction) | Azure Cosmos DB emulator running in a local container. |
+| [MongoDB on container](/azure/cosmos-db/introduction) | MongoDB document databases provides high reliability and easy scalability. This option makes it available in a local container. |
+| [PostgreSQL on container](/azure/postgresql/overview) | PostgreSQL is an object-relational database system that provides reliability and data integrity. This option makes it available in a local container. |
+| [SQLite](/ef/core/providers/sqlite/?tabs=dotnet-core-cli) | SQLite is an in-process library that provides a self-contained, transactional SQL database engine with no configuration. |
+| [SQL Server Database](/sql/sql-server/) | On-premises SQL Server Database. |
 
-Use Connected Services to connect your application to any of the following services:
+## Support for Azure emulators and local alternatives
 
-| Name | ASP.NET Link | Description |
-|-|-|-|
-| [OpenAPI](https://github.com/OAI/OpenAPI-Specification) endpoints | [Develop ASP.NET Core apps with OpenAPI](/aspnet/core/web-api/Microsoft.dotnet-openapi) | A standard format for describing the capabilities of a service in computer-readable and human-readable form. |
-| [gRPC](https://grpc.io/docs/) endpoints | [Introduction to gRPC services on .NET](/aspnet/core/grpc/) | An open-source real-time procedure calling service. |
-| [WCF](/dotnet/framework/wcf/) endpoints | n/a | A .NET Framework solution supporting programming with a distributed network of services. |
+Visual Studio makes it easier to develop Azure applications locally by easing the transition from locally emulated services to services running in the cloud. You can use Connected Services to connect your application to local emulators, some of which run in a local container, and other local alternatives to Azure services. Visual Studio currently supports the following:
 
 Visual Studio generates any necessary client or server code to facilitate the communication.
 
@@ -82,23 +84,15 @@ Visual Studio generates any necessary client or server code to facilitate the co
 | [Secrets.json](/aspnet/core/security/app-secrets?tabs=windows) | Local alternative for Key Vault. |
 | [SQL Server Express LocalDB](/sql/database-engine/configure-windows/sql-server-express-localdb) | Local alternative to Azure SQL Database. |
 
-## Databases and data providers
-
-Visual Studio provides options to connect to on-premises databases, locally emulated versions of data providers, as well as Azure database services.
-
-| Name | Description |
-| - | - |
-| [Azure Cosmos DB Emulator on container](/azure/cosmos-db/introduction) | Azure Cosmos DB emulator running in a local container. |
-| [MongoDB on container](/azure/cosmos-db/introduction) | MongoDB document databases provides high reliability and easy scalability. This option makes it available in a local container. |
-| [PostgreSQL on container](/azure/postgresql/overview) | PostgreSQL is an object-relational database system that provides reliability and data integrity. This option makes it available in a local container. |
-| [SQLite](/ef/core/providers/sqlite/?tabs=dotnet-core-cli) | SQLite is an in-process library that provides a self-contained, transactional SQL database engine with no configuration. |
-| [SQL Server Database](/sql/sql-server/) | On-premises SQL Server Database. |
-
-## How it works
+## Connect your app to gRPC, OpenAPI and WCF endpoints
 
-Visual Studio creates two new files visible in Solution Explorer under Properties called *serviceDependencies.json* and *serviceDependencies.local.json*. Both of these files are safe to check in as they do not contain any secrets.
+Use Connected Services to connect your application to any of the following services:
 
-Visual Studio also creates a file called *serviceDependencies.local.json.user* which is not visible in Solution Explorer by default. This file contains information that could be considered a secret (for example, resource IDs in Azure) and we do not recommend you check it in.
+| Name | ASP.NET Link | Description |
+|-|-|-|
+| [OpenAPI](https://github.com/OAI/OpenAPI-Specification) endpoints | [Develop ASP.NET Core apps with OpenAPI](/aspnet/core/web-api/Microsoft.dotnet-openapi) | A standard format for describing the capabilities of a service in computer-readable and human-readable form. |
+| [gRPC](https://grpc.io/docs/) endpoints | [Introduction to gRPC services on .NET](/aspnet/core/grpc/) | An open-source real-time procedure calling service. |
+| [WCF](/dotnet/framework/wcf/) endpoints | n/a | A .NET Framework solution supporting programming with a distributed network of services. |
 
 ## Containers
 
@@ -113,3 +107,9 @@ During development, you usually use a local emulator, a local database, or a moc
 If you click those links, Visual Studio will present a few screens that ask for the connection information to the "real" service running in the cloud that your cloud app will use instead of the local service. For example, if you initially configured an app to run with a locally running instance of SQL LocalDB, you would have provided a connection string name and an initial value that referenced that LocalDB database. After your app is first deployed to a cloud environment, you can use the **Configure** links to specify the connection string to use in the cloud. For Azure deployment scenarios, Visual Studio also gives the option of using an [Azure Key Vault](/azure/key-vault/general/overview) to securely store the connection string and other secrets.
 
 ![Screenshot showing the options presented to replace the SQL LocalDB service with a real database connection.](media/vs-2022/configure-dependency.png)
+
+## How it works
+
+Visual Studio creates two new files visible in Solution Explorer under Properties called *serviceDependencies.json* and *serviceDependencies.local.json*. Both of these files are safe to check in as they do not contain any secrets.
+
+Visual Studio also creates a file called *serviceDependencies.local.json.user* which is not visible in Solution Explorer by default. This file contains information that could be considered a secret (for example, resource IDs in Azure) and we do not recommend you check it in.