Merge pull request #283702 from mumian/0806-bicep-extension-name

rename bicep extension name

Author: v-dirichards

.openpublishing.redirection.azure-resource-manager.json

@@ -2004,6 +2004,11 @@
       "source_path": "articles/azure-resource-manager/bicep/bicep-error-bcp333.md",
       "redirect_url": "diagnostics/bcp333",
       "redirect_document_id": false
-    }
+    },
+    {
+      "source_path_from_root": "/articles/azure-resource-manager/bicep/bicep-extensibility-kubernetes-provider.md",
+      "redirect_url": "/azure/azure-resource-manager/bicep/bicep-kubernetes-extension",
+      "redirect_document_id": false
+    }    
   ]
 }

articles/azure-resource-manager/bicep/bicep-import.md

@@ -3,16 +3,16 @@ title: Imports in Bicep
 description: Describes how to import shared functionality and namespaces in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/03/2024
+ms.date: 08/07/2024
 ---
 
 # Imports in Bicep
 
-This article describes the syntax you use to export and import shared functionality, as well as namespaces for Bicep extensibility providers.
+This article describes the syntax you use to export and import shared functionality, as well as namespaces for Bicep extensions.
 
 ## Exporting types, variables and functions
 
-The `@export()` decorator is used to indicate that a given statement can be imported by another file. This decorator is only valid on type, variable and function statements. Variable statements marked with `@export()` must be compile-time constants.
+The `@export()` decorator indicates that a given statement can be imported by another file. This decorator is only valid on type, variable, and function statements. Variable statements marked with `@export()` must be compile-time constants.
 
 The syntax for exporting functionality for use in other Bicep files is:
 
@@ -21,7 +21,7 @@ The syntax for exporting functionality for use in other Bicep files is:
 <statement_to_export>
 ```
 
-## Import types, variables and functions
+## Import types, variables, and functions
 
 The syntax for importing functionality from another Bicep file is:
 
@@ -80,7 +80,7 @@ output greeting string = sayHello('Bicep user')
 output exampleObject myImports.myObjectType = exampleObject
 ```
 
-## Import namespaces and extensibility providers (Preview)
+## Import namespaces and extensions (Preview)
 
 > [!NOTE]
 > The experimental feature `extensibility` must be enabled from the [Bicep config file](./bicep-config.md#enable-experimental-features) to use this feature.
@@ -92,27 +92,27 @@ import '[email protected]'
 import '[email protected]'
 ```
 
-Both `az` and `sys` are Bicep built-in namespaces. They are imported by default. For more information about the data types and the functions defined in `az` and `sys`, see [Data types](./data-types.md) and  [Bicep functions](./bicep-functions.md).
+Both `az` and `sys` are Bicep built-in namespaces. They're imported by default. For more information about the data types and the functions defined in `az` and `sys`, see [Data types](./data-types.md) and  [Bicep functions](./bicep-functions.md).
 
-The syntax for importing Bicep extensibility providers is:
+The syntax for importing Bicep extensions is:
 
 ```bicep
-import '<provider-name>@<provider-version>'
+import '<extension-name>@<extension-version>'
 ```
 
-The syntax for importing Bicep extensibility providers which require configuration is:
+The syntax for importing Bicep extensions, which require configuration is:
 
 ```bicep
-import '<provider-name>@<provider-version>' with {
-  <provider-properties>
+import '<extension-name>@<extension-version>' with {
+  <extension-properties>
 }
 ```
 
-For an example, see [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
+For an example, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
 
 ## Next steps
 
 - To learn about the Bicep data types, see [Data types](./data-types.md).
 - To learn about the Bicep functions, see [Bicep functions](./bicep-functions.md).
-- To learn about how to use the Kubernetes provider, see [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
-- To go through a Kubernetes provider tutorial, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes provider.](/azure/aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider).
+- To learn about how to use the Bicep Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
+- To go through a Kubernetes extension tutorial, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension.](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).

articles/azure-resource-manager/bicep/bicep-extensibility-kubernetes-provider.md renamed to articles/azure-resource-manager/bicep/bicep-kubernetes-extension.md

@@ -1,17 +1,17 @@
 ---
-title: Bicep extensibility Kubernetes provider
-description: Learn how to Bicep Kubernetes provider  to deploy .NET applications to Azure Kubernetes Service clusters.
+title: Bicep Kubernetes extension
+description: Learn how to Bicep Kubernetes extension to deploy .NET applications to Azure Kubernetes Service clusters.
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-dotnet
-ms.date: 07/11/2024
+ms.date: 08/07/2024
 ---
 
-# Bicep extensibility Kubernetes provider (Preview)
+# Bicep Kubernetes extension (Preview)
 
-The Kubernetes provider allows you to create Kubernetes resources directly with Bicep. Bicep can deploy anything that can be deployed with the [Kubernetes command-line client (kubectl)](https://kubernetes.io/docs/reference/kubectl/kubectl/) and a [Kubernetes manifest file](/azure/aks/concepts-clusters-workloads#deployments-and-yaml-manifests).
+The Kubernetes extension allows you to create Kubernetes resources directly with Bicep. Bicep can deploy anything that can be deployed with the [Kubernetes command-line client (kubectl)](https://kubernetes.io/docs/reference/kubectl/kubectl/) and a [Kubernetes manifest file](/azure/aks/concepts-clusters-workloads#deployments-and-yaml-manifests).
 
 > [!NOTE]
-> Kubernetes provider is not currently supported for private clusters:
+> The Kubernetes extension is not currently supported for private clusters:
 > 
 > ```bicep
 > resource AKS 'Microsoft.ContainerService/managedClusters@2024-02-01' = {
@@ -38,12 +38,12 @@ This preview feature can be enabled by configuring the [bicepconfig.json](./bice
 }
 ```
 
-## Import Kubernetes provider
+## Import Kubernetes extension
 
 To safely pass secrets for the Kubernetes deployment, you must invoke the Kubernetes code with a Bicep module and pass the parameter as a secret.
-To import the Kubernetes provider, use the [import statement](./bicep-import-providers.md). After importing the provider, you can refactor the Bicep module file as usual, such as by using variables, parameters, and output. By contract, the Kubernetes manifest in YML doesn't include any programmability support.
+To import the Kubernetes extension, use the [import statement](./bicep-import.md). After importing the extension, you can refactor the Bicep module file as usual, such as by using variables, parameters, and output. By contract, the Kubernetes manifest in YML doesn't include any programmability support.
 
-The following sample imports the Kubernetes provider:
+The following sample imports the Kubernetes extension:
 
 ```bicep
 @secure()
@@ -55,7 +55,7 @@ import '[email protected]' with {
 } as k8s
 ```
 
-- **namespace**: Specify the namespace of the provider.
+- **namespace**: Specify the namespace of the extension.
 - **KubeConfig**: Specify a base64 encoded value of the [Kubernetes cluster admin credentials](/rest/api/aks/managed-clusters/list-cluster-admin-credentials).
 
 The following sample shows how to pass `kubeConfig` value from a parent Bicep file:
@@ -81,4 +81,4 @@ From Visual Studio Code, you can import Kubernetes manifest files to create Bice
 
 ## Next steps
 
-- [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep extensibility Kubernetes provider](/azure/aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider)
+- [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension)

articles/azure-resource-manager/bicep/toc.yml

@@ -413,9 +413,9 @@
       href: deployment-stacks.md
     - name: Bicep extensibility
       items:
-      - name: Kubernetes provider
-        href: ./bicep-extensibility-kubernetes-provider.md
-      - name: Microsoft Graph provider
+      - name: Kubernetes extension
+        href: ./bicep-kubernetes-extension.md
+      - name: Microsoft Graph extension
         href: https://aka.ms/graphbicep
     - name: Patterns
       items: