From 02a1d2cfffc0b026b55a7af035deee3a01c763c1 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 13:23:16 -0500 Subject: [PATCH 01/21] New commands overview doc --- articles/azure-developer-cli/TOC.yml | 2 + articles/azure-developer-cli/azd-commands.md | 69 ++++++++++++++++++++ 2 files changed, 71 insertions(+) create mode 100644 articles/azure-developer-cli/azd-commands.md diff --git a/articles/azure-developer-cli/TOC.yml b/articles/azure-developer-cli/TOC.yml index df968d926..b512ea681 100644 --- a/articles/azure-developer-cli/TOC.yml +++ b/articles/azure-developer-cli/TOC.yml @@ -9,6 +9,8 @@ items: - name: Install or update azd href: install-azd.md + - name: What are Azure Developer CLI commands? + href: azd-commands.md - name: What are Azure Developer CLI templates? href: azd-templates.md - name: Quickstart - Deploy an azd template diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md new file mode 100644 index 000000000..285c5d749 --- /dev/null +++ b/articles/azure-developer-cli/azd-commands.md @@ -0,0 +1,69 @@ +--- +title: Understanding Azure Developer CLI Commands +description: This article provides an in-depth conceptual overview of Azure Developer CLI commands, explores commonly used commands, and explains their relationship with Azure Developer CLI templates. +ms.topic: conceptual +ms.date: 01/15/2025 +--- + +# Explore Azure Developer CLI commands overview + +Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and streamline the development, deployment, and management of applications on Azure. These commands provide developers with a powerful and flexible way to interact with Azure services directly from the command line, enabling automation and integration into various development workflows. In this article you'll learn about the following: + +- Key concepts about `azd` commands +- How `azd` commands and templates are related +- Commonly used `azd` commands + +## What are Azure Developer CLI commands? + +The Azure Developer CLI provides a set of commands such as `azd up` and `azd init` that leverage the `azd` template system and perform other tasks. Conceptually, Azure Developer CLI commands are designed to abstract away the complexities of managing Azure resources and services. They streamline the end-to-end developer workflow and provide high-level commands that map to common developer tasks or workflow stages. + +This emphasis on high level development stages differentiates `azd` commands from other tools such as the Azure CLI or Azure PowerShell. Whereas those tools offer commands that focus on granular control over Azure resources and specific configurations, `azd` commands automate broader development tasks such as provisioning an entire set of services at once, or deploying an entire app. `azd` commands are able to perform these broader tasks due to their integration with the `azd` template system, which is covered in the next section. THe following table highlights the differences between `azd` commands and similar Azure command line tools: + +| Tool | Sample Command | Outcome | +|---------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| Azure CLI | `az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name myWebApp` | Provisions a new web app in the specified resource group and app service plan. | +| Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new web app in the specified resource group and app service plan. | +| Azure Developer CLI | `azd provision` | Provisions the necessary Azure infrastructure, including a web app, based on the project configuration. | + +`azd` aims to enhance the developer experience by reducing the complexity of managing Azure resources. It abstracts away many of the low-level details, allowing developers to focus more on creating and deploying app features rather than managing infrastructure. + +## The relationship between Azure Developer CLI commands and templates + +[Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to structural `azd` conventions and include sample application code, infrastructure files, as well as `azd` configuration files. Most `azd` templates include the following: + +- **`infra` folder** - Contains all of the Bicep or Terraform infrastructure as code files for the `azd` template. +- **`azure.yaml` file** - A configuration file that defines one or more services in your project and maps them to Azure resources defined in the `infra` folder for deployment. +- **`.azure` folder** - Contains essential Azure configurations and environment variables, such as the location to deploy resources or other subscription information. +- **`src` folder** - Contains all of the deployable app source code. + +:::image type="content" source="media/make-azd-compatible/azd-template-structure.png" alt-text="A screenshot showing an Azure Developer CLI template structure."::: + +Without `azd` commands, these templates are just standard code repositories. In essence, Azure Developer CLI templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications. For example, `azd` commands leverage the conventional structure of these templates to perform actions and handle the following concerns: + +- **Project Initialization**: `azd init` sets up a new or existing project with a predefined structure and configuration. +- **Infrastructure Provisioning**: `azd up` or `azd provision` uses infrastructure-as-code templates in the `infra` folder to automate the creation of Azure resources. +- **Code Deployment**: `azd up` or `azd deploy` handle the deployment of application code in the `src` folder (configurable) to the provisioned infrastructure. +- **Pipeline configuration**: `azd pipelie config` uses workflow configuration files in the `.github` or `.ado` folders to create a CI/CD pipeline for your app via GitHub Actions or Azure Pipelines with a single command. +- **Monitoring and Management**: `azd monitor` assists with monitoring the health and performance of the deployed application by hooking into Azure monitoring features. + +## Commonly used commands + +`azd` commands provide a wide variety of features and functionality. Visit the [Azure Developer CLI commands](/azure/developer/azure-developer-cli/reference) reference page for a complete list of `azd` commands, parameters and their functionality. Some of the most commonly used commands include: + +- **`azd init`**: Initializes a new Azure Developer CLI project with a predefined structure and configuration. This command sets up the necessary files and directories to start a new project. +- **`azd up`**: Provisions the necessary Azure resources and deploys the application in one step. This command combines the provisioning and deployment processes to quickly get your application running on Azure. +- **`azd provision`**: Provisions the required Azure infrastructure based on infrastructure-as-code templates. This command creates the necessary Azure resources such as VMs, databases, and storage accounts. +- **`azd deploy`**: Deploys the application code to the provisioned Azure infrastructure. This command handles the deployment of your application code to the resources created by the `azd provision` command. +- **`azd monitor`**: Monitors the health and performance of the deployed application. This command provides insights into the application's performance and helps identify any issues. +- **`azd pipeline config`**: Configures a CI/CD pipeline for the project. This command sets up continuous integration and continuous deployment pipelines to automate the build and deployment processes. +- **`azd down`**: De-provisions the Azure resources created by the project. This command removes the Azure resources that were provisioned, helping to clean up and avoid unnecessary costs. +- **`azd env list`**: Lists all the environments for the project. This command shows all the different environments (e.g., development, staging, production) that have been set up for the project. +- **`azd env new`**: Creates a new environment for the project. This command sets up a new environment with its own configuration and resources, allowing you to manage multiple environments for different stages of development. +- **`azd config list`**: Lists the configuration settings for the project. This command shows all the configuration settings that have been applied to the project. +- **`azd config set`**: Sets a configuration setting for the project. This command allows you to update or add a new configuration setting. +- **`azd config get`**: Gets the value of a configuration setting for the project. This command retrieves the current value of a specific configuration setting. + +## Next steps + +> [!div class="nextstepaction"] +> [What are Azure Developer CLI templates?](./azd-templates.md) From 0309e6022050d328cab8bffd2c55a111474e562a Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 14:23:39 -0500 Subject: [PATCH 02/21] refactor --- articles/azure-developer-cli/azd-commands.md | 29 ++++++++++---------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index 285c5d749..2282f431e 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -7,7 +7,7 @@ ms.date: 01/15/2025 # Explore Azure Developer CLI commands overview -Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and streamline the development, deployment, and management of applications on Azure. These commands provide developers with a powerful and flexible way to interact with Azure services directly from the command line, enabling automation and integration into various development workflows. In this article you'll learn about the following: +Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and streamline the development, deployment, and management of applications on Azure. In this article you'll learn the following: - Key concepts about `azd` commands - How `azd` commands and templates are related @@ -15,30 +15,30 @@ Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and ## What are Azure Developer CLI commands? -The Azure Developer CLI provides a set of commands such as `azd up` and `azd init` that leverage the `azd` template system and perform other tasks. Conceptually, Azure Developer CLI commands are designed to abstract away the complexities of managing Azure resources and services. They streamline the end-to-end developer workflow and provide high-level commands that map to common developer tasks or workflow stages. +The Azure Developer CLI provides a set of commands such as `azd up` and `azd init` that leverage the `azd` template system to automate developer workflows and perform other tasks. Conceptually, `azd` commands are designed to abstract away the complexities of managing Azure resources and services. They streamline the end-to-end developer workflow and provide high-level commands that map to common developer tasks or workflow stages. -This emphasis on high level development stages differentiates `azd` commands from other tools such as the Azure CLI or Azure PowerShell. Whereas those tools offer commands that focus on granular control over Azure resources and specific configurations, `azd` commands automate broader development tasks such as provisioning an entire set of services at once, or deploying an entire app. `azd` commands are able to perform these broader tasks due to their integration with the `azd` template system, which is covered in the next section. THe following table highlights the differences between `azd` commands and similar Azure command line tools: +This emphasis on high level development stages differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools offer commands that focus on granular control over individual Azure resources and specific configurations, `azd` commands automate broader development tasks such as provisioning an entire set of services at once, or packaging and deploying multiple services at once. The following table provides an example of the differences between `azd` commands and other Azure command line tools: | Tool | Sample Command | Outcome | |---------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| | Azure CLI | `az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name myWebApp` | Provisions a new web app in the specified resource group and app service plan. | -| Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new web app in the specified resource group and app service plan. | -| Azure Developer CLI | `azd provision` | Provisions the necessary Azure infrastructure, including a web app, based on the project configuration. | +| Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new Azure App Service instance web app in the specified resource group and app service plan. | +| Azure Developer CLI | `azd provision` | Provisions multiple Azure resources required for an app based on project resources and configurations, such as an Azure resource group, an Azure App Service web app and app service plan, an Azure Storage account, and an Azure Key Vault. | -`azd` aims to enhance the developer experience by reducing the complexity of managing Azure resources. It abstracts away many of the low-level details, allowing developers to focus more on creating and deploying app features rather than managing infrastructure. +`azd` enhances the developer experience by reducing the complexity of managing Azure resources. It abstracts away many of the low-level details, allowing developers to focus more on creating and deploying app features rather than manually managing infrastructure. ## The relationship between Azure Developer CLI commands and templates -[Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to structural `azd` conventions and include sample application code, infrastructure files, as well as `azd` configuration files. Most `azd` templates include the following: +`azd` commands are able to perform broader workflow tasks due in-part to their integration with the `azd` template system. [Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to structural `azd` conventions and include sample application code, infrastructure files, as well as `azd` configuration files. Most `azd` templates include the following: -- **`infra` folder** - Contains all of the Bicep or Terraform infrastructure as code files for the `azd` template. -- **`azure.yaml` file** - A configuration file that defines one or more services in your project and maps them to Azure resources defined in the `infra` folder for deployment. +- **`infra` folder** - Contains all of the Bicep or Terraform infrastructure-as-code files for the `azd` template. +- **`azure.yaml` file** - A configuration file that defines one or more services in your project and maps them to Azure resources defined in the `infra` folder for deployment. - **`.azure` folder** - Contains essential Azure configurations and environment variables, such as the location to deploy resources or other subscription information. - **`src` folder** - Contains all of the deployable app source code. :::image type="content" source="media/make-azd-compatible/azd-template-structure.png" alt-text="A screenshot showing an Azure Developer CLI template structure."::: -Without `azd` commands, these templates are just standard code repositories. In essence, Azure Developer CLI templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications. For example, `azd` commands leverage the conventional structure of these templates to perform actions and handle the following concerns: +Without `azd` commands, these templates are just standard code repositories. `azd` templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications: - **Project Initialization**: `azd init` sets up a new or existing project with a predefined structure and configuration. - **Infrastructure Provisioning**: `azd up` or `azd provision` uses infrastructure-as-code templates in the `infra` folder to automate the creation of Azure resources. @@ -46,22 +46,21 @@ Without `azd` commands, these templates are just standard code repositories. In - **Pipeline configuration**: `azd pipelie config` uses workflow configuration files in the `.github` or `.ado` folders to create a CI/CD pipeline for your app via GitHub Actions or Azure Pipelines with a single command. - **Monitoring and Management**: `azd monitor` assists with monitoring the health and performance of the deployed application by hooking into Azure monitoring features. +> [!NOTE] +> `azd` can also create and manage some Azure resources without the need to define infrastructure-as-code templates manually using the new [`azd compose`](/azure/developer/azure-developer-cli/azd-compose) feature, which is currently in alpha. + ## Commonly used commands `azd` commands provide a wide variety of features and functionality. Visit the [Azure Developer CLI commands](/azure/developer/azure-developer-cli/reference) reference page for a complete list of `azd` commands, parameters and their functionality. Some of the most commonly used commands include: - **`azd init`**: Initializes a new Azure Developer CLI project with a predefined structure and configuration. This command sets up the necessary files and directories to start a new project. -- **`azd up`**: Provisions the necessary Azure resources and deploys the application in one step. This command combines the provisioning and deployment processes to quickly get your application running on Azure. +- **`azd up`**: Provisions the necessary Azure resources and deploys the application in one step. This command combines `azd package`, `azd provision` and `azd deploy` to quickly get your application running on Azure. - **`azd provision`**: Provisions the required Azure infrastructure based on infrastructure-as-code templates. This command creates the necessary Azure resources such as VMs, databases, and storage accounts. - **`azd deploy`**: Deploys the application code to the provisioned Azure infrastructure. This command handles the deployment of your application code to the resources created by the `azd provision` command. - **`azd monitor`**: Monitors the health and performance of the deployed application. This command provides insights into the application's performance and helps identify any issues. - **`azd pipeline config`**: Configures a CI/CD pipeline for the project. This command sets up continuous integration and continuous deployment pipelines to automate the build and deployment processes. - **`azd down`**: De-provisions the Azure resources created by the project. This command removes the Azure resources that were provisioned, helping to clean up and avoid unnecessary costs. -- **`azd env list`**: Lists all the environments for the project. This command shows all the different environments (e.g., development, staging, production) that have been set up for the project. -- **`azd env new`**: Creates a new environment for the project. This command sets up a new environment with its own configuration and resources, allowing you to manage multiple environments for different stages of development. - **`azd config list`**: Lists the configuration settings for the project. This command shows all the configuration settings that have been applied to the project. -- **`azd config set`**: Sets a configuration setting for the project. This command allows you to update or add a new configuration setting. -- **`azd config get`**: Gets the value of a configuration setting for the project. This command retrieves the current value of a specific configuration setting. ## Next steps From 444d2a91a852d2ca665cfa576a93868b559f97a6 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 14:50:35 -0500 Subject: [PATCH 03/21] edits --- articles/azure-developer-cli/azd-commands.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index 2282f431e..9e008562a 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -15,32 +15,30 @@ Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and ## What are Azure Developer CLI commands? -The Azure Developer CLI provides a set of commands such as `azd up` and `azd init` that leverage the `azd` template system to automate developer workflows and perform other tasks. Conceptually, `azd` commands are designed to abstract away the complexities of managing Azure resources and services. They streamline the end-to-end developer workflow and provide high-level commands that map to common developer tasks or workflow stages. +The Azure Developer CLI provides a set of commands such as `azd up` and `azd init` that leverage the `azd` template system to automate developer workflows and perform other tasks. Conceptually, `azd` commands are designed to streamline the end-to-end developer workflow and provide abstractions that map to common developer tasks or workflow stages. -This emphasis on high level development stages differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools offer commands that focus on granular control over individual Azure resources and specific configurations, `azd` commands automate broader development tasks such as provisioning an entire set of services at once, or packaging and deploying multiple services at once. The following table provides an example of the differences between `azd` commands and other Azure command line tools: +The emphasis on high level development stages is what differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide commands that focus on granular control over individual Azure resources and configurations, `azd` commands automate broader development tasks such as provisioning an entire set of resources at once, or deploying multiple services at once. The following table provides an example of the differences between `azd` commands and other Azure command-line tools: | Tool | Sample Command | Outcome | |---------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| | Azure CLI | `az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name myWebApp` | Provisions a new web app in the specified resource group and app service plan. | -| Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new Azure App Service instance web app in the specified resource group and app service plan. | +| Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new web app in the specified resource group and app service plan. | | Azure Developer CLI | `azd provision` | Provisions multiple Azure resources required for an app based on project resources and configurations, such as an Azure resource group, an Azure App Service web app and app service plan, an Azure Storage account, and an Azure Key Vault. | -`azd` enhances the developer experience by reducing the complexity of managing Azure resources. It abstracts away many of the low-level details, allowing developers to focus more on creating and deploying app features rather than manually managing infrastructure. - ## The relationship between Azure Developer CLI commands and templates -`azd` commands are able to perform broader workflow tasks due in-part to their integration with the `azd` template system. [Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to structural `azd` conventions and include sample application code, infrastructure files, as well as `azd` configuration files. Most `azd` templates include the following: +`azd` commands can perform broader workflow tasks due in-part to their integration with the `azd` template system. [Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to `azd` structural conventions and include sample application code, infrastructure files, and configuration files. Most `azd` templates include the following: -- **`infra` folder** - Contains all of the Bicep or Terraform infrastructure-as-code files for the `azd` template. -- **`azure.yaml` file** - A configuration file that defines one or more services in your project and maps them to Azure resources defined in the `infra` folder for deployment. - **`.azure` folder** - Contains essential Azure configurations and environment variables, such as the location to deploy resources or other subscription information. +- **`infra` folder** - Contains all of the Bicep or Terraform infrastructure-as-code files for the `azd` template. - **`src` folder** - Contains all of the deployable app source code. +- **`azure.yaml` file** - A configuration file that defines one or more services in your project and maps them to Azure resources defined in the `infra` folder for deployment. -:::image type="content" source="media/make-azd-compatible/azd-template-structure.png" alt-text="A screenshot showing an Azure Developer CLI template structure."::: + :::image type="content" source="media/make-azd-compatible/azd-template-structure.png" alt-text="A screenshot showing an Azure Developer CLI template structure."::: Without `azd` commands, these templates are just standard code repositories. `azd` templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications: -- **Project Initialization**: `azd init` sets up a new or existing project with a predefined structure and configuration. +- **Template Initialization**: `azd init` sets up a new or existing template with a predefined structure and configuration. - **Infrastructure Provisioning**: `azd up` or `azd provision` uses infrastructure-as-code templates in the `infra` folder to automate the creation of Azure resources. - **Code Deployment**: `azd up` or `azd deploy` handle the deployment of application code in the `src` folder (configurable) to the provisioned infrastructure. - **Pipeline configuration**: `azd pipelie config` uses workflow configuration files in the `.github` or `.ado` folders to create a CI/CD pipeline for your app via GitHub Actions or Azure Pipelines with a single command. From c04defa34d7677a0285e05937acc0c82f7dc5be2 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 15:04:55 -0500 Subject: [PATCH 04/21] fixes --- articles/azure-developer-cli/azd-commands.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index 9e008562a..b276dc889 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -1,11 +1,11 @@ --- -title: Understanding Azure Developer CLI Commands -description: This article provides an in-depth conceptual overview of Azure Developer CLI commands, explores commonly used commands, and explains their relationship with Azure Developer CLI templates. +title: Azure Developer CLI commands overview +description: This article provides a conceptual overview of key concepts for Azure Developer CLI commands ms.topic: conceptual ms.date: 01/15/2025 --- -# Explore Azure Developer CLI commands overview +# Azure Developer CLI commands overview Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and streamline the development, deployment, and management of applications on Azure. In this article you'll learn the following: @@ -34,7 +34,7 @@ The emphasis on high level development stages is what differentiates `azd` comma - **`src` folder** - Contains all of the deployable app source code. - **`azure.yaml` file** - A configuration file that defines one or more services in your project and maps them to Azure resources defined in the `infra` folder for deployment. - :::image type="content" source="media/make-azd-compatible/azd-template-structure.png" alt-text="A screenshot showing an Azure Developer CLI template structure."::: +:::image type="content" source="media/make-azd-compatible/azd-template-structure.png" alt-text="A screenshot showing an Azure Developer CLI template structure."::: Without `azd` commands, these templates are just standard code repositories. `azd` templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications: @@ -51,10 +51,10 @@ Without `azd` commands, these templates are just standard code repositories. `az `azd` commands provide a wide variety of features and functionality. Visit the [Azure Developer CLI commands](/azure/developer/azure-developer-cli/reference) reference page for a complete list of `azd` commands, parameters and their functionality. Some of the most commonly used commands include: -- **`azd init`**: Initializes a new Azure Developer CLI project with a predefined structure and configuration. This command sets up the necessary files and directories to start a new project. +- **`azd init`**: Initializes an existing or new `azd` template. - **`azd up`**: Provisions the necessary Azure resources and deploys the application in one step. This command combines `azd package`, `azd provision` and `azd deploy` to quickly get your application running on Azure. -- **`azd provision`**: Provisions the required Azure infrastructure based on infrastructure-as-code templates. This command creates the necessary Azure resources such as VMs, databases, and storage accounts. -- **`azd deploy`**: Deploys the application code to the provisioned Azure infrastructure. This command handles the deployment of your application code to the resources created by the `azd provision` command. +- **`azd provision`**: Provisions the required Azure infrastructure based on infrastructure-as-code templates. +- **`azd deploy`**: Deploys the application code to the Azure resources created by `azd provision`. - **`azd monitor`**: Monitors the health and performance of the deployed application. This command provides insights into the application's performance and helps identify any issues. - **`azd pipeline config`**: Configures a CI/CD pipeline for the project. This command sets up continuous integration and continuous deployment pipelines to automate the build and deployment processes. - **`azd down`**: De-provisions the Azure resources created by the project. This command removes the Azure resources that were provisioned, helping to clean up and avoid unnecessary costs. From 65ec2288074ac41cfc95f63efa38c41d5ee8129d Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 15:56:06 -0500 Subject: [PATCH 05/21] verbiage --- articles/azure-developer-cli/azd-commands.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index b276dc889..a48801cf8 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -15,9 +15,9 @@ Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and ## What are Azure Developer CLI commands? -The Azure Developer CLI provides a set of commands such as `azd up` and `azd init` that leverage the `azd` template system to automate developer workflows and perform other tasks. Conceptually, `azd` commands are designed to streamline the end-to-end developer workflow and provide abstractions that map to common developer tasks or workflow stages. +The Azure Developer CLI provides a set of commands such as `azd up` and `azd init` that map to common development tasks or workflow stages. They provide abstractions to streamline the development, deployment, and management of applications on Azure. -The emphasis on high level development stages is what differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide commands that focus on granular control over individual Azure resources and configurations, `azd` commands automate broader development tasks such as provisioning an entire set of resources at once, or deploying multiple services at once. The following table provides an example of the differences between `azd` commands and other Azure command-line tools: +The emphasis on high-level development stages is what differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide commands that focus on granular control over individual Azure resources and configurations, `azd` commands automate broader development tasks such as provisioning an entire set of resources at once, or deploying multiple services at once. The following table provides an example of the differences between `azd` commands and other Azure command-line tools: | Tool | Sample Command | Outcome | |---------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| @@ -27,7 +27,7 @@ The emphasis on high level development stages is what differentiates `azd` comma ## The relationship between Azure Developer CLI commands and templates -`azd` commands can perform broader workflow tasks due in-part to their integration with the `azd` template system. [Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to `azd` structural conventions and include sample application code, infrastructure files, and configuration files. Most `azd` templates include the following: +`azd` commands are able to perform broader workflow tasks due in-part to their integration with the `azd` template system. [Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to `azd` structural conventions and include sample application code, infrastructure files, and configuration files. Most `azd` templates include the following: - **`.azure` folder** - Contains essential Azure configurations and environment variables, such as the location to deploy resources or other subscription information. - **`infra` folder** - Contains all of the Bicep or Terraform infrastructure-as-code files for the `azd` template. @@ -36,7 +36,7 @@ The emphasis on high level development stages is what differentiates `azd` comma :::image type="content" source="media/make-azd-compatible/azd-template-structure.png" alt-text="A screenshot showing an Azure Developer CLI template structure."::: -Without `azd` commands, these templates are just standard code repositories. `azd` templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications: +Without `azd` commands, these templates are just standard code repositories. Essentially, `azd` templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications: - **Template Initialization**: `azd init` sets up a new or existing template with a predefined structure and configuration. - **Infrastructure Provisioning**: `azd up` or `azd provision` uses infrastructure-as-code templates in the `infra` folder to automate the creation of Azure resources. @@ -49,7 +49,7 @@ Without `azd` commands, these templates are just standard code repositories. `az ## Commonly used commands -`azd` commands provide a wide variety of features and functionality. Visit the [Azure Developer CLI commands](/azure/developer/azure-developer-cli/reference) reference page for a complete list of `azd` commands, parameters and their functionality. Some of the most commonly used commands include: +`azd` commands provide a variety of features and functionality. Visit the [Azure Developer CLI commands](/azure/developer/azure-developer-cli/reference) reference page for a complete list of `azd` commands, parameters and their functionality. Some of the most commonly used commands include: - **`azd init`**: Initializes an existing or new `azd` template. - **`azd up`**: Provisions the necessary Azure resources and deploys the application in one step. This command combines `azd package`, `azd provision` and `azd deploy` to quickly get your application running on Azure. From ed98d13f9c275b9f697153d564916bd5f9361f0b Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 16:26:31 -0500 Subject: [PATCH 06/21] refactor --- articles/azure-developer-cli/TOC.yml | 4 +-- articles/azure-developer-cli/azd-commands.md | 31 +++++++++----------- 2 files changed, 16 insertions(+), 19 deletions(-) diff --git a/articles/azure-developer-cli/TOC.yml b/articles/azure-developer-cli/TOC.yml index b512ea681..e15b3ac8f 100644 --- a/articles/azure-developer-cli/TOC.yml +++ b/articles/azure-developer-cli/TOC.yml @@ -9,12 +9,12 @@ items: - name: Install or update azd href: install-azd.md + - name: Quickstart - Deploy an azd template + href: get-started.md - name: What are Azure Developer CLI commands? href: azd-commands.md - name: What are Azure Developer CLI templates? href: azd-templates.md - - name: Quickstart - Deploy an azd template - href: get-started.md - name: Supported languages and environments href: supported-languages-environments.md - name: Deployment diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index a48801cf8..1f6a731ac 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -10,14 +10,24 @@ ms.date: 01/15/2025 Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and streamline the development, deployment, and management of applications on Azure. In this article you'll learn the following: - Key concepts about `azd` commands -- How `azd` commands and templates are related +- How `azd` commands compare to other command-line tools - Commonly used `azd` commands +- How `azd` commands and templates are related ## What are Azure Developer CLI commands? -The Azure Developer CLI provides a set of commands such as `azd up` and `azd init` that map to common development tasks or workflow stages. They provide abstractions to streamline the development, deployment, and management of applications on Azure. +The Azure Developer CLI provides a set of commands such as and `azd provision` and `azd deploy` that map to common development workflow stages and streamline tasks such as provisioning, deployment, pipeline configuration, and management of applications on Azure. Some commands are also used to manage certain `azd` configurations and environment settings. + +> [!NOTE] +> Explore a simple `azd` command workflow in more detail using the [Deploy an Azure Developer CLI template](/azure/developer/azure-developer-cli/get-started) quickstart. + +Most `azd` commands also accept parameters you can use to customize their behavior. Visit the [Azure Developer CLI commands](/azure/developer/azure-developer-cli/reference) reference page for a complete list of `azd` commands, parameters and their functionality. -The emphasis on high-level development stages is what differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide commands that focus on granular control over individual Azure resources and configurations, `azd` commands automate broader development tasks such as provisioning an entire set of resources at once, or deploying multiple services at once. The following table provides an example of the differences between `azd` commands and other Azure command-line tools: +## Compare Azure Developer CLI commands to other tools + +The emphasis on high-level development stages is what differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide numerous commands that focus on granular control over individual Azure resources and configurations, `azd` provides fewer, broader commands to automate development tasks such as provisioning an entire set of resources or deploying multiple services at once. + +The following table highlights the differences between a sample `azd` command and other Azure command-line tools. Note that the `azd provision` command performs numerous tasks at once and does not have a direct equivalent in these other tools. Many Azure CLI or PowerShell commands would be required to accomplish the same task. | Tool | Sample Command | Outcome | |---------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| @@ -25,7 +35,7 @@ The emphasis on high-level development stages is what differentiates `azd` comma | Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new web app in the specified resource group and app service plan. | | Azure Developer CLI | `azd provision` | Provisions multiple Azure resources required for an app based on project resources and configurations, such as an Azure resource group, an Azure App Service web app and app service plan, an Azure Storage account, and an Azure Key Vault. | -## The relationship between Azure Developer CLI commands and templates +## The relationship between commands and templates `azd` commands are able to perform broader workflow tasks due in-part to their integration with the `azd` template system. [Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to `azd` structural conventions and include sample application code, infrastructure files, and configuration files. Most `azd` templates include the following: @@ -47,19 +57,6 @@ Without `azd` commands, these templates are just standard code repositories. Ess > [!NOTE] > `azd` can also create and manage some Azure resources without the need to define infrastructure-as-code templates manually using the new [`azd compose`](/azure/developer/azure-developer-cli/azd-compose) feature, which is currently in alpha. -## Commonly used commands - -`azd` commands provide a variety of features and functionality. Visit the [Azure Developer CLI commands](/azure/developer/azure-developer-cli/reference) reference page for a complete list of `azd` commands, parameters and their functionality. Some of the most commonly used commands include: - -- **`azd init`**: Initializes an existing or new `azd` template. -- **`azd up`**: Provisions the necessary Azure resources and deploys the application in one step. This command combines `azd package`, `azd provision` and `azd deploy` to quickly get your application running on Azure. -- **`azd provision`**: Provisions the required Azure infrastructure based on infrastructure-as-code templates. -- **`azd deploy`**: Deploys the application code to the Azure resources created by `azd provision`. -- **`azd monitor`**: Monitors the health and performance of the deployed application. This command provides insights into the application's performance and helps identify any issues. -- **`azd pipeline config`**: Configures a CI/CD pipeline for the project. This command sets up continuous integration and continuous deployment pipelines to automate the build and deployment processes. -- **`azd down`**: De-provisions the Azure resources created by the project. This command removes the Azure resources that were provisioned, helping to clean up and avoid unnecessary costs. -- **`azd config list`**: Lists the configuration settings for the project. This command shows all the configuration settings that have been applied to the project. - ## Next steps > [!div class="nextstepaction"] From 336337fd78e7fc3179f0b4459170fff1f5f70459 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 16:32:11 -0500 Subject: [PATCH 07/21] refactor --- articles/azure-developer-cli/azd-commands.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index 1f6a731ac..9d6bd30f0 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -7,16 +7,7 @@ ms.date: 01/15/2025 # Azure Developer CLI commands overview -Azure Developer CLI (`azd`) commands are a set of tools designed to simplify and streamline the development, deployment, and management of applications on Azure. In this article you'll learn the following: - -- Key concepts about `azd` commands -- How `azd` commands compare to other command-line tools -- Commonly used `azd` commands -- How `azd` commands and templates are related - -## What are Azure Developer CLI commands? - -The Azure Developer CLI provides a set of commands such as and `azd provision` and `azd deploy` that map to common development workflow stages and streamline tasks such as provisioning, deployment, pipeline configuration, and management of applications on Azure. Some commands are also used to manage certain `azd` configurations and environment settings. +The Azure Developer CLI provides a set of commands such as and `azd provision` and `azd deploy` that map to common development workflow stages and streamline tasks such as provisioning, deployment, pipeline configuration, and management of applications on Azure. Some commands are also used to manage `azd` configurations and environment settings. > [!NOTE] > Explore a simple `azd` command workflow in more detail using the [Deploy an Azure Developer CLI template](/azure/developer/azure-developer-cli/get-started) quickstart. From 7cb16999c7dbe6b7e62cbfa700fca377c9b5d6e6 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 18:14:19 -0500 Subject: [PATCH 08/21] updates --- articles/azure-developer-cli/azd-commands.md | 68 ++++++++++++++++---- 1 file changed, 55 insertions(+), 13 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index 9d6bd30f0..2270fbea5 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -7,18 +7,16 @@ ms.date: 01/15/2025 # Azure Developer CLI commands overview -The Azure Developer CLI provides a set of commands such as and `azd provision` and `azd deploy` that map to common development workflow stages and streamline tasks such as provisioning, deployment, pipeline configuration, and management of applications on Azure. Some commands are also used to manage `azd` configurations and environment settings. +The Azure Developer CLI (`azd`) is designed to streamline the end-to-end developer workflow on Azure. `azd` provides high-level commands that act as abstractions to simplify common developer tasks such as project initialization, infrastructure provisioning, code deployment, and monitoring. `azd` commands are available in the terminal, an integrated development environment (IDE), or through CI/CD (continuous integration/continuous deployment) pipelines. > [!NOTE] -> Explore a simple `azd` command workflow in more detail using the [Deploy an Azure Developer CLI template](/azure/developer/azure-developer-cli/get-started) quickstart. - -Most `azd` commands also accept parameters you can use to customize their behavior. Visit the [Azure Developer CLI commands](/azure/developer/azure-developer-cli/reference) reference page for a complete list of `azd` commands, parameters and their functionality. +> Visit the [Deploy an Azure Developer CLI template](/azure/developer/azure-developer-cli/get-started) quickstart to explore a sample `azd` command workflow in more detail. ## Compare Azure Developer CLI commands to other tools -The emphasis on high-level development stages is what differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide numerous commands that focus on granular control over individual Azure resources and configurations, `azd` provides fewer, broader commands to automate development tasks such as provisioning an entire set of resources or deploying multiple services at once. +The emphasis on high-level development stages is what differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide numerous commands for granular control over individual Azure resources and configurations, `azd` provides fewer, broader commands to automate higher-level development tasks such as provisioning multiple resources or deploying multiple services at once. -The following table highlights the differences between a sample `azd` command and other Azure command-line tools. Note that the `azd provision` command performs numerous tasks at once and does not have a direct equivalent in these other tools. Many Azure CLI or PowerShell commands would be required to accomplish the same task. +The following table highlights the differences between a sample `azd` command and other Azure command-line tools. Note that the `azd provision` command performs numerous tasks at once, and does not have a direct equivalent in these other tools. Many Azure CLI or PowerShell commands would be required to accomplish the same task. | Tool | Sample Command | Outcome | |---------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| @@ -26,7 +24,7 @@ The following table highlights the differences between a sample `azd` command an | Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new web app in the specified resource group and app service plan. | | Azure Developer CLI | `azd provision` | Provisions multiple Azure resources required for an app based on project resources and configurations, such as an Azure resource group, an Azure App Service web app and app service plan, an Azure Storage account, and an Azure Key Vault. | -## The relationship between commands and templates +## The relationship between Azure Developer CLI commands and templates `azd` commands are able to perform broader workflow tasks due in-part to their integration with the `azd` template system. [Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to `azd` structural conventions and include sample application code, infrastructure files, and configuration files. Most `azd` templates include the following: @@ -37,17 +35,61 @@ The following table highlights the differences between a sample `azd` command an :::image type="content" source="media/make-azd-compatible/azd-template-structure.png" alt-text="A screenshot showing an Azure Developer CLI template structure."::: -Without `azd` commands, these templates are just standard code repositories. Essentially, `azd` templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications: +Without `azd` commands, these templates are just standard code repositories. Essentially, `azd` templates serve as foundational blueprints, while CLI commands act as the engine driving deployment, management, and monitoring of your applications. `azd` commands use the assets in these templates to perform various tasks. + +Using the preceding template as an example: -- **Template Initialization**: `azd init` sets up a new or existing template with a predefined structure and configuration. -- **Infrastructure Provisioning**: `azd up` or `azd provision` uses infrastructure-as-code templates in the `infra` folder to automate the creation of Azure resources. -- **Code Deployment**: `azd up` or `azd deploy` handle the deployment of application code in the `src` folder (configurable) to the provisioned infrastructure. -- **Pipeline configuration**: `azd pipelie config` uses workflow configuration files in the `.github` or `.ado` folders to create a CI/CD pipeline for your app via GitHub Actions or Azure Pipelines with a single command. -- **Monitoring and Management**: `azd monitor` assists with monitoring the health and performance of the deployed application by hooking into Azure monitoring features. +- The `azd provision` command creates resources in Azure using the infrastructure-as-code files in the `infra` folder of a template. +- The `azd deploy` command deploys an app or service defined in the `src` folder. > [!NOTE] > `azd` can also create and manage some Azure resources without the need to define infrastructure-as-code templates manually using the new [`azd compose`](/azure/developer/azure-developer-cli/azd-compose) feature, which is currently in alpha. +## Explore common commands + +The following sections provide an overview of some of the most common `azd` commands to provide examples of working with templates and different development tasks. + +> [!NOTE] +> For a complete list of `azd` commands and their parameters, visit the [Azure Developer CLI reference](/azure/developer/azure-developer-cli/reference) page. + +### Initialize and run a template + +- **`azd init`**: Initializes an existing `azd` template or creates and initializes a new template. This command essentially sets up the necessary files and directories to start working with `azd`. + +- **`azd up`**: A convenience command to provision, package, and deploy all of your app resources in one command. This command is the equivalent of running `azd provision`, `azd package`, and `azd deploy` individually. + +### Infrastructure Provisioning + +- **`azd provision`**: Provisions the required Azure resources such as Azure Container App instances or Azure Storage accounts based on infrastructure-as-code templates or resources defined in `azure.yaml`. + +### Code Deployment + +- **`azd package`**: Packages the application's code to be deployed to Azure. + +- **`azd deploy`**: Deploys your application code to the resources created by the `azd provision` command. + +### Monitoring and Management + +- **`azd monitor`**: Provides insights into the health and performance of the deployed application + +### CI/CD Pipeline Configuration + +- **`azd pipeline config`**: Configures a CI/CD pipeline for the project. This command sets up continuous integration and continuous deployment pipelines to automate the build and deployment processes. + +### Environment Management + +- **`azd env list`**: Lists all the different environments (e.g., development, staging, production) that have been set up for the template. +- **`azd env new`**: Creates a new environment with its own configuration and resources, allowing you to manage multiple environments for different stages of development. + +### Configuration Management + +- **`azd config list`**: Lists the settings configured for `azd`. +- **`azd config set`**: Allows you to update or add a new configuration setting for `azd`. + +### Resource Cleanup + +- **`azd down`**: Deletes the Azure resources created by the project to clean up your environment and avoid unnecessary costs. + ## Next steps > [!div class="nextstepaction"] From 547a0ad9294b9be887539c39b2270d527b22546a Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 18:23:45 -0500 Subject: [PATCH 09/21] fix formatting --- articles/azure-developer-cli/azd-commands.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index 2270fbea5..5cc2dd51e 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -7,22 +7,27 @@ ms.date: 01/15/2025 # Azure Developer CLI commands overview -The Azure Developer CLI (`azd`) is designed to streamline the end-to-end developer workflow on Azure. `azd` provides high-level commands that act as abstractions to simplify common developer tasks such as project initialization, infrastructure provisioning, code deployment, and monitoring. `azd` commands are available in the terminal, an integrated development environment (IDE), or through CI/CD (continuous integration/continuous deployment) pipelines. +The Azure Developer CLI (`azd`) is designed to streamline the end-to-end developer workflow on Azure. `azd` provides high-level commands that act as abstractions to simplify common developer tasks such as project initialization, infrastructure provisioning, code deployment, and monitoring. `azd` commands are available in the terminal, an integrated development environment (IDE), or through CI/CD (continuous integration/continuous deployment) pipelines. In this article, you'll learn about the following: + +- Key `azd` command concepts +- How `azd` commands compare to other tools +- The relationship between `azd` commands and templates +- Common `azd` commands and which development tasks they map to > [!NOTE] > Visit the [Deploy an Azure Developer CLI template](/azure/developer/azure-developer-cli/get-started) quickstart to explore a sample `azd` command workflow in more detail. ## Compare Azure Developer CLI commands to other tools -The emphasis on high-level development stages is what differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide numerous commands for granular control over individual Azure resources and configurations, `azd` provides fewer, broader commands to automate higher-level development tasks such as provisioning multiple resources or deploying multiple services at once. +The emphasis on high-level development stages differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide numerous commands for granular control over individual Azure resources and configurations, `azd` provides fewer, broader commands to automate higher-level development tasks such as provisioning multiple resources or deploying multiple services at once. The following table highlights the differences between a sample `azd` command and other Azure command-line tools. Note that the `azd provision` command performs numerous tasks at once, and does not have a direct equivalent in these other tools. Many Azure CLI or PowerShell commands would be required to accomplish the same task. | Tool | Sample Command | Outcome | |---------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| Azure Developer CLI | `azd provision` | Provisions multiple Azure resources required for an app based on project resources and configurations, such as an Azure resource group, an Azure App Service web app and app service plan, an Azure Storage account, and an Azure Key Vault. | | Azure CLI | `az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name myWebApp` | Provisions a new web app in the specified resource group and app service plan. | | Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new web app in the specified resource group and app service plan. | -| Azure Developer CLI | `azd provision` | Provisions multiple Azure resources required for an app based on project resources and configurations, such as an Azure resource group, an Azure App Service web app and app service plan, an Azure Storage account, and an Azure Key Vault. | ## The relationship between Azure Developer CLI commands and templates @@ -55,7 +60,6 @@ The following sections provide an overview of some of the most common `azd` comm ### Initialize and run a template - **`azd init`**: Initializes an existing `azd` template or creates and initializes a new template. This command essentially sets up the necessary files and directories to start working with `azd`. - - **`azd up`**: A convenience command to provision, package, and deploy all of your app resources in one command. This command is the equivalent of running `azd provision`, `azd package`, and `azd deploy` individually. ### Infrastructure Provisioning @@ -65,7 +69,6 @@ The following sections provide an overview of some of the most common `azd` comm ### Code Deployment - **`azd package`**: Packages the application's code to be deployed to Azure. - - **`azd deploy`**: Deploys your application code to the resources created by the `azd provision` command. ### Monitoring and Management @@ -88,7 +91,7 @@ The following sections provide an overview of some of the most common `azd` comm ### Resource Cleanup -- **`azd down`**: Deletes the Azure resources created by the project to clean up your environment and avoid unnecessary costs. +- **`azd down`**: Deletes the Azure resources created by the template to clean up your environment and avoid unnecessary costs. ## Next steps From 1dae1458940a7cd5e020549dd37b069faaa8bc71 Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 18:27:35 -0500 Subject: [PATCH 10/21] fix --- articles/azure-developer-cli/azd-commands.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index 5cc2dd51e..2b44084b3 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -17,7 +17,7 @@ The Azure Developer CLI (`azd`) is designed to streamline the end-to-end develop > [!NOTE] > Visit the [Deploy an Azure Developer CLI template](/azure/developer/azure-developer-cli/get-started) quickstart to explore a sample `azd` command workflow in more detail. -## Compare Azure Developer CLI commands to other tools +## Compare Azure Developer CLI commands The emphasis on high-level development stages differentiates `azd` commands from other command-line tools such as the Azure CLI or Azure PowerShell. Whereas those tools provide numerous commands for granular control over individual Azure resources and configurations, `azd` provides fewer, broader commands to automate higher-level development tasks such as provisioning multiple resources or deploying multiple services at once. @@ -29,7 +29,7 @@ The following table highlights the differences between a sample `azd` command an | Azure CLI | `az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name myWebApp` | Provisions a new web app in the specified resource group and app service plan. | | Azure PowerShell | `New-AzWebApp -ResourceGroupName "myResourceGroup" -Name "myWebApp" -AppServicePlan "myAppServicePlan"` | Provisions a new web app in the specified resource group and app service plan. | -## The relationship between Azure Developer CLI commands and templates +## Azure Developer CLI commands and templates `azd` commands are able to perform broader workflow tasks due in-part to their integration with the `azd` template system. [Azure Developer CLI templates](/azure/developer/azure-developer-cli/azd-templates) are code projects that adhere to `azd` structural conventions and include sample application code, infrastructure files, and configuration files. Most `azd` templates include the following: From 1d573ec8e899c0f2a1b8203e84e2903e0f73b6de Mon Sep 17 00:00:00 2001 From: Alex Wolf Date: Fri, 17 Jan 2025 18:31:45 -0500 Subject: [PATCH 11/21] tweak --- articles/azure-developer-cli/azd-commands.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/articles/azure-developer-cli/azd-commands.md b/articles/azure-developer-cli/azd-commands.md index 2b44084b3..35b43eb24 100644 --- a/articles/azure-developer-cli/azd-commands.md +++ b/articles/azure-developer-cli/azd-commands.md @@ -9,10 +9,10 @@ ms.date: 01/15/2025 The Azure Developer CLI (`azd`) is designed to streamline the end-to-end developer workflow on Azure. `azd` provides high-level commands that act as abstractions to simplify common developer tasks such as project initialization, infrastructure provisioning, code deployment, and monitoring. `azd` commands are available in the terminal, an integrated development environment (IDE), or through CI/CD (continuous integration/continuous deployment) pipelines. In this article, you'll learn about the following: -- Key `azd` command concepts +- Essential `azd` command concepts - How `azd` commands compare to other tools - The relationship between `azd` commands and templates -- Common `azd` commands and which development tasks they map to +- Common `azd` commands and which development tasks they accelerate > [!NOTE] > Visit the [Deploy an Azure Developer CLI template](/azure/developer/azure-developer-cli/get-started) quickstart to explore a sample `azd` command workflow in more detail. @@ -84,11 +84,6 @@ The following sections provide an overview of some of the most common `azd` comm - **`azd env list`**: Lists all the different environments (e.g., development, staging, production) that have been set up for the template. - **`azd env new`**: Creates a new environment with its own configuration and resources, allowing you to manage multiple environments for different stages of development. -### Configuration Management - -- **`azd config list`**: Lists the settings configured for `azd`. -- **`azd config set`**: Allows you to update or add a new configuration setting for `azd`. - ### Resource Cleanup - **`azd down`**: Deletes the Azure resources created by the template to clean up your environment and avoid unnecessary costs. From be53ed634ac66108823bd3b312bb37168fd5a97b Mon Sep 17 00:00:00 2001 From: JoshTheTechWriter <183134486+JoshTheTechWriter@users.noreply.github.com> Date: Wed, 15 Jan 2025 12:42:42 -0500 Subject: [PATCH 12/21] Eight bundle of 20 files. --- ...stgresql-flexible-server-non-admin-user.md | 2 +- ...postgresql-single-server-non-admin-user.md | 2 +- ...-data-azure-mysql-flexible-server-setup.md | 6 +- ...ng-data-azure-mysql-single-server-setup.md | 8 +- ...-azure-postgresql-flexible-server-setup.md | 6 +- ...ta-azure-postgresql-single-server-setup.md | 6 +- .../spring-data-r2dbc-create-schema.md | 2 +- .../includes/spring-data-sql-server-setup.md | 2 +- .../includes/spring-jms-passwordless-queue.md | 4 +- .../includes/spring-jms-passwordless-topic.md | 4 +- .../java/spring-framework/kafka-support.md | 6 +- ...igrate-kafka-to-passwordless-connection.md | 22 +- ...igrate-mysql-to-passwordless-connection.md | 16 +- ...e-postgresql-to-passwordless-connection.md | 10 +- ...sql-database-to-passwordless-connection.md | 2 +- .../migration-guide-for-4.0.md | 202 +++++++++--------- .../java/spring-framework/mysql-support.md | 12 +- .../spring-framework/postgresql-support.md | 10 +- .../java/spring-framework/production-ready.md | 22 +- .../java/spring-framework/redis-support.md | 8 +- 20 files changed, 176 insertions(+), 176 deletions(-) diff --git a/articles/java/spring-framework/includes/create-postgresql-flexible-server-non-admin-user.md b/articles/java/spring-framework/includes/create-postgresql-flexible-server-non-admin-user.md index d0d27399d..48d399382 100644 --- a/articles/java/spring-framework/includes/create-postgresql-flexible-server-non-admin-user.md +++ b/articles/java/spring-framework/includes/create-postgresql-flexible-server-non-admin-user.md @@ -33,7 +33,7 @@ ms.author: hangwan > [!IMPORTANT] > To use passwordless connections, configure the Microsoft Entra admin user for your Azure Database for PostgreSQL Flexible Server instance. For more information, see [Manage Microsoft Entra roles in Azure Database for PostgreSQL - Flexible Server](/azure/postgresql/flexible-server/how-to-manage-azure-ad-users). -Create a SQL script called *create_ad_user.sql* for creating a non-admin user. Add the following contents and save it locally: +Create a SQL script called **create_ad_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash cat << EOF > create_ad_user.sql diff --git a/articles/java/spring-framework/includes/create-postgresql-single-server-non-admin-user.md b/articles/java/spring-framework/includes/create-postgresql-single-server-non-admin-user.md index bd6f17ba6..f0413a409 100644 --- a/articles/java/spring-framework/includes/create-postgresql-single-server-non-admin-user.md +++ b/articles/java/spring-framework/includes/create-postgresql-single-server-non-admin-user.md @@ -33,7 +33,7 @@ ms.author: hangwan > [!IMPORTANT] > To use passwordless connections, configure the Microsoft Entra admin user for your Azure Database for PostgreSQL Single Server instance. For more information, see [Use Microsoft Entra ID for authentication with PostgreSQL](/azure/postgresql/single-server/how-to-configure-sign-in-azure-ad-authentication). -Create a SQL script called *create_ad_user.sql* for creating a non-admin user. Add the following contents and save it locally: +Create a SQL script called **create_ad_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash cat << EOF > create_ad_user.sql diff --git a/articles/java/spring-framework/includes/spring-data-azure-mysql-flexible-server-setup.md b/articles/java/spring-framework/includes/spring-data-azure-mysql-flexible-server-setup.md index acaa08e69..7ab6dbee9 100644 --- a/articles/java/spring-framework/includes/spring-data-azure-mysql-flexible-server-setup.md +++ b/articles/java/spring-framework/includes/spring-data-azure-mysql-flexible-server-setup.md @@ -24,7 +24,7 @@ You can use the following method to create a non-admin user that uses a password ### [Password](#tab/password) -Create a SQL script called *create_user.sql* for creating a non-admin user. Add the following contents and save it locally: +Create a SQL script called **create_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash cat << EOF > create_user.sql @@ -49,7 +49,7 @@ mysql -h mysqlflexibletest.mysql.database.azure.com --user [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Starter JDBC MySQL artifact: diff --git a/articles/java/spring-framework/includes/spring-data-azure-mysql-single-server-setup.md b/articles/java/spring-framework/includes/spring-data-azure-mysql-single-server-setup.md index ac88310c7..7eb2e7c9f 100644 --- a/articles/java/spring-framework/includes/spring-data-azure-mysql-single-server-setup.md +++ b/articles/java/spring-framework/includes/spring-data-azure-mysql-single-server-setup.md @@ -21,7 +21,7 @@ This step will create a non-admin user and grant all permissions on the `demo` d > [!IMPORTANT] > To use passwordless connections, create a Microsoft Entra admin user for your Azure Database for MySQL instance. For more information, see the [Setting the Microsoft Entra Admin user](/azure/mysql/single-server/how-to-configure-sign-in-azure-ad-authentication#setting-the-azure-ad-admin-user) section of [Use Microsoft Entra ID for authentication with MySQL](/azure/mysql/single-server/how-to-configure-sign-in-azure-ad-authentication). -Create a SQL script called *create_ad_user.sql* for creating a non-admin user. Add the following contents and save it locally: +Create a SQL script called **create_ad_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash export AZ_MYSQL_AD_NON_ADMIN_USERID=$(az ad signed-in-user show --query id --output tsv) @@ -45,7 +45,7 @@ mysql -h mysqlsingletest.mysql.database.azure.com --user create_user.sql @@ -70,7 +70,7 @@ mysql -h mysqlsingletest.mysql.database.azure.com --user [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Starter JDBC MySQL artifact: diff --git a/articles/java/spring-framework/includes/spring-data-azure-postgresql-flexible-server-setup.md b/articles/java/spring-framework/includes/spring-data-azure-postgresql-flexible-server-setup.md index 241258af3..66a88aec2 100644 --- a/articles/java/spring-framework/includes/spring-data-azure-postgresql-flexible-server-setup.md +++ b/articles/java/spring-framework/includes/spring-data-azure-postgresql-flexible-server-setup.md @@ -24,7 +24,7 @@ You can use the following method to create a non-admin user that uses a password ### [Password](#tab/password) -Create a SQL script called *create_user.sql* for creating a non-admin user. Add the following contents and save it locally: +Create a SQL script called **create_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash cat << EOF > create_user.sql @@ -48,7 +48,7 @@ psql "host=postgresqlflexibletest.postgres.database.azure.com user= [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Starter JDBC PostgreSQL artifact: diff --git a/articles/java/spring-framework/includes/spring-data-azure-postgresql-single-server-setup.md b/articles/java/spring-framework/includes/spring-data-azure-postgresql-single-server-setup.md index d92276593..8f7acf6a7 100644 --- a/articles/java/spring-framework/includes/spring-data-azure-postgresql-single-server-setup.md +++ b/articles/java/spring-framework/includes/spring-data-azure-postgresql-single-server-setup.md @@ -24,7 +24,7 @@ You can use the following method to create a non-admin user that uses a password ### [Password](#tab/password) -Create a SQL script called *create_user.sql* for creating a non-admin user. Add the following contents and save it locally: +Create a SQL script called **create_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash cat << EOF > create_user.sql @@ -48,7 +48,7 @@ psql "host=postgresqlsingletest.postgres.database.azure.com user= [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Starter JDBC PostgreSQL artifact: diff --git a/articles/java/spring-framework/includes/spring-data-r2dbc-create-schema.md b/articles/java/spring-framework/includes/spring-data-r2dbc-create-schema.md index 01bf08dbd..bd6eefffc 100644 --- a/articles/java/spring-framework/includes/spring-data-r2dbc-create-schema.md +++ b/articles/java/spring-framework/includes/spring-data-r2dbc-create-schema.md @@ -36,4 +36,4 @@ public class DemoApplication { } ``` -This Spring bean uses a file called *schema.sql*, so create that file in the *src/main/resources* folder, and add the following text: +This Spring bean uses a file called **schema.sql**, so create that file in the **src/main/resources** folder, and add the following text: diff --git a/articles/java/spring-framework/includes/spring-data-sql-server-setup.md b/articles/java/spring-framework/includes/spring-data-sql-server-setup.md index ed4aff92e..6921b88d2 100644 --- a/articles/java/spring-framework/includes/spring-data-sql-server-setup.md +++ b/articles/java/spring-framework/includes/spring-data-sql-server-setup.md @@ -47,7 +47,7 @@ The Microsoft Entra admin you created is an SQL database admin user, so you don' ### [Password](#tab/password) -1. First, create a SQL script called *create_user.sql* for creating a non-admin user. Add the following contents and save it locally: +1. First, create a SQL script called **create_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash cat << EOF > create_user.sql diff --git a/articles/java/spring-framework/includes/spring-jms-passwordless-queue.md b/articles/java/spring-framework/includes/spring-jms-passwordless-queue.md index c41ac87d2..c85d12094 100644 --- a/articles/java/spring-framework/includes/spring-jms-passwordless-queue.md +++ b/articles/java/spring-framework/includes/spring-jms-passwordless-queue.md @@ -18,7 +18,7 @@ The following table describes the fields in the configuration: | Field | Description | |----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `spring.jms.servicebus.namespace` | Specify the namespace you obtained in your Service Bus service instance from the Azure portal. | -| `spring.jms.servicebus.pricing-tier` | Specify the pricing tier of your service bus. Supported values are *premium* and *standard*. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | +| `spring.jms.servicebus.pricing-tier` | Specify the pricing tier of your service bus. Supported values are `premium` and `standard`. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | | `spring.jms.servicebus.passwordless-enabled` | Specify whether to use passwordless. | | `spring.jms.listener.receive-timeout` | By default the receive timeout value is 1000. We recommend that you set it to 60000 | @@ -35,7 +35,7 @@ The following table describes the fields in the configuration: | Field | Description | |-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `spring.jms.servicebus.connection-string` | Specify the connection string you obtained in your Service Bus namespace from the Azure portal. | -| `spring.jms.servicebus.pricing-tier` | Specify the pricing tier of your service bus. Supported values are *premium* and *standard*. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | +| `spring.jms.servicebus.pricing-tier` | Specify the pricing tier of your service bus. Supported values are `premium` and `standard`. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | | `spring.jms.listener.receive-timeout` | By default the receive timeout value is 1000. We recommend that you set it to 60000 | --- diff --git a/articles/java/spring-framework/includes/spring-jms-passwordless-topic.md b/articles/java/spring-framework/includes/spring-jms-passwordless-topic.md index 2e5bb392e..f09d4dfc7 100644 --- a/articles/java/spring-framework/includes/spring-jms-passwordless-topic.md +++ b/articles/java/spring-framework/includes/spring-jms-passwordless-topic.md @@ -19,7 +19,7 @@ The following table describes the fields in the configuration: | Field | Description | |----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `spring.jms.servicebus.namespace` | Specify the namespace you obtained in your Service Bus service instance from the Azure portal. | -| `spring.jms.servicebus.pricing-tier` | Specify the pricing tier of your service bus. Supported values are *premium* and *standard*. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | +| `spring.jms.servicebus.pricing-tier` | Specify the pricing tier of your service bus. Supported values are `premium` and `standard`. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | | `spring.jms.servicebus.topic-client-id` | Specify the JMS client ID, which is your Service Bus subscription ID in the Azure portal. | | `spring.jms.servicebus.passwordless-enabled` | Specify whether to use passwordless. | | `spring.jms.listener.receive-timeout` | By default the receive timeout value is 1000. We recommend that you set it to 60000 | @@ -38,7 +38,7 @@ The following table describes the fields in the configuration: | Field | Description | |-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `spring.jms.servicebus.connection-string` | Specify the connection string you obtained in your Service Bus namespace from the Azure portal. | -| `spring.jms.servicebus.pricing-tier` | Specify the pricing tier of your service bus. Supported values are *premium* and *standard*. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | +| `spring.jms.servicebus.pricing-tier` | Specify the pricing tier of your service bus. Supported values are `premium` and `standard`. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | | `spring.jms.servicebus.topic-client-id` | Specify the JMS client ID, which is your Service Bus subscription ID in the Azure portal. | | `spring.jms.listener.receive-timeout` | By default the receive timeout value is 1000. We recommend that you set it to 60000 | diff --git a/articles/java/spring-framework/kafka-support.md b/articles/java/spring-framework/kafka-support.md index 40ec839f0..c220c68f4 100644 --- a/articles/java/spring-framework/kafka-support.md +++ b/articles/java/spring-framework/kafka-support.md @@ -127,7 +127,7 @@ The following table shows the Spring Boot Kafka common configuration options: > | spring.kafka.properties.azure.credential.client-certificate-path | Path of a PEM certificate file to use when performing service principal authentication with Azure. | > | spring.kafka.properties.azure.credential.client-id | Client ID to use when performing service principal authentication with Azure. This is a legacy property. | > | spring.kafka.properties.azure.credential.client-secret | Client secret to use when performing service principal authentication with Azure. This is a legacy property. | -> | spring.kafka.properties.azure.credential.managed-identity-enabled | Whether to enable managed identity to authenticate with Azure. If *true* and the `client-id` is set, will use the client ID as user assigned managed identity client ID. The default value is *false*. | +> | spring.kafka.properties.azure.credential.managed-identity-enabled | Whether to enable managed identity to authenticate with Azure. If `true` and the `client-id` is set, will use the client ID as user assigned managed identity client ID. The default value is `false`. | > | spring.kafka.properties.azure.credential.password | Password to use when performing username/password authentication with Azure. | > | spring.kafka.properties.azure.credential.username | Username to use when performing username/password authentication with Azure. | > | spring.kafka.properties.azure.profile.environment.active-directory-endpoint | The Microsoft Entra endpoint to connect to. | @@ -149,7 +149,7 @@ The following table shows the Spring Boot Event Hubs for Kafka common configurat > [!div class="mx-tdBreakAll"] > | Property | Description | > |----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -> | **spring.cloud.azure.eventhubs**.kafka.enabled | Whether to enable the Azure Event Hubs Kafka support. The default value is *true*. | +> | **spring.cloud.azure.eventhubs**.kafka.enabled | Whether to enable the Azure Event Hubs Kafka support. The default value is `true`. | > | **spring.cloud.azure.eventhubs**.connection-string | Azure Event Hubs connection string. Provide this value when you want to provide the connection string directly. | > | **spring.cloud.azure.eventhubs**.namespace | Azure Event Hubs namespace. Provide this value when you want to retrieve the connection information through Azure Resource Manager. | > | **spring.cloud.azure.eventhubs**.resource.resource-group | The resource group of Azure Event Hubs namespace. Provide this value when you want to retrieve the connection information through Azure Resource Manager. | @@ -251,7 +251,7 @@ spring.cloud.stream.kafka.binder.brokers=.servicebus.windows.net: 1. To use the managed identity, you need enable the managed identity for your service and assign the `Azure Event Hubs Data Receiver` and `Azure Event Hubs Data Sender` roles. For more information, see [Assign Azure roles for access rights](/azure/event-hubs/authorize-access-azure-active-directory#assign-azure-roles-for-access-rights). -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/migrate-kafka-to-passwordless-connection.md b/articles/java/spring-framework/migrate-kafka-to-passwordless-connection.md index d903cf31e..9c6b0fb62 100644 --- a/articles/java/spring-framework/migrate-kafka-to-passwordless-connection.md +++ b/articles/java/spring-framework/migrate-kafka-to-passwordless-connection.md @@ -78,11 +78,11 @@ If you want to run this sample locally with Microsoft Entra authentication, be s :::image type="content" source="media/migrate-kafka-to-passwordless-connection/migration-role-eventhubs.png" alt-text="Screenshot of Azure portal Access Control (IAM) page of Event Hubs Namespace resource with Add role assignment highlighted." lightbox="media/migrate-kafka-to-passwordless-connection/migration-role-eventhubs.png"::: -1. Use the search box to filter the results to the desired role. For this example, search for *Azure Event Hubs Data Sender* and *Azure Event Hubs Data Receiver* and select the matching result and then choose **Next**. +1. Use the search box to filter the results to the desired role. For this example, search for **Azure Event Hubs Data Sender** and **Azure Event Hubs Data Receiver** and select the matching result and then choose **Next**. 1. Under **Assign access to**, select **User, group, or service principal**, and then choose **Select members**. -1. In the dialog, search for your Microsoft Entra username (usually your *user@domain* email address) and then choose **Select** at the bottom of the dialog. +1. In the dialog, search for your Microsoft Entra username (usually your **user@domain** email address) and then choose **Select** at the bottom of the dialog. 1. Select **Review + assign** to go to the final page, and then **Review + assign** again to complete the process. @@ -120,7 +120,7 @@ To authenticate using the Azure CLI, use the following steps: --query "id" --output tsv) ``` -1. Use the following commands to assign *Azure Event Hubs Data Sender* and *Azure Event Hubs Data Receiver* roles to your account. +1. Use the following commands to assign `Azure Event Hubs Data Sender` and `Azure Event Hubs Data Receiver` roles to your account. ```azurecli az role assignment create \ @@ -147,7 +147,7 @@ Next, use the following steps to update your Spring Kafka application to use pas #### [Java](#tab/java-kafka) -1. Inside your project, open the *pom.xml* file and add the following reference: +1. Inside your project, open the **pom.xml** file and add the following reference: ```xml @@ -367,7 +367,7 @@ The following steps show you how to assign a system-assigned managed identity fo ##### [Service Connector](#tab/service-connector) -When you use Service Connector, it can help to assign the system-assigned managed identity to your Azure hosting environment, and then configure the *Azure Event Hubs Data Sender* and *Azure Event Hubs Data Receiver* roles for the managed identity. +When you use Service Connector, it can help to assign the system-assigned managed identity to your Azure hosting environment, and then configure the `Azure Event Hubs Data Sender` and `Azure Event Hubs Data Receiver` roles for the managed identity. The following compute services are currently supported: @@ -386,7 +386,7 @@ For this migration guide, you'll use App Service, but the steps are similar for - **Service type**: Choose **Event Hubs**. - **Subscription**: Select the subscription you'd like to use. - - **Connection Name**: Enter a name for your connection, such as *connector_appservice_eventhub*. + - **Connection Name**: Enter a name for your connection, such as **connector_appservice_eventhub**. - **Namespace**: Select the Event Hubs namespace you'd like to use. - **Client type**: Leave the default value selected or choose the specific client you'd like to use. @@ -398,7 +398,7 @@ For this migration guide, you'll use App Service, but the steps are similar for 1. Leave the default values selected, and then select **Next: Review + Create**. 1. After Azure validates your settings, select **Create**. -The Service Connector will automatically assign a system-assigned managed identity for the app service. The connector will also assign the managed identity roles of *Azure Event Hubs Data Sender* and *Azure Event Hubs Data Receiver* for the Event Hubs instance you selected. +The Service Connector will automatically assign a system-assigned managed identity for the app service. The connector will also assign the managed identity roles of `Azure Event Hubs Data Sender` and `Azure Event Hubs Data Receiver` for the Event Hubs instance you selected. ##### [Container Apps](#tab/container-apps) @@ -551,7 +551,7 @@ Next, grant permissions to the managed identity you created to access your Event If you connected your services using the Service Connector, you don't need to complete this step. The following necessary configurations were handled for you: -- If you selected a managed identity when you created the connection, a system-assigned managed identity was created for your app and assigned the *Azure Event Hubs Data Sender* and *Azure Event Hubs Data Receiver* roles on the Event Hubs. +- If you selected a managed identity when you created the connection, a system-assigned managed identity was created for your app and assigned the `Azure Event Hubs Data Sender` and `Azure Event Hubs Data Receiver` roles on the Event Hubs. - If you chose to use a connection string, the connection string was added as an app environment variable. @@ -562,7 +562,7 @@ If you connected your services using the Service Connector, you don't need to co > > 1. In the Azure portal, navigate to **Azure Spring Apps**, then choose the app you use. > 2. Select **Identity** on the navigation menu, and on the **System assigned** tab, select **Azure role assignments**. -> 3. Select **Add role assignments**, search for *Azure Event Hubs Data Sender* and *Azure Event Hubs Data Receiver*, select the matching result, and then select **Save**. +> 3. Select **Add role assignments**, search for **Azure Event Hubs Data Sender** and **Azure Event Hubs Data Receiver**, select the matching result, and then select **Save**. 1. In the Azure portal, locate your Event Hubs namespace using the main search bar or the navigation pane. @@ -574,11 +574,11 @@ If you connected your services using the Service Connector, you don't need to co :::image type="content" source="media/migrate-kafka-to-passwordless-connection/migration-role-eventhubs.png" alt-text="Screenshot of Azure portal Access control (IAM) page of Event Hubs Namespace resource with Add role assignment menu option highlighted." lightbox="media/migrate-kafka-to-passwordless-connection/migration-role-eventhubs.png"::: -1. Use the search box to filter the results to the desired role. For this example, search for *Azure Event Hubs Data Sender* and *Azure Event Hubs Data Receiver*, select the matching result, and then select **Next**. +1. Use the search box to filter the results to the desired role. For this example, search for **Azure Event Hubs Data Sender** and **Azure Event Hubs Data Receiver**, select the matching result, and then select **Next**. 1. Under **Assign access to**, select **Managed identity**, and then select **Select members**. -1. In the flyout, search for the subscription where hosting service is located. Then, select *All system-assigned managed identities*, and select the managed identity of your hosting service. Select the system assigned identity, and then select **Select** to close the flyout menu. +1. In the flyout, search for the subscription where hosting service is located. Then, select **All system-assigned managed identities**, and select the managed identity of your hosting service. Select the system assigned identity, and then select **Select** to close the flyout menu. > [!NOTE] > If you use Azure Kubernetes Service, select **User-assigned managed identities** and then select the managed identity of the Kubernetes cluster, which has a name with the following structure: `-agentpool`. diff --git a/articles/java/spring-framework/migrate-mysql-to-passwordless-connection.md b/articles/java/spring-framework/migrate-mysql-to-passwordless-connection.md index 9af7bc13a..16534cd89 100644 --- a/articles/java/spring-framework/migrate-mysql-to-passwordless-connection.md +++ b/articles/java/spring-framework/migrate-mysql-to-passwordless-connection.md @@ -91,7 +91,7 @@ az identity create \ ``` > [!IMPORTANT] -> After creating the user-assigned identity, ask your *Global Administrator* or *Privileged Role Administrator* to grant the following permissions for this identity: `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.ALL`. For more information, see the [Permissions](/azure/mysql/flexible-server/concepts-azure-ad-authentication#permissions) section of [Active Directory authentication](/azure/mysql/flexible-server/concepts-azure-ad-authentication). +> After creating the user-assigned identity, ask your Global Administrator or Privileged Role Administrator to grant the following permissions for this identity: `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.ALL`. For more information, see the [Permissions](/azure/mysql/flexible-server/concepts-azure-ad-authentication#permissions) section of [Active Directory authentication](/azure/mysql/flexible-server/concepts-azure-ad-authentication). Run the following command to assign the identity to the MySQL server for creating the Microsoft Entra admin: @@ -154,7 +154,7 @@ az mysql server firewall-rule create \ Next, create a non-admin Microsoft Entra user and grant all permissions on the `$AZ_DATABASE_NAME` database to it. You can change the database name `$AZ_DATABASE_NAME` to fit your needs. -Create a SQL script called *create_ad_user.sql* for creating a non-admin user. Add the following contents and save it locally: +Create a SQL script called **create_ad_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash export AZ_MYSQL_AD_NON_ADMIN_USERID=$(az ad signed-in-user show --query id --output tsv) @@ -202,7 +202,7 @@ Next, use the following steps to update your code to use passwordless connection ``` -1. Enable the Azure MySQL authentication plugin in the JDBC URL. Identify the locations in your code that currently create a `java.sql.Connection` to connect to Azure Database for MySQL. Update `url` and `user` in your *application.properties* file to match the following values: +1. Enable the Azure MySQL authentication plugin in the JDBC URL. Identify the locations in your code that currently create a `java.sql.Connection` to connect to Azure Database for MySQL. Update `url` and `user` in your **application.properties** file to match the following values: ```properties url=jdbc:mysql://$AZ_DATABASE_SERVER_NAME.mysql.database.azure.com:3306/$AZ_DATABASE_NAME?serverTimezone=UTC&sslMode=REQUIRED&defaultAuthenticationPlugin=com.azure.identity.extensions.jdbc.mysql.AzureMysqlAuthenticationPlugin&authenticationPlugins=com.azure.identity.extensions.jdbc.mysql.AzureMysqlAuthenticationPlugin @@ -235,7 +235,7 @@ Next, use the following steps to update your code to use passwordless connection > [!NOTE] > For more information about how to manage Spring Cloud Azure library versions by using a bill of materials (BOM), see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -1. Update the *application.yaml* or *application.properties* file as shown in the following example. Change the `spring.datasource.username` to the Microsoft Entra user, remove the `spring.datasource.password` property, and add `spring.datasource.azure.passwordless-enabled=true`. +1. Update the **application.yaml** or **application.properties** file as shown in the following example. Change the `spring.datasource.username` to the Microsoft Entra user, remove the `spring.datasource.password` property, and add `spring.datasource.azure.passwordless-enabled=true`. ```yaml spring: @@ -279,7 +279,7 @@ The following steps show you how to assign a system-assigned managed identity fo ##### [Service Connector](#tab/service-connector) -When you use Service Connector, it can help to assign the system-assigned managed identity for your Azure hosting environment. However, Azure portal doesn’t support configuring Azure Database this way, so you need to use Azure CLI to assign the identity. +When you use Service Connector, it can help to assign the system-assigned managed identity for your Azure hosting environment. However, Azure portal doesn't support configuring Azure Database this way, so you need to use Azure CLI to assign the identity. ##### [Container Apps](#tab/container-apps) @@ -344,7 +344,7 @@ export AZ_IDENTITY_RESOURCE_ID=$(az identity create \ ``` > [!IMPORTANT] -> After creating the user-assigned identity, ask your *Global Administrator* or *Privileged Role Administrator* to grant the following permissions for this identity: `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.ALL`. For more information, see the [Permissions](/azure/mysql/flexible-server/concepts-azure-ad-authentication#permissions) section of [Active Directory authentication](/azure/mysql/flexible-server/concepts-azure-ad-authentication). +> After creating the user-assigned identity, ask your Global Administrator or Privileged Role Administrator to grant the following permissions for this identity: `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.ALL`. For more information, see the [Permissions](/azure/mysql/flexible-server/concepts-azure-ad-authentication#permissions) section of [Active Directory authentication](/azure/mysql/flexible-server/concepts-azure-ad-authentication). Then, install the [Service Connector](/azure/service-connector/overview) passwordless extension for the Azure CLI: @@ -447,7 +447,7 @@ Next, grant permissions to the managed identity you assigned to access your MySQ These steps will create a Microsoft Entra user for the managed identity and grant all permissions for the database `$AZ_DATABASE_NAME` to it. You can change the database name `$AZ_DATABASE_NAME` to fit your needs. -First, create a SQL script called *create_ad_user.sql* for creating a non-admin user. Add the following contents and save it locally: +First, create a SQL script called **create_ad_user.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash export AZ_MYSQL_AD_MI_USERID=$(az ad sp show --id $AZ_MI_OBJECT_ID --query appId --output tsv) @@ -486,7 +486,7 @@ properties.put("user", "$AZ_MYSQL_AD_MI_USERNAME"); ### [Spring](#tab/spring) -Update the *application.yaml* or *application.properties* file. Change the `spring.datasource.username` to the user created for the managed identity. +Update the **application.yaml** or **application.properties** file. Change the `spring.datasource.username` to the user created for the managed identity. ```yaml spring: diff --git a/articles/java/spring-framework/migrate-postgresql-to-passwordless-connection.md b/articles/java/spring-framework/migrate-postgresql-to-passwordless-connection.md index ba6cfde99..4faa69390 100644 --- a/articles/java/spring-framework/migrate-postgresql-to-passwordless-connection.md +++ b/articles/java/spring-framework/migrate-postgresql-to-passwordless-connection.md @@ -126,7 +126,7 @@ az postgres flexible-server firewall-rule create \ Next, create a non-admin Microsoft Entra user and grant all permissions on the `$AZ_DATABASE_NAME` database to it. You can change the database name `$AZ_DATABASE_NAME` to fit your needs. -Create a SQL script called *create_ad_user_local.sql* for creating a non-admin user. Add the following contents and save it locally: +Create a SQL script called **create_ad_user_local.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash cat << EOF > create_ad_user_local.sql @@ -169,7 +169,7 @@ Next, use the following steps to update your code to use passwordless connection ``` -1. Enable the Azure PostgreSQL authentication plugin in JDBC URL. Identify the locations in your code that currently create a `java.sql.Connection` to connect to Azure Database for PostgreSQL. Update `url` and `user` in your *application.properties* file to match the following values: +1. Enable the Azure PostgreSQL authentication plugin in JDBC URL. Identify the locations in your code that currently create a `java.sql.Connection` to connect to Azure Database for PostgreSQL. Update `url` and `user` in your **application.properties** file to match the following values: ```properties url=jdbc:postgresql://$AZ_DATABASE_SERVER_NAME.postgres.database.azure.com:5432/$AZ_DATABASE_NAME?sslmode=require&authenticationPluginClassName=com.azure.identity.extensions.jdbc.postgresql.AzurePostgresqlAuthenticationPlugin @@ -192,7 +192,7 @@ Next, use the following steps to update your code to use passwordless connection > [!NOTE] > For more information about how to manage Spring Cloud Azure library versions by using a bill of materials (BOM), see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -1. Update the *application.yaml* or *application.properties* file as shown in the following example. Change the `spring.datasource.username` to the Microsoft Entra user, remove the `spring.datasource.password` property, and add `spring.datasource.azure.passwordless-enabled=true`. +1. Update the **application.yaml** or **application.properties** file as shown in the following example. Change the `spring.datasource.username` to the Microsoft Entra user, remove the `spring.datasource.password` property, and add `spring.datasource.azure.passwordless-enabled=true`. ```yaml spring: @@ -397,7 +397,7 @@ If you connected your services using Service Connector, the previous step's comm The following steps will create a Microsoft Entra user for the managed identity and grant all permissions for the database `$AZ_DATABASE_NAME` to it. You can change the database name `$AZ_DATABASE_NAME` to fit your needs. -First, create a SQL script called *create_ad_user_mi.sql* for creating a non-admin user. Add the following contents and save it locally: +First, create a SQL script called **create_ad_user_mi.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash export AZ_POSTGRESQL_AD_MI_USERNAME=$(az ad sp show \ @@ -441,7 +441,7 @@ properties.put("user", "$AZ_POSTGRESQL_AD_MI_USERNAME"); ### [Spring](#tab/spring) -Update the *application.yaml* or *application.properties* file. Change the `spring.datasource.username` to the user created for the managed identity. +Update the **application.yaml** or **application.properties** file. Change the `spring.datasource.username` to the user created for the managed identity. ```yaml spring: diff --git a/articles/java/spring-framework/migrate-sql-database-to-passwordless-connection.md b/articles/java/spring-framework/migrate-sql-database-to-passwordless-connection.md index 71b757a70..8eb4f175a 100644 --- a/articles/java/spring-framework/migrate-sql-database-to-passwordless-connection.md +++ b/articles/java/spring-framework/migrate-sql-database-to-passwordless-connection.md @@ -135,7 +135,7 @@ Next, use the following steps to update your code to use passwordless connection > [!NOTE] > For more information about how to manage Spring Cloud Azure library versions by using a bill of materials (BOM), see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -1. Update the *application.yaml* or *application.properties* file as shown in the following example. Remove `spring.datasource.username` and `spring.datasource.password` properties. +1. Update the **application.yaml** or **application.properties** file as shown in the following example. Remove `spring.datasource.username` and `spring.datasource.password` properties. ```yaml spring: diff --git a/articles/java/spring-framework/migration-guide-for-4.0.md b/articles/java/spring-framework/migration-guide-for-4.0.md index 62697d3b6..1ccca6232 100644 --- a/articles/java/spring-framework/migration-guide-for-4.0.md +++ b/articles/java/spring-framework/migration-guide-for-4.0.md @@ -14,7 +14,7 @@ This guide helps with migration to Spring Cloud Azure 4.0 from legacy Azure Spri ## Introduction -We'll call libraries whose group ID and artifact ID follow the pattern `com.azure.spring:spring-cloud-azure-*` the **modern** libraries, and those with pattern `com.azure.spring:azure-spring-boot-*`, `com.azure.spring:azure-spring-cloud-*`, or `com.azure.spring:azure-spring-integration-*` the *legacy* libraries. +We'll call libraries whose group ID and artifact ID follow the pattern `com.azure.spring:spring-cloud-azure-*` the *modern* libraries, and those with pattern `com.azure.spring:azure-spring-boot-*`, `com.azure.spring:azure-spring-cloud-*`, or `com.azure.spring:azure-spring-integration-*` the *legacy* libraries. This guide will focus on side-by-side comparisons for similar configurations between the modern and legacy libraries. @@ -152,7 +152,7 @@ A chained credential, the `DefaultAzureCredential` bean is auto-configured by de ### Properties migration -We've created an *additional-spring-configuration-metadata.json* file to smooth the property migration when using with `spring-boot-properties-migrator`. First, add the following property migrator to your application: +We've created an **additional-spring-configuration-metadata.json** file to smooth the property migration when using with `spring-boot-properties-migrator`. First, add the following property migrator to your application: ```xml @@ -162,15 +162,15 @@ We've created an *additional-spring-configuration-metadata.json* file to smooth ``` -Or, if you’re using Gradle: +Or, if you're using Gradle: ```shell runtime("org.springframework.boot:spring-boot-properties-migrator") ``` -If you run the app, it will identify the properties that are no longer managed by Spring Cloud Azure. If there's a replacement, it will temporarily remap the property for you with a warning. If there isn’t a replacement, an error report will give you more information. Either way, the configuration has to be updated and the dependency removed once you've updated the configuration. +If you run the app, it will identify the properties that are no longer managed by Spring Cloud Azure. If there's a replacement, it will temporarily remap the property for you with a warning. If there isn't a replacement, an error report will give you more information. Either way, the configuration has to be updated and the dependency removed once you've updated the configuration. -Before you move on, it's a good idea to use the search feature of your IDE to double-check that you aren’t using one of the properties you’ve migrated in an integration test. +Before you move on, it's a good idea to use the search feature of your IDE to double-check that you aren't using one of the properties you've migrated in an integration test. > [!NOTE] > We've changed many configuration properties in this change. Using the `spring-boot-properties-migrator` will help smooth your migration. @@ -181,11 +181,11 @@ The modern `spring-cloud-azure-starter` enables you to define properties that ap | Prefix | Description | |---------------------------------|---------------------------------------------------------------| -| *spring.cloud.azure*.client | Configures the transport clients underneath each Azure SDK. | -| *spring.cloud.azure*.credential | Configures how to authenticate with Microsoft Entra ID. | -| *spring.cloud.azure*.profile | Configures the Azure cloud environment. | -| *spring.cloud.azure*.proxy | Configures the proxy options, apply to all Azure SDK clients. | -| *spring.cloud.azure*.retry | Configures the retry options, apply to all Azure SDK clients. The retry options have supported part of the SDKs, there’s no `spring.cloud.azure.cosmos.retry`. | +| `*spring.cloud.azure*.client` | Configures the transport clients underneath each Azure SDK. | +| `*spring.cloud.azure*.credential` | Configures how to authenticate with Microsoft Entra ID. | +| `*spring.cloud.azure*.profile` | Configures the Azure cloud environment. | +| `*spring.cloud.azure*.proxy` | Configures the proxy options, apply to all Azure SDK clients. | +| `*spring.cloud.azure*.retry` | Configures the retry options, apply to all Azure SDK clients. The retry options have supported part of the SDKs, there's no `spring.cloud.azure.cosmos.retry`. | For a full list of configurations, see [Spring Cloud Azure configuration properties](./configuration-properties-all.md). @@ -282,7 +282,7 @@ The following table shows the Removed dependencies: This section includes the changes about the properties added, removed and changed. -* *The following two points are the main to pay your attention to*: +* The following two points are the main to pay your attention to: 1. All configuration property names' prefix changed from `azure.activedirectory` to `spring.cloud.azure.active-directory`. 1. New property `spring.cloud.azure.active-directory.enabled` is added to enable/disable Microsoft Entra related features. The default value is `false`. @@ -317,21 +317,21 @@ The following table shows the property mappings between `azure-spring-boot-start > | azure.activedirectory.user-group.allowed-group-names | spring.cloud.azure.active-directory.user-group.allowed-group-names | > | azure.activedirectory.user-name-attribute | spring.cloud.azure.active-directory.user-name-attribute | -* *The value type of the following properties is changed from `long` to `Duration`*: +* The value type of the following properties is changed from `long` to `Duration`: * `jwt-connect-timeout` * `jwt-read-timeout` * `jwk-set-cache-lifespan` * `jwk-set-cache-refresh-time`. -* *The following properties are removed*: +* The following properties are removed: * azure.activedirectory.allow-telemetry * azure.activedirectory.user-group.enable-full-list * azure.activedirectory.graph-base-uri * azure.activedirectory.graph-membership-uri -* *The following properties are added*: +* The following properties are added: * spring.cloud.azure.active-directory.enabled * spring.cloud.azure.active-directory.profile.environment.microsoft-graph-endpoint @@ -342,7 +342,7 @@ The following table shows the property mappings between `azure-spring-boot-start Here are some examples of migration: -* *Example 1. Case 1* +* Example 1. Case 1 * For legacy: azure.activedirectory.graph-membership-uri=https://graph.microsoft.com/v1.0/me/memberOf @@ -351,7 +351,7 @@ Here are some examples of migration: spring.cloud.azure.active-directory.profile.environment.microsoft-graph-endpoint=`https://graph.microsoft.com/` + spring.cloud.azure.active-directory.user-group.use-transitive-members=`false` -* *Example 2. Case 2* +* Example 2. Case 2 * For legacy: azure.activedirectory.graph-membership-uri=https://graph.microsoft.com/v1.0/me/transitiveMemberOf @@ -385,7 +385,7 @@ The following table shows the class mappings from `azure-spring-boot-starter-act This section lists the removed classes from azure-spring-boot-starter-active-directory. -* *Removed legacy class* +* Removed legacy class * com.azure.spring.aad.webapp.AADHandleConditionalAccessFilter * com.azure.spring.aad.webapi.validator.AADJwtAudienceValidator @@ -429,23 +429,23 @@ The following table shows the property mappings from `azure-spring-boot-starter- > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |-----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| -> | *azure.activedirectory.b2c*.authenticate-additional-parameters | *spring.cloud.azure.active-directory.b2c*.authenticate-additional-parameters | -> | *azure.activedirectory.b2c*.authorization-clients | *spring.cloud.azure.active-directory.b2c*.authorization-clients | -> |*azure.activedirectory.b2c*.authorization-clients..authorization-grant-type | *spring.cloud.azure.active-directory.b2c*.authorization-clients..authorization-grant-type | -> | *azure.activedirectory.b2c*.authorization-clients..scopes | *spring.cloud.azure.active-directory.b2c*.authorization-clients..scopes | -> | *azure.activedirectory.b2c*.app-id-uri | *spring.cloud.azure.active-directory.b2c*.app-id-uri | -> | *azure.activedirectory.b2c*.base-uri | *spring.cloud.azure.active-directory.b2c*.base-uri | -> | *azure.activedirectory.b2c*.client-id | *spring.cloud.azure.active-directory.b2c*.credential.client-id | -> | *azure.activedirectory.b2c*.client-secret | *spring.cloud.azure.active-directory.b2c*.credential.client-secret | -> | *azure.activedirectory.b2c*.jwt-connect-timeout | *spring.cloud.azure.active-directory.b2c*.jwt-connect-timeout | -> | *azure.activedirectory.b2c*.jwt-read-timeout | *spring.cloud.azure.active-directory.b2c*.jwt-read-timeout | -> | *azure.activedirectory.b2c*.jwt-size-limit | *spring.cloud.azure.active-directory.b2c*.jwt-size-limit | -> | *azure.activedirectory.b2c*.login-flow | *spring.cloud.azure.active-directory.b2c*.login-flow | -> | *azure.activedirectory.b2c*.logout-success-url | *spring.cloud.azure.active-directory.b2c*.logout-success-url | -> | *azure.activedirectory.b2c*.reply-url | *spring.cloud.azure.active-directory.b2c*.reply-url | -> | *azure.activedirectory.b2c*.tenant-id | *spring.cloud.azure.active-directory.b2c*.profile.tenant-id | -> | *azure.activedirectory.b2c*.user-flows | *spring.cloud.azure.active-directory.b2c*.user-flows | -> | *azure.activedirectory.b2c*.user-name-attribute-name | *spring.cloud.azure.active-directory.b2c*.user-name-attribute-name | +> | `*azure.activedirectory.b2c*.authenticate-additional-parameters` | `*spring.cloud.azure.active-directory.b2c*.authenticate-additional-parameters` | +> | `*azure.activedirectory.b2c*.authorization-clients` | `*spring.cloud.azure.active-directory.b2c*.authorization-clients` | +> | `*azure.activedirectory.b2c*.authorization-clients..authorization-grant-type` | `*spring.cloud.azure.active-directory.b2c*.authorization-clients..authorization-grant-type` | +> | `*azure.activedirectory.b2c*.authorization-clients..scopes` | `*spring.cloud.azure.active-directory.b2c*.authorization-clients..scopes` | +> | `*azure.activedirectory.b2c*.app-id-uri` | `*spring.cloud.azure.active-directory.b2c*.app-id-uri` | +> | `*azure.activedirectory.b2c*.base-uri` | `*spring.cloud.azure.active-directory.b2c*.base-uri` | +> | `*azure.activedirectory.b2c*.client-id` | `*spring.cloud.azure.active-directory.b2c*.credential.client-id` | +> | `*azure.activedirectory.b2c*.client-secret` | `*spring.cloud.azure.active-directory.b2c*.credential.client-secret` | +> | `*azure.activedirectory.b2c*.jwt-connect-timeout` | `*spring.cloud.azure.active-directory.b2c*.jwt-connect-timeout` | +> | `*azure.activedirectory.b2c*.jwt-read-timeout` | `*spring.cloud.azure.active-directory.b2c*.jwt-read-timeout` | +> | `*azure.activedirectory.b2c*.jwt-size-limit` | `*spring.cloud.azure.active-directory.b2c*.jwt-size-limit` | +> | `*azure.activedirectory.b2c*.login-flow` | `*spring.cloud.azure.active-directory.b2c*.login-flow` | +> | `*azure.activedirectory.b2c*.logout-success-url` | `*spring.cloud.azure.active-directory.b2c*.logout-success-url` | +> | `*azure.activedirectory.b2c*.reply-url` | `*spring.cloud.azure.active-directory.b2c*.reply-url` | +> | `*azure.activedirectory.b2c*.tenant-id` | `*spring.cloud.azure.active-directory.b2c*.profile.tenant-id` | +> | `*azure.activedirectory.b2c*.user-flows` | `*spring.cloud.azure.active-directory.b2c*.user-flows` | +> | `*azure.activedirectory.b2c*.user-name-attribute-name` | `*spring.cloud.azure.active-directory.b2c*.user-name-attribute-name` | * Removed properties from azure-spring-boot-starter-active-directory-b2c: @@ -494,12 +494,12 @@ The following table shows the class mappings from `azure-spring-boot-starter-cos > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |--------------------------------------|---------------------------------------------------| -> |*azure.cosmos*.connection-mode |*spring.cloud.azure.cosmos*.connection-mode | -> |*azure.cosmos*.consistency-level |*spring.cloud.azure.cosmos*.consistency-level | -> |*azure.cosmos*.database |*spring.cloud.azure.cosmos*.database | -> |*azure.cosmos*.key |*spring.cloud.azure.cosmos*.key | -> |*azure.cosmos*.populate-query-metrics |*spring.cloud.azure.cosmos*.populate-query-metrics | -> |*azure.cosmos*.uri |*spring.cloud.azure.cosmos*.endpoint | +> | `*azure.cosmos*.connection-mode` | `*spring.cloud.azure.cosmos*.connection-mode` | +> | `*azure.cosmos*.consistency-level` | `*spring.cloud.azure.cosmos*.consistency-level` | +> | `*azure.cosmos*.database` | `*spring.cloud.azure.cosmos*.database` | +> | `*azure.cosmos*.key` | `*spring.cloud.azure.cosmos*.key` | +> | `*azure.cosmos*.populate-query-metrics` | `*spring.cloud.azure.cosmos*.populate-query-metrics` | +> | `*azure.cosmos*.uri` | `*spring.cloud.azure.cosmos*.endpoint` | ### From azure-spring-boot-starter-keyvault-secrets to spring-cloud-azure-starter-keyvault-secrets @@ -523,17 +523,17 @@ The following table shows the property mappings from `azure-spring-boot-starter- > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| -> | *azure.keyvault*.case-sensitive-keys | *spring.cloud.azure.keyvault.secret*.property-source[n].case-sensitive | -> | *azure.keyvault*.certificate-password | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-password | -> | *azure.keyvault*.certificate-path | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-path | -> | *azure.keyvault*.client-id | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-id | -> | *azure.keyvault*.client-key | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-secret | -> | *azure.keyvault*.enabled | *spring.cloud.azure.keyvault.secret*.property-source-enabled and *spring.cloud.azure.keyvault.secret*.property-source-enabled | -> | *azure.keyvault*.order | No longer supported. Use the order in property-source[n] instead. | -> | *azure.keyvault*.refresh-interval | *spring.cloud.azure.keyvault.secret*.property-source[n].refresh-interval | -> | *azure.keyvault*.secret-keys | *spring.cloud.azure.keyvault.secret*.property-source[n].secret-keys | -> | *azure.keyvault*.tenant-id | *spring.cloud.azure.keyvault.secret*.property-source[n].profile.tenant-id | -> | *azure.keyvault*.uri | *spring.cloud.azure.keyvault.secret*.property-source[n].endpoint | +> | `*azure.keyvault*.case-sensitive-keys` | `*spring.cloud.azure.keyvault.secret*.property-source[n].case-sensitive` | +> | `*azure.keyvault*.certificate-password` | `*spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-password` | +> | `*azure.keyvault*.certificate-path` | `*spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-path` | +> | `*azure.keyvault*.client-id` | `*spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-id` | +> | `*azure.keyvault*.client-key` | `*spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-secret` | +> | `*azure.keyvault*.enabled` | `*spring.cloud.azure.keyvault.secret*.property-source-enabled` and `*spring.cloud.azure.keyvault.secret*.property-source-enabled` | +> | `*azure.keyvault*.order` | No longer supported. Use the order in property-source[n] instead. | +> | `*azure.keyvault*.refresh-interval` | `*spring.cloud.azure.keyvault.secret*.property-source[n].refresh-interval` | +> | `*azure.keyvault*.secret-keys` | `*spring.cloud.azure.keyvault.secret*.property-source[n].secret-keys` | +> | `*azure.keyvault*.tenant-id` | `*spring.cloud.azure.keyvault.secret*.property-source[n].profile.tenant-id` | +> | `*azure.keyvault*.uri` | `*spring.cloud.azure.keyvault.secret*.property-source[n].endpoint` | * Removed properties from spring-cloud-azure-starter-keyvault-secrets @@ -586,9 +586,9 @@ The following table shows the property mappings from `azure-spring-boot-starter- | Legacy properties | Modern properties | |-------------------------------|------------------------------------------------| -| *azure.storage*.account-name | *spring.cloud.azure.storage.blob*.account-name | -| *azure.storage*.account-key | *spring.cloud.azure.storage.blob*.account-key | -| *azure.storage*.blob-endpoint | *spring.cloud.azure.storage.blob*.endpoint | +| `*azure.storage*.account-name` | `*spring.cloud.azure.storage.blob*.account-name` | +| `*azure.storage*.account-key` | `*spring.cloud.azure.storage.blob*.account-key` | +| `*azure.storage*.blob-endpoint` | `*spring.cloud.azure.storage.blob*.endpoint` | #### API changes @@ -622,9 +622,9 @@ The following table shows the property mappings from `azure-spring-boot-starter- | Legacy properties | Modern properties | |-------------------------------|-----------------------------------------------------| -| *azure.storage*.account-name | *spring.cloud.azure.storage.fileshare*.account-name | -| *azure.storage*.account-key | *spring.cloud.azure.storage.fileshare*.account-key | -| *azure.storage*.file-endpoint | *spring.cloud.azure.storage.fileshare*.endpoint | +| `*azure.storage*.account-name` | `*spring.cloud.azure.storage.fileshare*.account-name` | +| `*azure.storage*.account-key` | `*spring.cloud.azure.storage.fileshare*.account-key` | +| `*azure.storage*.file-endpoint` | `*spring.cloud.azure.storage.fileshare*.endpoint` | #### API changes @@ -662,12 +662,12 @@ The following table shows property mappings from `azure-spring-cloud-starter-eve > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |----------------------------------------------------------|--------------------------------------------------------------------------| -> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.eventhubs*.resource.resource-group | -> | *spring.cloud.azure.eventhub*.namespace | *spring.cloud.azure.eventhubs*.namespace | -> | *spring.cloud.azure.eventhub*.connection-string | *spring.cloud.azure.eventhubs*.connection-string | -> | *spring.cloud.azure.eventhub*.checkpoint-storage-account | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name | -> | *spring.cloud.azure.eventhub*.checkpoint-access-key | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key | -> | *spring.cloud.azure.eventhub*.checkpoint-container | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name | +> | `*spring.cloud.azure*.resource-group` | `*spring.cloud.azure.eventhubs*.resource.resource-group` | +> | `*spring.cloud.azure.eventhub*.namespace` | `*spring.cloud.azure.eventhubs*.namespace` | +> | `*spring.cloud.azure.eventhub*.connection-string` | `*spring.cloud.azure.eventhubs*.connection-string` | +> | `*spring.cloud.azure.eventhub*.checkpoint-storage-account` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name` | +> | `*spring.cloud.azure.eventhub*.checkpoint-access-key` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key` | +> | `*spring.cloud.azure.eventhub*.checkpoint-container` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name` | For example, change from: @@ -894,13 +894,13 @@ The following table shows the property mappings from `azure-spring-cloud-starter > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -> |*spring.cloud.azure*.resource-group |*spring.cloud.azure.servicebus*.resource.resource-group | -> |*spring.cloud.azure.servicebus*.transport-type |*spring.cloud.azure.servicebus*.client.transport-type | -> |*spring.cloud.azure.servicebus*.retry-options.retry-mode |*spring.cloud.azure.servicebus*.retry.mode | -> |*spring.cloud.azure.servicebus*.retry-options.max-retries |*spring.cloud.azure.servicebus*.retry.exponential.max-retries or *spring.cloud.azure.servicebus*.retry.fixed.max-retries, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | -> |*spring.cloud.azure.servicebus*.retry-options.delay |*spring.cloud.azure.servicebus*.retry.exponential.base-delay or *spring.cloud.azure.servicebus*.retry.fixed.delay, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | -> |*spring.cloud.azure.servicebus*.retry-options.max-delay |*spring.cloud.azure.servicebus*.retry.exponential.max-delay | -> |*spring.cloud.azure.servicebus*.retry-options.try-timeout |*spring.cloud.azure.servicebus*.retry.try-timeout | +> | `*spring.cloud.azure*.resource-group` | `*spring.cloud.azure.servicebus*.resource.resource-group` | +> | `*spring.cloud.azure.servicebus*.transport-type` | `*spring.cloud.azure.servicebus*.client.transport-type` | +> | `*spring.cloud.azure.servicebus*.retry-options.retry-mode` | `*spring.cloud.azure.servicebus*.retry.mode` | +> | `*spring.cloud.azure.servicebus*.retry-options.max-retries` | `*spring.cloud.azure.servicebus*.retry.exponential.max-retries` or `*spring.cloud.azure.servicebus*.retry.fixed.max-retries,` should be configured depending on `*spring.cloud.azure.servicebus*.retry.mode=*fixed*` or `*exponential*` | +> | `*spring.cloud.azure.servicebus*.retry-options.delay` | `*spring.cloud.azure.servicebus*.retry.exponential.base-delay` or `*spring.cloud.azure.servicebus*.retry.fixed.delay,` should be configured depending on `*spring.cloud.azure.servicebus*.retry.mode=*fixed*` or `*exponential*` | +> | `*spring.cloud.azure.servicebus*.retry-options.max-delay` | `*spring.cloud.azure.servicebus*.retry.exponential.max-delay` | +> | `*spring.cloud.azure.servicebus*.retry-options.try-timeout` | `*spring.cloud.azure.servicebus*.retry.try-timeout` | #### API changes @@ -1104,9 +1104,9 @@ The following table shows the property mappings from `azure-spring-cloud-starter > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |---------------------------------------------|------------------------------------------------------------| -> | *spring.cloud.azure.storage*.account | *spring.cloud.azure.storage.queue*.account-name | -> | *spring.cloud.azure.storage*.access-key | *spring.cloud.azure.storage.queue*.account-key | -> | *spring.cloud.azure.storage*.resource-group | *spring.cloud.azure.storage.queue*.resource.resource-group | +> | `*spring.cloud.azure.storage*.account` | `*spring.cloud.azure.storage.queue*.account-name` | +> | `*spring.cloud.azure.storage*.access-key` | `*spring.cloud.azure.storage.queue*.account-key` | +> | `*spring.cloud.azure.storage*.resource-group` | `*spring.cloud.azure.storage.queue*.resource.resource-group` | #### API changes @@ -1178,23 +1178,23 @@ The following table shows property mappings from `azure-spring-cloud-stream-bind > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| -> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.eventhubs*.resource.resource-group | -> | *spring.cloud.azure.eventhub*.namespace | *spring.cloud.azure.eventhubs*.namespace | -> | *spring.cloud.azure.eventhub*.connection-string | *spring.cloud.azure.eventhubs*.connection-string | -> | *spring.cloud.azure.eventhub*.checkpoint-storage-account | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name | -> | *spring.cloud.azure.eventhub*.checkpoint-access-key | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key | -> | *spring.cloud.azure.eventhub*.checkpoint-container | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-batch-size | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-size | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-wait-time | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-wait-time | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-mode | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.mode | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-count | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.count | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-interval | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.interval | -> |*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.start-position | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.initial-partition-event-position | +> | `*spring.cloud.azure*.resource-group` | `*spring.cloud.azure.eventhubs*.resource.resource-group` | +> | `*spring.cloud.azure.eventhub*.namespace` | `*spring.cloud.azure.eventhubs*.namespace` | +> | `*spring.cloud.azure.eventhub*.connection-string` | `*spring.cloud.azure.eventhubs*.connection-string` | +> | `*spring.cloud.azure.eventhub*.checkpoint-storage-account` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name` | +> | `*spring.cloud.azure.eventhub*.checkpoint-access-key` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key` | +> | `*spring.cloud.azure.eventhub*.checkpoint-container` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name` | +> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-batch-size` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-size` | +> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-wait-time` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-wait-time` | +> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-mode` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.mode` | +> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-count` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.count` | +> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-interval` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.interval` | +> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.start-position` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.initial-partition-event-position` | > [!NOTE] > The value type of the `start-position` configuration is also changed from an enum of `com.azure.spring.integration.core.api.StartPosition` to a `map` of `StartPositionProperties` for each partition. Thus, the key is the partition ID, and the value is of `com.azure.spring.cloud.service.eventhubs.properties.StartPositionProperties` which includes properties of offset, sequence number, enqueued date time and whether inclusive. -*Configuration migration examples* +Configuration migration examples To use the connection string for authentication and migrate the above mentioned properties, configuration changes are listed the follows: @@ -1372,26 +1372,26 @@ The following table lists the new configuration properties of `spring-cloud-azur > [!div class="mx-tdBreakAll"] > | Modern properties | Description | > |-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| -> | *spring.cloud.stream.servicebus*.bindings.binding-name.producer.entity-type | If you use the sending function, you need to set the entity-type, which you can set to topic or queue. | +> | `*spring.cloud.stream.servicebus*.bindings.binding-name.producer.entity-type` | If you use the sending function, you need to set the entity-type, which you can set to topic or queue. | The following table shows the property mappings from `azure-spring-cloud-stream-binder-servicebus-*` to `spring-cloud-azure-stream-binder-servicebus`: > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -> |*spring.cloud.azure*.resource-group |*spring.cloud.azure.servicebus*.resource.resource-group | -> |*spring.cloud.azure.servicebus*.transport-type |*spring.cloud.azure.servicebus*.client.transport-type | -> |*spring.cloud.azure.servicebus*.retry-options.retry-mode |*spring.cloud.azure.servicebus*.retry.mode | -> |*spring.cloud.azure.servicebus*.retry-options.max-retries |*spring.cloud.azure.servicebus*.retry.exponential.max-retries or *spring.cloud.azure.servicebus*.retry.fixed.max-retries, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | -> |*spring.cloud.azure.servicebus*.retry-options.delay |*spring.cloud.azure.servicebus*.retry.exponential.base-delay or *spring.cloud.azure.servicebus*.retry.fixed.delay, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | -> |*spring.cloud.azure.servicebus*.retry-options.max-delay |*spring.cloud.azure.servicebus*.retry.exponential.max-delay | -> |*spring.cloud.azure.servicebus*.retry-options.try-timeout |*spring.cloud.azure.servicebus*.retry.try-timeout | -> | *spring.cloud.stream.servicebus*.queue.bindings.* | *spring.cloud.stream.servicebus.bindings*.* | -> |*spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*concurrency* |*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls | -> |*spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*checkpoint-mode* |*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete* | -> | *spring.cloud.stream.servicebus*.topic.bindings.* | *spring.cloud.stream.servicebus.bindings*.* | -> |*spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*concurrency* |*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls | -> |*spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*checkpoint-mode* |*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete* | +> | `*spring.cloud.azure*.resource-group` | `*spring.cloud.azure.servicebus*.resource.resource-group` | +> | `*spring.cloud.azure.servicebus*.transport-type` | `*spring.cloud.azure.servicebus*.client.transport-type` | +> | `*spring.cloud.azure.servicebus*.retry-options.retry-mode` | `*spring.cloud.azure.servicebus*.retry.mode` | +> | `*spring.cloud.azure.servicebus*.retry-options.max-retries` | `*spring.cloud.azure.servicebus*.retry.exponential.max-retries` or `*spring.cloud.azure.servicebus*.retry.fixed.max-retries,` should be configured depending on `*spring.cloud.azure.servicebus*.retry.mode=*fixed*` or `*exponential*` | +> | `*spring.cloud.azure.servicebus*.retry-options.delay` | `*spring.cloud.azure.servicebus*.retry.exponential.base-delay` or `*spring.cloud.azure.servicebus*.retry.fixed.delay,` should be configured depending on `*spring.cloud.azure.servicebus*.retry.mode=*fixed*` or `*exponential*` | +> | `*spring.cloud.azure.servicebus*.retry-options.max-delay` | `*spring.cloud.azure.servicebus*.retry.exponential.max-delay` | +> | `*spring.cloud.azure.servicebus*.retry-options.try-timeout` | `*spring.cloud.azure.servicebus*.retry.try-timeout` | +> | `*spring.cloud.stream.servicebus*.queue.bindings.*` | `*spring.cloud.stream.servicebus.bindings*.*` | +> | `*spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*concurrency*` | `*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls` | +> | `*spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*checkpoint-mode*` | `*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete*` | +> | `*spring.cloud.stream.servicebus*.topic.bindings.*` | `*spring.cloud.stream.servicebus.bindings*.*` | +> | `*spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*concurrency*` | `*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls` | +> | `*spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*checkpoint-mode*` | `*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete*` | > [!NOTE] > The concurrency property will be replaced by the maxConcurrentSessions when sessionsEnabled is `true` and the maxConcurrentCalls when sessionsEnabled is `false`. @@ -1399,7 +1399,7 @@ The following table shows the property mappings from `azure-spring-cloud-stream- > [!NOTE] > Enabling auto-complete is equal to `RECORD` checkpoint mode, and oppositely the `MANUAL` mode. -*Configuration migration examples* +Configuration migration examples Legacy configuration, taking queue as example: diff --git a/articles/java/spring-framework/mysql-support.md b/articles/java/spring-framework/mysql-support.md index 123ecdda1..f8c46c895 100644 --- a/articles/java/spring-framework/mysql-support.md +++ b/articles/java/spring-framework/mysql-support.md @@ -59,8 +59,8 @@ The following table shows the Spring Cloud Azure for MySQL common configuration > | spring.datasource.azure.credential.client-certificate-password | Password of the certificate file. | > | spring.datasource.azure.credential.client-certificate-path | Path of a PEM certificate file to use when performing service principal authentication with Azure. | > | spring.datasource.azure.credential.client-id | Client ID to use when performing service principal authentication with Azure. This is a legacy property. | -> | spring.datasource.azure.credential.client-secret | Client secret to use when performing service principal authentication with Azure. This is a legacy property. | -> | spring.datasource.azure.credential.managed-identity-enabled | Whether to enable managed identity to authenticate with Azure. If *true* and the `client-id` is set, will use the client ID as user assigned managed identity client ID. The default value is *false*. | +> | spring.datasource.azure.credential.client-secret | Client secret to use when performing service principal authentication with Azure. This is a legacy property. | +> | spring.datasource.azure.credential.managed-identity-enabled | Whether to enable managed identity to authenticate with Azure. If `true` and the `client-id` is set, will use the client ID as user assigned managed identity client ID. The default value is `false`. | > | spring.datasource.azure.credential.password | Password to use when performing username/password authentication with Azure. | > | spring.datasource.azure.credential.username | Username to use when performing username/password authentication with Azure. | > | spring.datasource.azure.profile.cloud-type | Name of the Azure cloud to connect to. | @@ -94,7 +94,7 @@ The following sections show the classic Spring Boot application usage scenarios. 1. To create users and grant permission, see the [Create a MySQL non-admin user and grant permission](configure-spring-data-jdbc-with-azure-mysql.md#create-a-mysql-non-admin-user-and-grant-permission) section of [Use Spring Data JDBC with Azure Database for MySQL](configure-spring-data-jdbc-with-azure-mysql.md). -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: @@ -124,7 +124,7 @@ The following sections show the classic Spring Boot application usage scenarios. --output tsv) ``` - 1. Then, create a SQL script called *create_ad_user_sp.sql* for creating a non-admin user. Add the following contents and save it locally: + 1. Then, create a SQL script called **create_ad_user_sp.sql** for creating a non-admin user. Add the following contents and save it locally: ```bash cat << EOF > create_ad_user_sp.sql @@ -147,7 +147,7 @@ The following sections show the classic Spring Boot application usage scenarios. rm create_ad_user_sp.sql ``` -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: @@ -174,7 +174,7 @@ The following sections show the classic Spring Boot application usage scenarios. 1. To grant permissions, see the [Assign roles to the managed identity](migrate-mysql-to-passwordless-connection.md#assign-roles-to-the-managed-identity) section of [Migrate an application to use passwordless connections with Azure Database for MySQL](migrate-mysql-to-passwordless-connection.md). -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/postgresql-support.md b/articles/java/spring-framework/postgresql-support.md index 473584246..bc6a8ad1c 100644 --- a/articles/java/spring-framework/postgresql-support.md +++ b/articles/java/spring-framework/postgresql-support.md @@ -60,7 +60,7 @@ The following table shows the Spring Cloud Azure for PostgreSQL common configura > | spring.datasource.azure.credential.client-certificate-path | Path of a PEM certificate file to use when performing service principal authentication with Azure. | > | spring.datasource.azure.credential.client-id | Client ID to use when performing service principal authentication with Azure. This is a legacy property. | > | spring.datasource.azure.credential.client-secret | Client secret to use when performing service principal authentication with Azure. This is a legacy property. | -> | spring.datasource.azure.credential.managed-identity-enabled | Whether to enable managed identity to authenticate with Azure. If *true* and the `client-id` is set, will use the client ID as user assigned managed identity client ID. The default value is *false*. | +> | spring.datasource.azure.credential.managed-identity-enabled | Whether to enable managed identity to authenticate with Azure. If `true` and the `client-id` is set, will use the client ID as user assigned managed identity client ID. The default value is `false`. | > | spring.datasource.azure.credential.password | Password to use when performing username/password authentication with Azure. | > | spring.datasource.azure.credential.username | Username to use when performing username/password authentication with Azure. | > | spring.datasource.azure.profile.cloud-type | Name of the Azure cloud to connect to. | @@ -94,7 +94,7 @@ The following sections show the classic Spring Boot application usage scenarios. 1. To create users and grant permission, see the [Create a PostgreSQL non-admin user and grant permission](configure-spring-data-jdbc-with-azure-postgresql.md#create-a-postgresql-non-admin-user-and-grant-permission) section of [Use Spring Data JDBC with Azure Database for PostgreSQL](configure-spring-data-jdbc-with-azure-postgresql.md). -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: @@ -109,7 +109,7 @@ The following sections show the classic Spring Boot application usage scenarios. 1. Assign role to service principal: - 1. Create a SQL script called *create_ad_user_sp.sql* for creating a non-admin user. Add the following contents and save it locally: + 1. Create a SQL script called **create_ad_user_sp.sql** for creating a non-admin user. Add the following contents and save it locally: > [!IMPORTANT] > Make sure `` already exists in your Microsoft Entra tenant, or you won't be able to create the non-admin user. @@ -132,7 +132,7 @@ The following sections show the classic Spring Boot application usage scenarios. rm create_ad_user_sp.sql ``` -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: @@ -159,7 +159,7 @@ The following sections show the classic Spring Boot application usage scenarios. 1. To grant permissions, see the [Assign roles to the managed identity](migrate-postgresql-to-passwordless-connection.md#assign-roles-to-the-managed-identity) section of [Migrate an application to use passwordless connections with Azure Database for PostgreSQL](migrate-postgresql-to-passwordless-connection.md). -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/production-ready.md b/articles/java/spring-framework/production-ready.md index b89b09f15..e26bbf24f 100644 --- a/articles/java/spring-framework/production-ready.md +++ b/articles/java/spring-framework/production-ready.md @@ -12,11 +12,11 @@ ms.custom: devx-track-java, devx-track-extended-java **This article applies to:** ✅ Version 4.19.0 -We’ve added health indicators for App Configuration, Event Hubs, Azure Cosmos DB, Key Vault, Storage Blob, Storage Queue, and Storage File, as well as Spring Cloud Sleuth support for all HTTP-based Azure SDKs. As an example, you now can probe to determine whether a storage blob is up or down via Spring Boot actuator endpoint, as well as track dependencies and latencies going from your application to Key Vault. +We've added health indicators for App Configuration, Event Hubs, Azure Cosmos DB, Key Vault, Storage Blob, Storage Queue, and Storage File, as well as Spring Cloud Sleuth support for all HTTP-based Azure SDKs. As an example, you now can probe to determine whether a storage blob is up or down via Spring Boot actuator endpoint, as well as track dependencies and latencies going from your application to Key Vault. ## Enable health indicator -To enable the health indicators, add the Spring Cloud Azure Actuator Starter dependency to your *pom.xml* file. This dependency will also include the `spring-boot-starter-actuator`. +To enable the health indicators, add the Spring Cloud Azure Actuator Starter dependency to your **pom.xml** file. This dependency will also include the `spring-boot-starter-actuator`. ```xml @@ -29,14 +29,14 @@ The following table lists configurable properties to enable or disable health in | Azure Service | Property | |-----------------------|--------------------------------------------------------| -| App Configuration | *management.health.azure*-appconfiguration.enabled | -| Azure Cosmos DB | *management.health.azure*-cosmos.enabled | -| Event Hubs | *management.health.azure*-eventhubs.enabled | -| Key Vault Certificate | *management.health.azure*-keyvault-certificate.enabled | -| Key Vault Secret | *management.health.azure*-keyvault-secret.enabled | -| Storage Blob | *management.health.azure*-storage-blob.enabled | -| Storage File Share | *management.health.azure*-storage-fileshare.enabled | -| Storage Queue | *management.health.azure*-storage-queue.enabled | +| App Configuration | `**management.health.azure**-appconfiguration.enabled` | +| Azure Cosmos DB | `**management.health.azure**-cosmos.enabled` | +| Event Hubs | `**management.health.azure**-eventhubs.enabled` | +| Key Vault Certificate | `**management.health.azure**-keyvault-certificate.enabled` | +| Key Vault Secret | `**management.health.azure**-keyvault-secret.enabled` | +| Storage Blob | `**management.health.azure**-storage-blob.enabled` | +| Storage File Share | `**management.health.azure**-storage-fileshare.enabled` | +| Storage Queue | `**management.health.azure**-storage-queue.enabled` | > [!IMPORTANT] > Calling the health endpoint of Azure services may cause extra charges. For example, if you call `http://HOST_NAME:{port}/actuator/health/cosmos` to get Azure Cosmos DB health info, it will calculate Request Units (RUs). For more information, see [Request Units in Azure Cosmos DB](/azure/cosmos-db/request-units). @@ -48,7 +48,7 @@ The following table lists configurable properties to enable or disable health in ## Enable sleuth -When you want to trace Azure SDK activities by using Spring Cloud Sleuth, add the following Spring Cloud Azure Trace Sleuth dependency to your *pom.xml* file: +When you want to trace Azure SDK activities by using Spring Cloud Sleuth, add the following Spring Cloud Azure Trace Sleuth dependency to your **pom.xml** file: ```xml diff --git a/articles/java/spring-framework/redis-support.md b/articles/java/spring-framework/redis-support.md index d48b7c528..35271cc53 100644 --- a/articles/java/spring-framework/redis-support.md +++ b/articles/java/spring-framework/redis-support.md @@ -93,7 +93,7 @@ The following sections show the classic Spring Boot application usage scenarios. > > Remember to add the BOM `spring-cloud-azure-dependencies` along with the above dependency. For more information, see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: @@ -129,7 +129,7 @@ The following sections show the classic Spring Boot application usage scenarios. > > Remember to add the BOM `spring-cloud-azure-dependencies` along with the above dependency. For more information, see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: @@ -153,7 +153,7 @@ The following sections show the classic Spring Boot application usage scenarios. 1. To use the managed identity, you need enable the managed identity for your service and [enable Microsoft Entra authentication on your cache](/azure/azure-cache-for-redis/cache-azure-active-directory-for-authentication#enable-microsoft-entra-authentication-on-your-cache). -1. Then, add the following properties in your *application.yml* file: +1. Then, add the following properties in your **application.yml** file: ```yaml spring: @@ -218,7 +218,7 @@ Use the following steps to connect to Azure Cache for Redis: --- -2. Configure the following properties in your *application.yml* file: +2. Configure the following properties in your **application.yml** file: ```yaml spring: From 47a3a3a764b11b4595404d013a53b44d0c784088 Mon Sep 17 00:00:00 2001 From: Joshua Goldstein <183134486+JoshTheTechWriter@users.noreply.github.com> Date: Mon, 20 Jan 2025 13:00:33 -0500 Subject: [PATCH 13/21] Apply suggestions from code review --- .../migrate-mysql-to-passwordless-connection.md | 4 ++-- .../java/spring-framework/migration-guide-for-4.0.md | 10 +++++----- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/articles/java/spring-framework/migrate-mysql-to-passwordless-connection.md b/articles/java/spring-framework/migrate-mysql-to-passwordless-connection.md index 16534cd89..a8453f5bd 100644 --- a/articles/java/spring-framework/migrate-mysql-to-passwordless-connection.md +++ b/articles/java/spring-framework/migrate-mysql-to-passwordless-connection.md @@ -91,7 +91,7 @@ az identity create \ ``` > [!IMPORTANT] -> After creating the user-assigned identity, ask your Global Administrator or Privileged Role Administrator to grant the following permissions for this identity: `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.ALL`. For more information, see the [Permissions](/azure/mysql/flexible-server/concepts-azure-ad-authentication#permissions) section of [Active Directory authentication](/azure/mysql/flexible-server/concepts-azure-ad-authentication). +> After creating the user-assigned identity, ask your *Global Administrator* or *Privileged Role Administrator* to grant the following permissions for this identity: `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.ALL`. For more information, see the [Permissions](/azure/mysql/flexible-server/concepts-azure-ad-authentication#permissions) section of [Active Directory authentication](/azure/mysql/flexible-server/concepts-azure-ad-authentication). Run the following command to assign the identity to the MySQL server for creating the Microsoft Entra admin: @@ -344,7 +344,7 @@ export AZ_IDENTITY_RESOURCE_ID=$(az identity create \ ``` > [!IMPORTANT] -> After creating the user-assigned identity, ask your Global Administrator or Privileged Role Administrator to grant the following permissions for this identity: `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.ALL`. For more information, see the [Permissions](/azure/mysql/flexible-server/concepts-azure-ad-authentication#permissions) section of [Active Directory authentication](/azure/mysql/flexible-server/concepts-azure-ad-authentication). +> After creating the user-assigned identity, ask your *Global Administrator* or *Privileged Role Administrator* to grant the following permissions for this identity: `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.ALL`. For more information, see the [Permissions](/azure/mysql/flexible-server/concepts-azure-ad-authentication#permissions) section of [Active Directory authentication](/azure/mysql/flexible-server/concepts-azure-ad-authentication). Then, install the [Service Connector](/azure/service-connector/overview) passwordless extension for the Azure CLI: diff --git a/articles/java/spring-framework/migration-guide-for-4.0.md b/articles/java/spring-framework/migration-guide-for-4.0.md index 1ccca6232..0ff2a32a0 100644 --- a/articles/java/spring-framework/migration-guide-for-4.0.md +++ b/articles/java/spring-framework/migration-guide-for-4.0.md @@ -181,11 +181,11 @@ The modern `spring-cloud-azure-starter` enables you to define properties that ap | Prefix | Description | |---------------------------------|---------------------------------------------------------------| -| `*spring.cloud.azure*.client` | Configures the transport clients underneath each Azure SDK. | -| `*spring.cloud.azure*.credential` | Configures how to authenticate with Microsoft Entra ID. | -| `*spring.cloud.azure*.profile` | Configures the Azure cloud environment. | -| `*spring.cloud.azure*.proxy` | Configures the proxy options, apply to all Azure SDK clients. | -| `*spring.cloud.azure*.retry` | Configures the retry options, apply to all Azure SDK clients. The retry options have supported part of the SDKs, there's no `spring.cloud.azure.cosmos.retry`. | +| *spring.cloud.azure*.client | Configures the transport clients underneath each Azure SDK. | +| *spring.cloud.azure*.credential | Configures how to authenticate with Microsoft Entra ID. | +| *spring.cloud.azure*.profile | Configures the Azure cloud environment. | +| *spring.cloud.azure*.proxy | Configures the proxy options, apply to all Azure SDK clients. | +| *spring.cloud.azure*.retry | Configures the retry options, apply to all Azure SDK clients. The retry options have supported part of the SDKs, there's no `spring.cloud.azure.cosmos.retry`. | For a full list of configurations, see [Spring Cloud Azure configuration properties](./configuration-properties-all.md). From c337454dc71c8755bfb60afc09dfcf6563a7238d Mon Sep 17 00:00:00 2001 From: JoshTheTechWriter <183134486+JoshTheTechWriter@users.noreply.github.com> Date: Mon, 20 Jan 2025 13:14:26 -0500 Subject: [PATCH 14/21] Removed backticks from tables in migration-guide-for-4.0.md and production-ready.md. --- .../migration-guide-for-4.0.md | 164 +++++++++--------- .../java/spring-framework/production-ready.md | 20 +-- 2 files changed, 92 insertions(+), 92 deletions(-) diff --git a/articles/java/spring-framework/migration-guide-for-4.0.md b/articles/java/spring-framework/migration-guide-for-4.0.md index 0ff2a32a0..4461b5014 100644 --- a/articles/java/spring-framework/migration-guide-for-4.0.md +++ b/articles/java/spring-framework/migration-guide-for-4.0.md @@ -429,23 +429,23 @@ The following table shows the property mappings from `azure-spring-boot-starter- > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |-----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| -> | `*azure.activedirectory.b2c*.authenticate-additional-parameters` | `*spring.cloud.azure.active-directory.b2c*.authenticate-additional-parameters` | -> | `*azure.activedirectory.b2c*.authorization-clients` | `*spring.cloud.azure.active-directory.b2c*.authorization-clients` | -> | `*azure.activedirectory.b2c*.authorization-clients..authorization-grant-type` | `*spring.cloud.azure.active-directory.b2c*.authorization-clients..authorization-grant-type` | -> | `*azure.activedirectory.b2c*.authorization-clients..scopes` | `*spring.cloud.azure.active-directory.b2c*.authorization-clients..scopes` | -> | `*azure.activedirectory.b2c*.app-id-uri` | `*spring.cloud.azure.active-directory.b2c*.app-id-uri` | -> | `*azure.activedirectory.b2c*.base-uri` | `*spring.cloud.azure.active-directory.b2c*.base-uri` | -> | `*azure.activedirectory.b2c*.client-id` | `*spring.cloud.azure.active-directory.b2c*.credential.client-id` | -> | `*azure.activedirectory.b2c*.client-secret` | `*spring.cloud.azure.active-directory.b2c*.credential.client-secret` | -> | `*azure.activedirectory.b2c*.jwt-connect-timeout` | `*spring.cloud.azure.active-directory.b2c*.jwt-connect-timeout` | -> | `*azure.activedirectory.b2c*.jwt-read-timeout` | `*spring.cloud.azure.active-directory.b2c*.jwt-read-timeout` | -> | `*azure.activedirectory.b2c*.jwt-size-limit` | `*spring.cloud.azure.active-directory.b2c*.jwt-size-limit` | -> | `*azure.activedirectory.b2c*.login-flow` | `*spring.cloud.azure.active-directory.b2c*.login-flow` | -> | `*azure.activedirectory.b2c*.logout-success-url` | `*spring.cloud.azure.active-directory.b2c*.logout-success-url` | -> | `*azure.activedirectory.b2c*.reply-url` | `*spring.cloud.azure.active-directory.b2c*.reply-url` | -> | `*azure.activedirectory.b2c*.tenant-id` | `*spring.cloud.azure.active-directory.b2c*.profile.tenant-id` | -> | `*azure.activedirectory.b2c*.user-flows` | `*spring.cloud.azure.active-directory.b2c*.user-flows` | -> | `*azure.activedirectory.b2c*.user-name-attribute-name` | `*spring.cloud.azure.active-directory.b2c*.user-name-attribute-name` | +> | *azure.activedirectory.b2c*.authenticate-additional-parameters | *spring.cloud.azure.active-directory.b2c*.authenticate-additional-parameters | +> | *azure.activedirectory.b2c*.authorization-clients | *spring.cloud.azure.active-directory.b2c*.authorization-clients | +> | *azure.activedirectory.b2c*.authorization-clients..authorization-grant-type | *spring.cloud.azure.active-directory.b2c*.authorization-clients..authorization-grant-type | +> | *azure.activedirectory.b2c*.authorization-clients..scopes | *spring.cloud.azure.active-directory.b2c*.authorization-clients..scopes | +> | *azure.activedirectory.b2c*.app-id-uri | *spring.cloud.azure.active-directory.b2c*.app-id-uri | +> | *azure.activedirectory.b2c*.base-uri | *spring.cloud.azure.active-directory.b2c*.base-uri | +> | *azure.activedirectory.b2c*.client-id | *spring.cloud.azure.active-directory.b2c*.credential.client-id | +> | *azure.activedirectory.b2c*.client-secret | *spring.cloud.azure.active-directory.b2c*.credential.client-secret | +> | *azure.activedirectory.b2c*.jwt-connect-timeout | *spring.cloud.azure.active-directory.b2c*.jwt-connect-timeout | +> | *azure.activedirectory.b2c*.jwt-read-timeout | *spring.cloud.azure.active-directory.b2c*.jwt-read-timeout | +> | *azure.activedirectory.b2c*.jwt-size-limit | *spring.cloud.azure.active-directory.b2c*.jwt-size-limit | +> | *azure.activedirectory.b2c*.login-flow | *spring.cloud.azure.active-directory.b2c*.login-flow | +> | *azure.activedirectory.b2c*.logout-success-url | *spring.cloud.azure.active-directory.b2c*.logout-success-url | +> | *azure.activedirectory.b2c*.reply-url | *spring.cloud.azure.active-directory.b2c*.reply-url | +> | *azure.activedirectory.b2c*.tenant-id | *spring.cloud.azure.active-directory.b2c*.profile.tenant-id | +> | *azure.activedirectory.b2c*.user-flows | *spring.cloud.azure.active-directory.b2c*.user-flows | +> | *azure.activedirectory.b2c*.user-name-attribute-name | *spring.cloud.azure.active-directory.b2c*.user-name-attribute-name | * Removed properties from azure-spring-boot-starter-active-directory-b2c: @@ -494,12 +494,12 @@ The following table shows the class mappings from `azure-spring-boot-starter-cos > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |--------------------------------------|---------------------------------------------------| -> | `*azure.cosmos*.connection-mode` | `*spring.cloud.azure.cosmos*.connection-mode` | -> | `*azure.cosmos*.consistency-level` | `*spring.cloud.azure.cosmos*.consistency-level` | -> | `*azure.cosmos*.database` | `*spring.cloud.azure.cosmos*.database` | -> | `*azure.cosmos*.key` | `*spring.cloud.azure.cosmos*.key` | -> | `*azure.cosmos*.populate-query-metrics` | `*spring.cloud.azure.cosmos*.populate-query-metrics` | -> | `*azure.cosmos*.uri` | `*spring.cloud.azure.cosmos*.endpoint` | +> | *azure.cosmos*.connection-mode | *spring.cloud.azure.cosmos*.connection-mode | +> | *azure.cosmos*.consistency-level | *spring.cloud.azure.cosmos*.consistency-level | +> | *azure.cosmos*.database | *spring.cloud.azure.cosmos*.database | +> | *azure.cosmos*.key | *spring.cloud.azure.cosmos*.key | +> | *azure.cosmos*.populate-query-metrics | *spring.cloud.azure.cosmos*.populate-query-metrics | +> | *azure.cosmos*.uri | *spring.cloud.azure.cosmos*.endpoint | ### From azure-spring-boot-starter-keyvault-secrets to spring-cloud-azure-starter-keyvault-secrets @@ -523,17 +523,17 @@ The following table shows the property mappings from `azure-spring-boot-starter- > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| -> | `*azure.keyvault*.case-sensitive-keys` | `*spring.cloud.azure.keyvault.secret*.property-source[n].case-sensitive` | -> | `*azure.keyvault*.certificate-password` | `*spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-password` | -> | `*azure.keyvault*.certificate-path` | `*spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-path` | -> | `*azure.keyvault*.client-id` | `*spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-id` | -> | `*azure.keyvault*.client-key` | `*spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-secret` | -> | `*azure.keyvault*.enabled` | `*spring.cloud.azure.keyvault.secret*.property-source-enabled` and `*spring.cloud.azure.keyvault.secret*.property-source-enabled` | -> | `*azure.keyvault*.order` | No longer supported. Use the order in property-source[n] instead. | -> | `*azure.keyvault*.refresh-interval` | `*spring.cloud.azure.keyvault.secret*.property-source[n].refresh-interval` | -> | `*azure.keyvault*.secret-keys` | `*spring.cloud.azure.keyvault.secret*.property-source[n].secret-keys` | -> | `*azure.keyvault*.tenant-id` | `*spring.cloud.azure.keyvault.secret*.property-source[n].profile.tenant-id` | -> | `*azure.keyvault*.uri` | `*spring.cloud.azure.keyvault.secret*.property-source[n].endpoint` | +> | *azure.keyvault*.case-sensitive-keys | *spring.cloud.azure.keyvault.secret*.property-source[n].case-sensitive | +> | *azure.keyvault*.certificate-password | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-password | +> | *azure.keyvault*.certificate-path | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-path | +> | *azure.keyvault*.client-id | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-id | +> | *azure.keyvault*.client-key | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-secret | +> | *azure.keyvault*.enabled | *spring.cloud.azure.keyvault.secret*.property-source-enabled and *spring.cloud.azure.keyvault.secret*.property-source-enabled | +> | *azure.keyvault*.order | No longer supported. Use the order in property-source[n] instead. | +> | *azure.keyvault*.refresh-interval | *spring.cloud.azure.keyvault.secret*.property-source[n].refresh-interval | +> | *azure.keyvault*.secret-keys | *spring.cloud.azure.keyvault.secret*.property-source[n].secret-keys | +> | *azure.keyvault*.tenant-id | *spring.cloud.azure.keyvault.secret*.property-source[n].profile.tenant-id | +> | *azure.keyvault*.uri | *spring.cloud.azure.keyvault.secret*.property-source[n].endpoint | * Removed properties from spring-cloud-azure-starter-keyvault-secrets @@ -586,9 +586,9 @@ The following table shows the property mappings from `azure-spring-boot-starter- | Legacy properties | Modern properties | |-------------------------------|------------------------------------------------| -| `*azure.storage*.account-name` | `*spring.cloud.azure.storage.blob*.account-name` | -| `*azure.storage*.account-key` | `*spring.cloud.azure.storage.blob*.account-key` | -| `*azure.storage*.blob-endpoint` | `*spring.cloud.azure.storage.blob*.endpoint` | +| *azure.storage*.account-name | *spring.cloud.azure.storage.blob*.account-name | +| *azure.storage*.account-key | *spring.cloud.azure.storage.blob*.account-key | +| *azure.storage*.blob-endpoint | *spring.cloud.azure.storage.blob*.endpoint | #### API changes @@ -622,9 +622,9 @@ The following table shows the property mappings from `azure-spring-boot-starter- | Legacy properties | Modern properties | |-------------------------------|-----------------------------------------------------| -| `*azure.storage*.account-name` | `*spring.cloud.azure.storage.fileshare*.account-name` | -| `*azure.storage*.account-key` | `*spring.cloud.azure.storage.fileshare*.account-key` | -| `*azure.storage*.file-endpoint` | `*spring.cloud.azure.storage.fileshare*.endpoint` | +| *azure.storage*.account-name | *spring.cloud.azure.storage.fileshare*.account-name | +| *azure.storage*.account-key | *spring.cloud.azure.storage.fileshare*.account-key | +| *azure.storage*.file-endpoint | *spring.cloud.azure.storage.fileshare*.endpoint | #### API changes @@ -662,12 +662,12 @@ The following table shows property mappings from `azure-spring-cloud-starter-eve > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |----------------------------------------------------------|--------------------------------------------------------------------------| -> | `*spring.cloud.azure*.resource-group` | `*spring.cloud.azure.eventhubs*.resource.resource-group` | -> | `*spring.cloud.azure.eventhub*.namespace` | `*spring.cloud.azure.eventhubs*.namespace` | -> | `*spring.cloud.azure.eventhub*.connection-string` | `*spring.cloud.azure.eventhubs*.connection-string` | -> | `*spring.cloud.azure.eventhub*.checkpoint-storage-account` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name` | -> | `*spring.cloud.azure.eventhub*.checkpoint-access-key` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key` | -> | `*spring.cloud.azure.eventhub*.checkpoint-container` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name` | +> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.eventhubs*.resource.resource-group | +> | *spring.cloud.azure.eventhub*.namespace | *spring.cloud.azure.eventhubs*.namespace | +> | *spring.cloud.azure.eventhub*.connection-string | *spring.cloud.azure.eventhubs*.connection-string | +> | *spring.cloud.azure.eventhub*.checkpoint-storage-account | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name | +> | *spring.cloud.azure.eventhub*.checkpoint-access-key | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key | +> | *spring.cloud.azure.eventhub*.checkpoint-container | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name | For example, change from: @@ -894,13 +894,13 @@ The following table shows the property mappings from `azure-spring-cloud-starter > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -> | `*spring.cloud.azure*.resource-group` | `*spring.cloud.azure.servicebus*.resource.resource-group` | -> | `*spring.cloud.azure.servicebus*.transport-type` | `*spring.cloud.azure.servicebus*.client.transport-type` | -> | `*spring.cloud.azure.servicebus*.retry-options.retry-mode` | `*spring.cloud.azure.servicebus*.retry.mode` | -> | `*spring.cloud.azure.servicebus*.retry-options.max-retries` | `*spring.cloud.azure.servicebus*.retry.exponential.max-retries` or `*spring.cloud.azure.servicebus*.retry.fixed.max-retries,` should be configured depending on `*spring.cloud.azure.servicebus*.retry.mode=*fixed*` or `*exponential*` | -> | `*spring.cloud.azure.servicebus*.retry-options.delay` | `*spring.cloud.azure.servicebus*.retry.exponential.base-delay` or `*spring.cloud.azure.servicebus*.retry.fixed.delay,` should be configured depending on `*spring.cloud.azure.servicebus*.retry.mode=*fixed*` or `*exponential*` | -> | `*spring.cloud.azure.servicebus*.retry-options.max-delay` | `*spring.cloud.azure.servicebus*.retry.exponential.max-delay` | -> | `*spring.cloud.azure.servicebus*.retry-options.try-timeout` | `*spring.cloud.azure.servicebus*.retry.try-timeout` | +> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.servicebus*.resource.resource-group | +> | *spring.cloud.azure.servicebus*.transport-type | *spring.cloud.azure.servicebus*.client.transport-type | +> | *spring.cloud.azure.servicebus*.retry-options.retry-mode | *spring.cloud.azure.servicebus*.retry.mode | +> | *spring.cloud.azure.servicebus*.retry-options.max-retries | *spring.cloud.azure.servicebus*.retry.exponential.max-retries or *spring.cloud.azure.servicebus*.retry.fixed.max-retries, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | +> | *spring.cloud.azure.servicebus*.retry-options.delay | *spring.cloud.azure.servicebus*.retry.exponential.base-delay or *spring.cloud.azure.servicebus*.retry.fixed.delay, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | +> | *spring.cloud.azure.servicebus*.retry-options.max-delay | *spring.cloud.azure.servicebus*.retry.exponential.max-delay | +> | *spring.cloud.azure.servicebus*.retry-options.try-timeout | *spring.cloud.azure.servicebus*.retry.try-timeout | #### API changes @@ -1104,9 +1104,9 @@ The following table shows the property mappings from `azure-spring-cloud-starter > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |---------------------------------------------|------------------------------------------------------------| -> | `*spring.cloud.azure.storage*.account` | `*spring.cloud.azure.storage.queue*.account-name` | -> | `*spring.cloud.azure.storage*.access-key` | `*spring.cloud.azure.storage.queue*.account-key` | -> | `*spring.cloud.azure.storage*.resource-group` | `*spring.cloud.azure.storage.queue*.resource.resource-group` | +> | *spring.cloud.azure.storage*.account | *spring.cloud.azure.storage.queue*.account-name | +> | *spring.cloud.azure.storage*.access-key | *spring.cloud.azure.storage.queue*.account-key | +> | *spring.cloud.azure.storage*.resource-group | *spring.cloud.azure.storage.queue*.resource.resource-group | #### API changes @@ -1178,18 +1178,18 @@ The following table shows property mappings from `azure-spring-cloud-stream-bind > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| -> | `*spring.cloud.azure*.resource-group` | `*spring.cloud.azure.eventhubs*.resource.resource-group` | -> | `*spring.cloud.azure.eventhub*.namespace` | `*spring.cloud.azure.eventhubs*.namespace` | -> | `*spring.cloud.azure.eventhub*.connection-string` | `*spring.cloud.azure.eventhubs*.connection-string` | -> | `*spring.cloud.azure.eventhub*.checkpoint-storage-account` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name` | -> | `*spring.cloud.azure.eventhub*.checkpoint-access-key` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key` | -> | `*spring.cloud.azure.eventhub*.checkpoint-container` | `*spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name` | -> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-batch-size` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-size` | -> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-wait-time` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-wait-time` | -> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-mode` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.mode` | -> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-count` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.count` | -> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-interval` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.interval` | -> | `*spring.cloud.stream.eventhub.bindings.binding-name.consumer*.start-position` | `*spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.initial-partition-event-position` | +> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.eventhubs*.resource.resource-group | +> | *spring.cloud.azure.eventhub*.namespace | *spring.cloud.azure.eventhubs*.namespace | +> | *spring.cloud.azure.eventhub*.connection-string | *spring.cloud.azure.eventhubs*.connection-string | +> | *spring.cloud.azure.eventhub*.checkpoint-storage-account | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name | +> | *spring.cloud.azure.eventhub*.checkpoint-access-key | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key | +> | *spring.cloud.azure.eventhub*.checkpoint-container | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-batch-size | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-size | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-wait-time | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-wait-time | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-mode | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.mode | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-count | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.count | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-interval | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.interval | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.start-position | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.initial-partition-event-position | > [!NOTE] > The value type of the `start-position` configuration is also changed from an enum of `com.azure.spring.integration.core.api.StartPosition` to a `map` of `StartPositionProperties` for each partition. Thus, the key is the partition ID, and the value is of `com.azure.spring.cloud.service.eventhubs.properties.StartPositionProperties` which includes properties of offset, sequence number, enqueued date time and whether inclusive. @@ -1372,26 +1372,26 @@ The following table lists the new configuration properties of `spring-cloud-azur > [!div class="mx-tdBreakAll"] > | Modern properties | Description | > |-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| -> | `*spring.cloud.stream.servicebus*.bindings.binding-name.producer.entity-type` | If you use the sending function, you need to set the entity-type, which you can set to topic or queue. | +> | *spring.cloud.stream.servicebus*.bindings.binding-name.producer.entity-type | If you use the sending function, you need to set the entity-type, which you can set to topic or queue. | The following table shows the property mappings from `azure-spring-cloud-stream-binder-servicebus-*` to `spring-cloud-azure-stream-binder-servicebus`: > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -> | `*spring.cloud.azure*.resource-group` | `*spring.cloud.azure.servicebus*.resource.resource-group` | -> | `*spring.cloud.azure.servicebus*.transport-type` | `*spring.cloud.azure.servicebus*.client.transport-type` | -> | `*spring.cloud.azure.servicebus*.retry-options.retry-mode` | `*spring.cloud.azure.servicebus*.retry.mode` | -> | `*spring.cloud.azure.servicebus*.retry-options.max-retries` | `*spring.cloud.azure.servicebus*.retry.exponential.max-retries` or `*spring.cloud.azure.servicebus*.retry.fixed.max-retries,` should be configured depending on `*spring.cloud.azure.servicebus*.retry.mode=*fixed*` or `*exponential*` | -> | `*spring.cloud.azure.servicebus*.retry-options.delay` | `*spring.cloud.azure.servicebus*.retry.exponential.base-delay` or `*spring.cloud.azure.servicebus*.retry.fixed.delay,` should be configured depending on `*spring.cloud.azure.servicebus*.retry.mode=*fixed*` or `*exponential*` | -> | `*spring.cloud.azure.servicebus*.retry-options.max-delay` | `*spring.cloud.azure.servicebus*.retry.exponential.max-delay` | -> | `*spring.cloud.azure.servicebus*.retry-options.try-timeout` | `*spring.cloud.azure.servicebus*.retry.try-timeout` | -> | `*spring.cloud.stream.servicebus*.queue.bindings.*` | `*spring.cloud.stream.servicebus.bindings*.*` | -> | `*spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*concurrency*` | `*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls` | -> | `*spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*checkpoint-mode*` | `*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete*` | -> | `*spring.cloud.stream.servicebus*.topic.bindings.*` | `*spring.cloud.stream.servicebus.bindings*.*` | -> | `*spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*concurrency*` | `*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls` | -> | `*spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*checkpoint-mode*` | `*spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete*` | +> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.servicebus*.resource.resource-group | +> | *spring.cloud.azure.servicebus*.transport-type | *spring.cloud.azure.servicebus*.client.transport-type | +> | *spring.cloud.azure.servicebus*.retry-options.retry-mode | *spring.cloud.azure.servicebus*.retry.mode | +> | *spring.cloud.azure.servicebus*.retry-options.max-retries | *spring.cloud.azure.servicebus*.retry.exponential.max-retries or *spring.cloud.azure.servicebus*.retry.fixed.max-retries, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | +> | *spring.cloud.azure.servicebus*.retry-options.delay | *spring.cloud.azure.servicebus*.retry.exponential.base-delay or *spring.cloud.azure.servicebus*.retry.fixed.delay, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | +> | *spring.cloud.azure.servicebus*.retry-options.max-delay | *spring.cloud.azure.servicebus*.retry.exponential.max-delay | +> | *spring.cloud.azure.servicebus*.retry-options.try-timeout | *spring.cloud.azure.servicebus*.retry.try-timeout | +> | *spring.cloud.stream.servicebus*.queue.bindings.* | *spring.cloud.stream.servicebus.bindings*.* | +> | *spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*concurrency* | *spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls | +> | *spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*checkpoint-mode* | *spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete* | +> | *spring.cloud.stream.servicebus*.topic.bindings.* | *spring.cloud.stream.servicebus.bindings*.* | +> | *spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*concurrency* | *spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls | +> | *spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*checkpoint-mode* | *spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete* | > [!NOTE] > The concurrency property will be replaced by the maxConcurrentSessions when sessionsEnabled is `true` and the maxConcurrentCalls when sessionsEnabled is `false`. diff --git a/articles/java/spring-framework/production-ready.md b/articles/java/spring-framework/production-ready.md index e26bbf24f..a06a49ed2 100644 --- a/articles/java/spring-framework/production-ready.md +++ b/articles/java/spring-framework/production-ready.md @@ -27,16 +27,16 @@ To enable the health indicators, add the Spring Cloud Azure Actuator Starter dep The following table lists configurable properties to enable or disable health indicators for each Azure service: -| Azure Service | Property | -|-----------------------|--------------------------------------------------------| -| App Configuration | `**management.health.azure**-appconfiguration.enabled` | -| Azure Cosmos DB | `**management.health.azure**-cosmos.enabled` | -| Event Hubs | `**management.health.azure**-eventhubs.enabled` | -| Key Vault Certificate | `**management.health.azure**-keyvault-certificate.enabled` | -| Key Vault Secret | `**management.health.azure**-keyvault-secret.enabled` | -| Storage Blob | `**management.health.azure**-storage-blob.enabled` | -| Storage File Share | `**management.health.azure**-storage-fileshare.enabled` | -| Storage Queue | `**management.health.azure**-storage-queue.enabled` | +| Azure Service | Property | +|-----------------------|---------------------------------------------------------| +| App Configuration | *management.health.azure**-appconfiguration.enabled | +| Azure Cosmos DB | *management.health.azure**-cosmos.enabled | +| Event Hubs | *management.health.azure**-eventhubs.enabled | +| Key Vault Certificate | *management.health.azure**-keyvault-certificate.enabled | +| Key Vault Secret | *management.health.azure**-keyvault-secret.enabled | +| Storage Blob | *management.health.azure**-storage-blob.enabled | +| Storage File Share | *management.health.azure**-storage-fileshare.enabled | +| Storage Queue | *management.health.azure**-storage-queue.enabled | > [!IMPORTANT] > Calling the health endpoint of Azure services may cause extra charges. For example, if you call `http://HOST_NAME:{port}/actuator/health/cosmos` to get Azure Cosmos DB health info, it will calculate Request Units (RUs). For more information, see [Request Units in Azure Cosmos DB](/azure/cosmos-db/request-units). From 31989122f83450ad575d3998383c3ede8ff0fb13 Mon Sep 17 00:00:00 2001 From: JoshTheTechWriter <183134486+JoshTheTechWriter@users.noreply.github.com> Date: Mon, 20 Jan 2025 14:08:23 -0500 Subject: [PATCH 15/21] Removed unnecessary asterisks from production-ready.md. --- .../java/spring-framework/production-ready.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/articles/java/spring-framework/production-ready.md b/articles/java/spring-framework/production-ready.md index a06a49ed2..d5ba7b5d7 100644 --- a/articles/java/spring-framework/production-ready.md +++ b/articles/java/spring-framework/production-ready.md @@ -29,14 +29,14 @@ The following table lists configurable properties to enable or disable health in | Azure Service | Property | |-----------------------|---------------------------------------------------------| -| App Configuration | *management.health.azure**-appconfiguration.enabled | -| Azure Cosmos DB | *management.health.azure**-cosmos.enabled | -| Event Hubs | *management.health.azure**-eventhubs.enabled | -| Key Vault Certificate | *management.health.azure**-keyvault-certificate.enabled | -| Key Vault Secret | *management.health.azure**-keyvault-secret.enabled | -| Storage Blob | *management.health.azure**-storage-blob.enabled | -| Storage File Share | *management.health.azure**-storage-fileshare.enabled | -| Storage Queue | *management.health.azure**-storage-queue.enabled | +| App Configuration | *management.health.azure*-appconfiguration.enabled | +| Azure Cosmos DB | *management.health.azure*-cosmos.enabled | +| Event Hubs | *management.health.azure*-eventhubs.enabled | +| Key Vault Certificate | *management.health.azure*-keyvault-certificate.enabled | +| Key Vault Secret | *management.health.azure*-keyvault-secret.enabled | +| Storage Blob | *management.health.azure*-storage-blob.enabled | +| Storage File Share | *management.health.azure*-storage-fileshare.enabled | +| Storage Queue | *management.health.azure*-storage-queue.enabled | > [!IMPORTANT] > Calling the health endpoint of Azure services may cause extra charges. For example, if you call `http://HOST_NAME:{port}/actuator/health/cosmos` to get Azure Cosmos DB health info, it will calculate Request Units (RUs). For more information, see [Request Units in Azure Cosmos DB](/azure/cosmos-db/request-units). From ba88803884bae835c5691e23448399f9359af569 Mon Sep 17 00:00:00 2001 From: JoshTheTechWriter <183134486+JoshTheTechWriter@users.noreply.github.com> Date: Mon, 20 Jan 2025 14:10:06 -0500 Subject: [PATCH 16/21] Corrected minor table spacing issue in production-ready.md. --- articles/java/spring-framework/production-ready.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/java/spring-framework/production-ready.md b/articles/java/spring-framework/production-ready.md index d5ba7b5d7..4eeca6818 100644 --- a/articles/java/spring-framework/production-ready.md +++ b/articles/java/spring-framework/production-ready.md @@ -27,8 +27,8 @@ To enable the health indicators, add the Spring Cloud Azure Actuator Starter dep The following table lists configurable properties to enable or disable health indicators for each Azure service: -| Azure Service | Property | -|-----------------------|---------------------------------------------------------| +| Azure Service | Property | +|-----------------------|--------------------------------------------------------| | App Configuration | *management.health.azure*-appconfiguration.enabled | | Azure Cosmos DB | *management.health.azure*-cosmos.enabled | | Event Hubs | *management.health.azure*-eventhubs.enabled | From fa8d80967df4c2f76a55b716b440ecec5ac14eec Mon Sep 17 00:00:00 2001 From: JoshTheTechWriter <183134486+JoshTheTechWriter@users.noreply.github.com> Date: Wed, 15 Jan 2025 12:43:06 -0500 Subject: [PATCH 17/21] Ninth bundle of files. --- .../spring-framework/resource-handling.md | 20 ++++----- .../spring-framework/secret-management.md | 28 ++++++------- ...ur-restful-api-using-spring-cloud-azure.md | 4 +- ...-boot-starter-for-entra-developer-guide.md | 42 +++++++++---------- .../spring-cloud-azure-overview.md | 10 ++--- .../spring-cloud-stream-support.md | 16 +++---- .../spring-framework/spring-data-support.md | 28 ++++++------- .../spring-integration-support.md | 22 +++++----- .../spring-framework/spring-jms-support.md | 6 +-- .../spring-messaging-support.md | 30 ++++++------- .../spring-security-support.md | 24 +++++------ .../testcontainers-support.md | 2 +- ...using-event-hubs-in-spring-applications.md | 26 ++++++------ ...sing-service-bus-in-spring-applications.md | 34 +++++++-------- ...ng-storage-queue-in-spring-applications.md | 22 +++++----- .../create-hello-world-web-app.md | 6 +-- .../java/toolkit-for-eclipse/installation.md | 2 +- ...aging-redis-caches-using-azure-explorer.md | 4 +- ...g-virtual-machines-using-azure-explorer.md | 8 ++-- .../toolkit-for-intellij/chatgpt-intellij.md | 2 +- 20 files changed, 168 insertions(+), 168 deletions(-) diff --git a/articles/java/spring-framework/resource-handling.md b/articles/java/spring-framework/resource-handling.md index e9fea8c32..18034ce63 100644 --- a/articles/java/spring-framework/resource-handling.md +++ b/articles/java/spring-framework/resource-handling.md @@ -41,7 +41,7 @@ The `spring-cloud-azure-starter-storage-blob` dependency is only required when y The `spring-cloud-azure-starter-storage-file-share` dependency is only required when you're using Azure Storage File Share. > [!TIP] -> We also provide `spring-cloud-azure-starter-storage` to support all the features of Storage. If you choose to use it, `spring.cloud.azure.storage.enable` is the property to configure and the default value is *true*. You can then use `spring.cloud.azure.storage..enable` to disable unneeded services. +> We also provide `spring-cloud-azure-starter-storage` to support all the features of Storage. If you choose to use it, `spring.cloud.azure.storage.enable` is the property to configure and the default value is `true`. You can then use `spring.cloud.azure.storage..enable` to disable unneeded services. ## Configuration @@ -53,24 +53,24 @@ The following table lists the configurable properties of `spring-cloud-azure-sta > [!div class="mx-tdBreakAll"] > | Property | Default | Description | > |------------------------------------------------|---------|--------------------------------------------------------------------------| -> | *spring.cloud.azure.storage.blob*.enabled | true | A value that indicates whether an Azure Blob Storage service is enabled. | -> | *spring.cloud.azure.storage.blob*.endpoint | | The URI to connect to Azure Blob Storage. | -> | *spring.cloud.azure.storage.blob*.account-key | | The private key to connect to Azure Blob Storage. | -> | *spring.cloud.azure.storage.blob*.account-name | | The Azure Storage Blob account name. +> | `*spring.cloud.azure.storage.blob*.enabled` | true | A value that indicates whether an Azure Blob Storage service is enabled. | +> | `*spring.cloud.azure.storage.blob*.endpoint` | | The URI to connect to Azure Blob Storage. | +> | `*spring.cloud.azure.storage.blob*.account-key` | | The private key to connect to Azure Blob Storage. | +> | `*spring.cloud.azure.storage.blob*.account-name` | | The Azure Storage Blob account name. The following table lists the configurable properties of `spring-cloud-azure-starter-storage-file-share`: > [!div class="mx-tdBreakAll"] > | Property | Default | Description | > |-----------------------------------------------------|---------|-----------------------------------------------------------------------| -> | *spring.cloud.azure.storage.fileshare*.enabled | true | A value that indicates whether Azure File Storage service is enabled. | -> | *spring.cloud.azure.storage.fileshare*.endpoint | | The URI to connect to Azure File Storage. | -> | *spring.cloud.azure.storage.fileshare*.account-key | | The private key to connect to Azure File Storage. | -> | *spring.cloud.azure.storage.fileshare*.account-name | | The Azure Storage File Share account name. | +> | `*spring.cloud.azure.storage.fileshare*.enabled` | true | A value that indicates whether Azure File Storage service is enabled. | +> | `*spring.cloud.azure.storage.fileshare*.endpoint` | | The URI to connect to Azure File Storage. | +> | `*spring.cloud.azure.storage.fileshare*.account-key` | | The private key to connect to Azure File Storage. | +> | `*spring.cloud.azure.storage.fileshare*.account-name` | | The Azure Storage File Share account name. | ## Basic usage -Add the following properties to your *application.yml* file: +Add the following properties to your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/secret-management.md b/articles/java/spring-framework/secret-management.md index 833c402dd..8e8114595 100644 --- a/articles/java/spring-framework/secret-management.md +++ b/articles/java/spring-framework/secret-management.md @@ -24,7 +24,7 @@ Spring Cloud Azure construct `PropertySource` which holds secrets stored in Azur ``` > [!TIP] -> We also provide `spring-cloud-azure-starter-keyvault` to support all the features of Key Vault. If you choose to use it, `spring.cloud.azure.keyvault.enable` is the property to configure and the default value is *true*. You can then use `spring.cloud.azure.keyvault..enable` to disable unneeded services. +> We also provide `spring-cloud-azure-starter-keyvault` to support all the features of Key Vault. If you choose to use it, `spring.cloud.azure.keyvault.enable` is the property to configure and the default value is `true`. You can then use `spring.cloud.azure.keyvault..enable` to disable unneeded services. ## Basic usage @@ -85,7 +85,7 @@ Key Vault secret names support only characters in `[0-9a-zA-Z-]`. For more infor #### Use property placeholders -For example, suppose you're setting this property in your *application.properties* file: +For example, suppose you're setting this property in your **application.properties** file: ```properties property.with.special.character__=${propertyWithoutSpecialCharacter} @@ -136,18 +136,18 @@ public static void main(String[] args) { > [!div class="mx-tdBreakAll"] > | Property | Default value | Description | > |--------------------------------------------------------------------------|---------------|--------------------------------------------------------------------------------------------------------| -> | *spring.cloud.azure.keyvault.secret*.property-source-enabled | true | Whether to enable the Key Vault property source. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].name | | Name of this property source. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].endpoint | | Azure Key Vault endpoint. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].case-sensitive | false | Whether the secret keys are case-sensitive. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].secret-keys | | The secret keys supported for this property source. All keys be retrieved if this property is missing. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].refresh-interval | 30m | Time interval to refresh all Key Vault secrets. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].service-version | | Secret service version used when making API requests. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].client | | Client related properties. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].credential | | Credential related properties. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].profile | | Profile related properties. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].proxy | | Proxy related properties. | -> | *spring.cloud.azure.keyvault.secret*.property-sources[].retry | | Retry related properties. | +> | `*spring.cloud.azure.keyvault.secret*.property-source-enabled` | true | Whether to enable the Key Vault property source. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].name` | | Name of this property source. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].endpoint` | | Azure Key Vault endpoint. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].case-sensitive` | false | Whether the secret keys are case-sensitive. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].secret-keys` | | The secret keys supported for this property source. All keys be retrieved if this property is missing. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].refresh-interval` | 30m | Time interval to refresh all Key Vault secrets. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].service-version` | | Secret service version used when making API requests. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].client` | | Client related properties. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].credential` | | Credential related properties. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].profile` | | Profile related properties. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].proxy` | | Proxy related properties. | +> | `*spring.cloud.azure.keyvault.secret*.property-sources[].retry` | | Retry related properties. | * See [Authorize access with Microsoft Entra ID](authentication.md#authorize-access-with-azure-active-directory) to make sure the [security principal](/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object) has been granted the sufficient permission to access the Azure Key Vault Secrets. * If common properties like `client`, `credential`, `profile`, `proxy`, `retry` aren't configured in `spring.cloud.azure.keyvault.secret.property-sources[].xxx`, `spring.cloud.azure.xxx` will be used. See [Spring Cloud Azure configuration](configuration-properties-global.md) to get more information about these common properties. diff --git a/articles/java/spring-framework/secure-your-restful-api-using-spring-cloud-azure.md b/articles/java/spring-framework/secure-your-restful-api-using-spring-cloud-azure.md index 12390ae9b..9639833c4 100644 --- a/articles/java/spring-framework/secure-your-restful-api-using-spring-cloud-azure.md +++ b/articles/java/spring-framework/secure-your-restful-api-using-spring-cloud-azure.md @@ -86,7 +86,7 @@ Next, enable the REST API protection with Spring Cloud Azure. ### Add Security dependencies -To install the Spring Cloud Azure Starter Azure Active Directory module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Starter Azure Active Directory module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -106,7 +106,7 @@ To install the Spring Cloud Azure Starter Azure Active Directory module, add the > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Starter Microsoft Entra artifact: diff --git a/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md b/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md index 476f242b3..a277db36e 100644 --- a/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md +++ b/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md @@ -54,11 +54,11 @@ This scenario uses the [The OAuth 2.0 authorization code grant](/azure/active-di To use the Microsoft Entra starter in this scenario, use the following steps: -Set the redirect URI to *\/login/oauth2/code/*. For example: `http://localhost:8080/login/oauth2/code/`. Be sure to include the trailing `/`. For more information about the redirect URI, see [Add a redirect URI](/azure/active-directory/develop/quickstart-register-app#add-a-redirect-uri) in [Quickstart: Register an application with the Microsoft identity platform](/azure/active-directory/develop/quickstart-register-app). +Set the redirect URI to `application-base-uri>/login/oauth2/code/`. For example: `http://localhost:8080/login/oauth2/code/`. Be sure to include the trailing `/`. For more information about the redirect URI, see [Add a redirect URI](/azure/active-directory/develop/quickstart-register-app#add-a-redirect-uri) in [Quickstart: Register an application with the Microsoft identity platform](/azure/active-directory/develop/quickstart-register-app). :::image type="content" source="media/spring-boot-starter-for-entra-developer-guide/web-application-set-redirect-uri-2.png" alt-text="Screenshot of Azure portal showing web app authentication page with redirect URI highlighted."::: -Add the following dependencies to your *pom.xml* file. +Add the following dependencies to your **pom.xml** file. ```xml @@ -74,7 +74,7 @@ Add the following dependencies to your *pom.xml* file. > [!NOTE] > For more information about how to manage Spring Cloud Azure library versions by using a bill of materials (BOM), see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -Add the following properties to your *application.yml* file. You can get the values for these properties from the app registration you created in the Azure portal, as described in the prerequisites. +Add the following properties to your **application.yml** file. You can get the values for these properties from the app registration you created in the Azure portal, as described in the prerequisites. ```yaml spring: @@ -161,7 +161,7 @@ To use the Microsoft Entra starter in this scenario, use the following steps: Set the redirect URI as described previously. -Add the following dependencies to your *pom.xml* file. +Add the following dependencies to your **pom.xml** file. ```xml @@ -177,7 +177,7 @@ Add the following dependencies to your *pom.xml* file. > [!NOTE] > For more information about how to manage Spring Cloud Azure library versions by using a bill of materials (BOM), see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -Add the following properties to your *application.yml* file, as described previously: +Add the following properties to your **application.yml** file, as described previously: ```yaml spring: @@ -224,7 +224,7 @@ This scenario doesn't support sign in, but protects the server by validating the To use the Microsoft Entra starter in this scenario, use the following steps: -Add the following dependencies to your *pom.xml* file. +Add the following dependencies to your **pom.xml** file. ```xml @@ -240,7 +240,7 @@ Add the following dependencies to your *pom.xml* file. > [!NOTE] > For more information about how to manage Spring Cloud Azure library versions by using a bill of materials (BOM), see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -Add the following properties to your *application.yml* file, as described previously: +Add the following properties to your **application.yml** file, as described previously: ```yaml spring: @@ -253,7 +253,7 @@ spring: app-id-uri: ``` -You can use both the *\* and *\* values to verify the access token. You can get the *\* value from the Azure portal, as shown in the following images: +You can use both the `` and `` values to verify the access token. You can get the `` value from the Azure portal, as shown in the following images: :::image type="content" source="media/spring-boot-starter-for-entra-developer-guide/get-app-id-uri-2.png" alt-text="Screenshot of Azure portal showing web app Expose an API page with Application ID URI highlighted."::: @@ -325,7 +325,7 @@ This scenario supports a resource server visiting other resource servers. To use the Microsoft Entra starter in this scenario, use the following steps: -Add the following dependencies to your *pom.xml* file. +Add the following dependencies to your **pom.xml** file. ```xml @@ -345,7 +345,7 @@ Add the following dependencies to your *pom.xml* file. > [!NOTE] > For more information about how to manage Spring Cloud Azure library versions by using a bill of materials (BOM), see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -Add the following properties to your *application.yml* file: +Add the following properties to your **application.yml** file: ```yaml spring: @@ -386,7 +386,7 @@ This scenario supports [Access a web application](#access-a-web-application) and To use `aad-starter` in this scenario, follow these steps: -Add the following dependencies to your *pom.xml* file. +Add the following dependencies to your **pom.xml** file. ```xml @@ -406,7 +406,7 @@ Add the following dependencies to your *pom.xml* file. > [!NOTE] > For more information about how to manage Spring Cloud Azure library versions by using a bill of materials (BOM), see the [Getting started](developer-guide-overview.md#getting-started) section of the [Spring Cloud Azure developer guide](developer-guide-overview.md). -Update your *application.yml* file. Set property `spring.cloud.azure.active-directory.application-type` to `web_application_and_resource_server`, and specify the authorization type for each authorization client, as shown in the following example. +Update your **application.yml** file. Set property `spring.cloud.azure.active-directory.application-type` to `web_application_and_resource_server`, and specify the authorization type for each authorization client, as shown in the following example. ```yaml spring: @@ -524,15 +524,15 @@ The Spring Boot Starter for Microsoft Entra ID provides the following properties | Properties | Description | |----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| spring.cloud.azure.active-directory.app-id-uri | Used by the resource server to validate the audience in the access token. The access token is valid only when the audience is equal to the *\* or *\* values described previously. | +| spring.cloud.azure.active-directory.app-id-uri | Used by the resource server to validate the audience in the access token. The access token is valid only when the audience is equal to the `` or `` values described previously. | | spring.cloud.azure.active-directory.authorization-clients | A map that configures the resource APIs the application is going to visit. Each item corresponds to one resource API the application is going to visit. In your Spring code, each item corresponds to one `OAuth2AuthorizedClient` object. | -| spring.cloud.azure.active-directory.authorization-clients.*\*.scopes | The API permissions of a resource server that the application is going to acquire. | -| spring.cloud.azure.active-directory.authorization-clients.*\*.authorization-grant-type | The type of authorization client. Supported types are [authorization_code](/azure/active-directory/develop/v2-oauth2-auth-code-flow) (default type for webapp), [on_behalf_of](/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow) (default type for resource-server), [client_credentials](/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow). | +| `spring.cloud.azure.active-directory.authorization-clients..scopes` | The API permissions of a resource server that the application is going to acquire. | +| `spring.cloud.azure.active-directory.authorization-clients..authorization-grant-type` | The type of authorization client. Supported types are [authorization_code](/azure/active-directory/develop/v2-oauth2-auth-code-flow) (default type for webapp), [on_behalf_of](/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow) (default type for resource-server), [client_credentials](/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow). | | spring.cloud.azure.active-directory.application-type | Refer to [Application type](#application-type). | | spring.cloud.azure.active-directory.profile.environment.active-directory-endpoint | The base URI for the authorization server. The default value is `https://login.microsoftonline.com/`. | | spring.cloud.azure.active-directory.credential.client-id | The registered application ID in Microsoft Entra ID. | | spring.cloud.azure.active-directory.credential.client-secret | The client secret of the registered application. | -| spring.cloud.azure.active-directory.user-group.use-transitive-members | Use `v1.0/me/transitiveMemberOf` to get groups if set to *true*. Otherwise, use `/v1.0/me/memberOf`. | +| spring.cloud.azure.active-directory.user-group.use-transitive-members | Use `v1.0/me/transitiveMemberOf` to get groups if set to `true`. Otherwise, use `/v1.0/me/memberOf`. | | spring.cloud.azure.active-directory.post-logout-redirect-uri | The redirect URI for posting the sign-out. | | spring.cloud.azure.active-directory.profile.tenant-id | The Azure tenant ID. The values allowed for `tenant-id` are: `common`, `organizations`, `consumers`, or the tenant ID. | | spring.cloud.azure.active-directory.user-group.allowed-group-names | The expected user groups that an authority will be granted to if found in the response from the `MemberOf` Graph API call. | @@ -542,7 +542,7 @@ The following examples show you how to use these properties: **Property example 1:** To use [Azure China 21Vianet](/azure/china/resources-developer-guide#check-endpoints-in-azure) instead of Azure Global, use the following step. -- Add the following properties to your *application.yml* file: +- Add the following properties to your **application.yml** file: ```yaml spring: @@ -559,7 +559,7 @@ With this method, you can use an [Azure sovereign or national cloud](/azure/acti **Property example 2:** To use a group name to protect some method in a web application, use the following steps: -Add the following property to your *application.yml* file: +Add the following property to your **application.yml** file: ```yaml spring: @@ -665,7 +665,7 @@ public class RoleController { **Property example 3:** To enable client credential flow in a resource server visiting resource servers, use the following steps: -Add the following property to your *application.yml* file: +Add the following property to your **application.yml** file: ```yaml spring: @@ -758,9 +758,9 @@ The Azure SDKs for Java offer a consistent logging story to help troubleshoot an ### Enable Spring logging -Spring enables all the supported logging systems to set logger levels in the Spring environment (for example, in *application.properties*) by using `logging.level.=` where level is one of TRACE, DEBUG, INFO, WARN, ERROR, FATAL, or OFF. You can configure the root logger by using `logging.level.root`. +Spring enables all the supported logging systems to set logger levels in the Spring environment (for example, in **application.properties**) by using `logging.level.=` where level is one of TRACE, DEBUG, INFO, WARN, ERROR, FATAL, or OFF. You can configure the root logger by using `logging.level.root`. -The following example shows potential logging settings in the *application.properties* file: +The following example shows potential logging settings in the **application.properties** file: ```properties logging.level.root=WARN diff --git a/articles/java/spring-framework/spring-cloud-azure-overview.md b/articles/java/spring-framework/spring-cloud-azure-overview.md index a6815ec97..bfd433a63 100644 --- a/articles/java/spring-framework/spring-cloud-azure-overview.md +++ b/articles/java/spring-framework/spring-cloud-azure-overview.md @@ -40,7 +40,7 @@ The following section demonstrates the benefits of using Spring Cloud Azure. In Without Spring Cloud Azure, if you want to retrieve secrets stored in Azure Key Vault, you need to the following steps: -1. Add the following dependencies to your *pom.xml* file: +1. Add the following dependencies to your **pom.xml** file: ```xml @@ -149,7 +149,7 @@ Without Spring Cloud Azure, if you want to retrieve secrets stored in Azure Key } ``` -1. Add the necessary properties to your *application.yml* file, as shown in the following example: +1. Add the necessary properties to your **application.yml** file, as shown in the following example: ```yaml azure: @@ -166,7 +166,7 @@ Without Spring Cloud Azure, if you want to retrieve secrets stored in Azure Key With Spring Cloud Azure, if you want to retrieve secrets stored in Azure Key Vault, the requirements are simpler, as shown in the following steps: -1. Add the following dependencies to your *pom.xml* file: +1. Add the following dependencies to your **pom.xml** file: ```xml @@ -195,10 +195,10 @@ With Spring Cloud Azure, if you want to retrieve secrets stored in Azure Key Vau > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). -1. Add the following properties to your *application.yml* file: +1. Add the following properties to your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/spring-cloud-stream-support.md b/articles/java/spring-framework/spring-cloud-stream-support.md index e776c27ef..7c7ebcfb6 100644 --- a/articles/java/spring-framework/spring-cloud-stream-support.md +++ b/articles/java/spring-framework/spring-cloud-stream-support.md @@ -197,7 +197,7 @@ The above [connection](#connection-configuration-properties) and [common Azure S 1. Fill the configuration options with credential information. - * For credentials as connection string, configure the following properties in your *application.yml* file: + * For credentials as connection string, configure the following properties in your **application.yml** file: ```yaml spring: @@ -227,7 +227,7 @@ The above [connection](#connection-configuration-properties) and [common Azure S mode: MANUAL ``` - * For credentials as service principal, configure the following properties in your *application.yml* file: + * For credentials as service principal, configure the following properties in your **application.yml** file: ```yaml spring: @@ -264,7 +264,7 @@ The above [connection](#connection-configuration-properties) and [common Azure S > [!NOTE] > The values allowed for `tenant-id` are: `common`, `organizations`, `consumers`, or the tenant ID. For more information about these values, see the [Used the wrong endpoint (personal and organization accounts)](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist#cause-3-used-the-wrong-endpoint-personal-and-organization-accounts) section of [Error AADSTS50020 - User account from identity provider does not exist in tenant](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist). For information on converting your single-tenant app, see [Convert single-tenant app to multitenant on Microsoft Entra ID](/entra/identity-platform/howto-convert-app-to-be-multi-tenant). - * For credentials as managed identities, configure the following properties in your *application.yml* file: + * For credentials as managed identities, configure the following properties in your **application.yml** file: ```yaml spring: @@ -572,7 +572,7 @@ For the basic message headers supported, see the [Event Hubs message headers](sp Connection to multiple Event Hubs namespaces is also supported by using multiple binders. This sample takes a connection string as example. Credentials of service principals and managed identities are also supported. You can set related properties in each binder's environment settings. -1. To use multiple binders with Event Hubs, configure the following properties in your *application.yml* file: +1. To use multiple binders with Event Hubs, configure the following properties in your **application.yml** file: ```yaml spring: @@ -837,7 +837,7 @@ The above [connection](#connection-configuration-properties-1) and [common Azure 1. Fill the configuration options with credential information. - * For credentials as connection string, configure the following properties in your *application.yml* file: + * For credentials as connection string, configure the following properties in your **application.yml** file: ```yaml spring: @@ -865,7 +865,7 @@ The above [connection](#connection-configuration-properties-1) and [common Azure entity-type: queue # set as "topic" if you use Service Bus Topic ``` - * For credentials as service principal, configure the following properties in your *application.yml* file: + * For credentials as service principal, configure the following properties in your **application.yml** file: ```yaml spring: @@ -901,7 +901,7 @@ The above [connection](#connection-configuration-properties-1) and [common Azure > [!NOTE] > The values allowed for `tenant-id` are: `common`, `organizations`, `consumers`, or the tenant ID. For more information about these values, see the [Used the wrong endpoint (personal and organization accounts)](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist#cause-3-used-the-wrong-endpoint-personal-and-organization-accounts) section of [Error AADSTS50020 - User account from identity provider does not exist in tenant](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist). For information on converting your single-tenant app, see [Convert single-tenant app to multitenant on Microsoft Entra ID](/entra/identity-platform/howto-convert-app-to-be-multi-tenant). - * For credentials as managed identities, configure the following properties in your *application.yml* file: + * For credentials as managed identities, configure the following properties in your **application.yml** file: ```yaml spring: @@ -1153,7 +1153,7 @@ For the basic message headers supported, see the [Service Bus message headers](s Connection to multiple Service Bus namespaces is also supported by using multiple binders. This sample takes connection string as example. Credentials of service principals and managed identities are also supported, users can set related properties in each binder's environment settings. -1. To use multiple binders of ServiceBus, configure the following properties in your *application.yml* file: +1. To use multiple binders of ServiceBus, configure the following properties in your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/spring-data-support.md b/articles/java/spring-framework/spring-data-support.md index 72a3e4a34..aae433ede 100644 --- a/articles/java/spring-framework/spring-data-support.md +++ b/articles/java/spring-framework/spring-data-support.md @@ -37,19 +37,19 @@ The following table lists the configurable properties of `spring-cloud-azure-sta > [!div class="mx-tdBreakAll"] > | Property | Description | > |--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| -> | *spring.cloud.azure.cosmos*.enabled | A value that indicates whether Azure Cosmos DB Service is enabled. The default value is *true*. | -> | *spring.cloud.azure.cosmos*.database | The Azure Cosmos DB database ID. | -> | *spring.cloud.azure.cosmos*.endpoint | The URI to connect Azure Cosmos DB. | -> | *spring.cloud.azure.cosmos*.key | The PrivateKey to connect Azure Cosmos DB. | -> | *spring.cloud.azure.cosmos*.credential.client-certificate-password | The password of the certificate file. | -> | *spring.cloud.azure.cosmos*.credential.client-certificate-path | The path of a PEM certificate file to use when performing service principal authentication with Azure. | -> | *spring.cloud.azure.cosmos*.credential.client-id | The client ID to use when performing service principal authentication with Azure. | -> | *spring.cloud.azure.cosmos*.credential.client-secret | The client secret to use when performing service principal authentication with Azure. | -> | *spring.cloud.azure.cosmos*.credential.managed-identity-enabled | Whether to enable managed identity. The default value is *false*. | -> | *spring.cloud.azure.cosmos*.credential.password | The password to use when performing username/password authentication with Azure. | -> | *spring.cloud.azure.cosmos*.credential.username | The username to use when performing username/password authentication with Azure. | -> | *spring.cloud.azure.cosmos*.populate-query-metrics | A value that indicates whether to populate diagnostics strings and query metrics. The default value is *false*. | -> | *spring.cloud.azure.cosmos*.consistency-level | A [consistency level](/azure/cosmos-db/consistency-levels) for Azure Cosmos DB. | +> | `*spring.cloud.azure.cosmos*.enabled` | A value that indicates whether Azure Cosmos DB Service is enabled. The default value is `true`. | +> | `*spring.cloud.azure.cosmos*.database` | The Azure Cosmos DB database ID. | +> | `*spring.cloud.azure.cosmos*.endpoint` | The URI to connect Azure Cosmos DB. | +> | `*spring.cloud.azure.cosmos*.key` | The PrivateKey to connect Azure Cosmos DB. | +> | `*spring.cloud.azure.cosmos*.credential.client-certificate-password` | The password of the certificate file. | +> | `*spring.cloud.azure.cosmos*.credential.client-certificate-path` | The path of a PEM certificate file to use when performing service principal authentication with Azure. | +> | `*spring.cloud.azure.cosmos*.credential.client-id` | The client ID to use when performing service principal authentication with Azure. | +> | `*spring.cloud.azure.cosmos*.credential.client-secret` | The client secret to use when performing service principal authentication with Azure. | +> | `*spring.cloud.azure.cosmos*.credential.managed-identity-enabled` | Whether to enable managed identity. The default value is `false`. | +> | `*spring.cloud.azure.cosmos*.credential.password` | The password to use when performing username/password authentication with Azure. | +> | `*spring.cloud.azure.cosmos*.credential.username` | The username to use when performing username/password authentication with Azure. | +> | `*spring.cloud.azure.cosmos*.populate-query-metrics` | A value that indicates whether to populate diagnostics strings and query metrics. The default value is `false`. | +> | `*spring.cloud.azure.cosmos*.consistency-level` | A [consistency level](/azure/cosmos-db/consistency-levels) for Azure Cosmos DB. | ### Key concepts @@ -67,7 +67,7 @@ The following list shows the key concepts of the Spring Data support: * The Spring Data [@Id](https://github.com/spring-projects/spring-data-commons/blob/db62390de90c93a78743c97cc2cc9ccd964994a5/src/main/java/org/springframework/data/annotation/Id.java) annotation. There are two ways to map a field in a domain class to the `id` of an Azure Cosmos DB document: * Annotate a field in domain class with `@Id`. This field will be mapped to document `id` in Azure Cosmos DB. - * Set the name of this field to `id`. This field will be mapped to document `id` in Azure Cosmos DB. + `*` Set the name of this field to `id`. This field will be mapped to document `id` in Azure Cosmos DB. > [!NOTE] > If both ways are applied, the `@Id` annotation has higher priority. diff --git a/articles/java/spring-framework/spring-integration-support.md b/articles/java/spring-framework/spring-integration-support.md index a011d284a..663150c56 100644 --- a/articles/java/spring-framework/spring-integration-support.md +++ b/articles/java/spring-framework/spring-integration-support.md @@ -115,7 +115,7 @@ developers can use `EventHubsContainerProperties` for the configuration. See [th 1. Fill the credential configuration options. - * For credentials as connection string, configure the following properties in your *application.yml* file: + * For credentials as connection string, configure the following properties in your **application.yml** file: ```yaml spring: @@ -130,7 +130,7 @@ developers can use `EventHubsContainerProperties` for the configuration. See [th account-key: ${CHECKPOINT-ACCESS-KEY} ``` - * For credentials as managed identities, configure the following properties in your *application.yml* file: + * For credentials as managed identities, configure the following properties in your **application.yml** file: ```yaml spring: @@ -147,7 +147,7 @@ developers can use `EventHubsContainerProperties` for the configuration. See [th account-name: ${ACCOUNT_NAME} ``` - * For credentials as service principal, configure the following properties in your *application.yml* file: + * For credentials as service principal, configure the following properties in your **application.yml** file: ```yaml spring: @@ -415,7 +415,7 @@ developers can use `ServiceBusContainerProperties` for the configuration. See [t 1. Fill the credential configuration options. - * For credentials as connection string, configure the following properties in your *application.yml* file: + * For credentials as connection string, configure the following properties in your **application.yml** file: ```yaml spring: @@ -425,7 +425,7 @@ developers can use `ServiceBusContainerProperties` for the configuration. See [t connection-string: ${AZURE_SERVICE_BUS_CONNECTION_STRING} ``` - * For credentials as managed identities, configure the following properties in your *application.yml* file: + * For credentials as managed identities, configure the following properties in your **application.yml** file: ```yaml spring: @@ -443,7 +443,7 @@ developers can use `ServiceBusContainerProperties` for the configuration. See [t > [!NOTE] > The values allowed for `tenant-id` are: `common`, `organizations`, `consumers`, or the tenant ID. For more information about these values, see the [Used the wrong endpoint (personal and organization accounts)](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist#cause-3-used-the-wrong-endpoint-personal-and-organization-accounts) section of [Error AADSTS50020 - User account from identity provider does not exist in tenant](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist). For information on converting your single-tenant app, see [Convert single-tenant app to multitenant on Microsoft Entra ID](/entra/identity-platform/howto-convert-app-to-be-multi-tenant). - * For credentials as service principal, configure the following properties in your *application.yml* file: + * For credentials as service principal, configure the following properties in your **application.yml** file: ```yaml spring: @@ -615,7 +615,7 @@ Mapping between Service Bus Headers and Spring Headers: This starter supports [Service Bus partitioning](/azure/service-bus-messaging/service-bus-partitioning) by allowing setting partition key and session ID in the message header. This section introduces how to set partition key for messages. -*Recommended:* Use `ServiceBusMessageHeaders.PARTITION_KEY` as the key of the header. +Recommended: Use `ServiceBusMessageHeaders.PARTITION_KEY` as the key of the header. ```java public class SampleController { @@ -630,7 +630,7 @@ public class SampleController { } ``` -*Not recommended but currently supported:* `AzureHeaders.PARTITION_KEY` as the key of the header. +Not recommended but currently supported: `AzureHeaders.PARTITION_KEY` as the key of the header. ```java public class SampleController { @@ -730,7 +730,7 @@ Connection configurable properties of spring-cloud-azure-starter-integration-sto 1. Fill the credential configuration options. - * For credentials as connection string, configure the following properties in your *application.yml* file: + * For credentials as connection string, configure the following properties in your **application.yml** file: ```yaml spring: @@ -741,7 +741,7 @@ Connection configurable properties of spring-cloud-azure-starter-integration-sto connection-string: ${AZURE_STORAGE_QUEUE_CONNECTION_STRING} ``` - * For credentials as managed identities, configure the following properties in your *application.yml* file: + * For credentials as managed identities, configure the following properties in your **application.yml** file: ```yaml spring: @@ -760,7 +760,7 @@ Connection configurable properties of spring-cloud-azure-starter-integration-sto > [!NOTE] > The values allowed for `tenant-id` are: `common`, `organizations`, `consumers`, or the tenant ID. For more information about these values, see the [Used the wrong endpoint (personal and organization accounts)](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist#cause-3-used-the-wrong-endpoint-personal-and-organization-accounts) section of [Error AADSTS50020 - User account from identity provider does not exist in tenant](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist). For information on converting your single-tenant app, see [Convert single-tenant app to multitenant on Microsoft Entra ID](/entra/identity-platform/howto-convert-app-to-be-multi-tenant). - * For credentials as service principal, configure the following properties in your *application.yml* file: + * For credentials as service principal, configure the following properties in your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/spring-jms-support.md b/articles/java/spring-framework/spring-jms-support.md index 51336c7e2..fed729f07 100644 --- a/articles/java/spring-framework/spring-jms-support.md +++ b/articles/java/spring-framework/spring-jms-support.md @@ -54,7 +54,7 @@ The following table describes the configurable properties when using the Spring > | **spring.jms.servicebus**.enabled | A value that indicates whether to enable Service Bus JMS autoconfiguration. The default value is `true`. | > | **spring.jms.servicebus**.idle-timeout | The connection idle timeout duration that indicates how long the client expects Service Bus to keep a connection alive when no messages are delivered. The default value is `2m`. | > | **spring.jms.servicebus**.passwordless-enabled | Whether to enable passwordless for Azure Service Bus JMS. The default value is `false`. | -> | **spring.jms.servicebus**.pricing-tier | The Azure Service Bus Price Tier. Supported values are *premium* and *standard*. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | +> | **spring.jms.servicebus**.pricing-tier | The Azure Service Bus Price Tier. Supported values are `premium and `standard`. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | > | **spring.jms.servicebus**.listener.reply-pub-sub-domain | A value that indicates whether the reply destination type is a topic. Only works for the `topicJmsListenerContainerFactory` bean. | > | **spring.jms.servicebus**.listener.phase | The phase in which this container should be started and stopped. | > | **spring.jms.servicebus**.listener.reply-qos-settings | Configures the `QosSettings` to use when sending a reply. | @@ -83,7 +83,7 @@ For more information, see [Spring JMS Document](https://docs.spring.io/spring-fr ### Connect to Azure Service Bus JMS using passwordless -Configure the following properties in your *application.yml* file: +Configure the following properties in your **application.yml** file: ```yaml spring: @@ -101,7 +101,7 @@ spring: 1. To use the managed identity, enable the managed identity for your service and assign the `Azure Service Bus Data Owner` role. For more information, see [Authenticate a managed identity with Microsoft Entra ID to access Azure Service Bus resources](/azure/service-bus-messaging/service-bus-managed-service-identity). -1. Configure the following properties in your *application.yml* file: +1. Configure the following properties in your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/spring-messaging-support.md b/articles/java/spring-framework/spring-messaging-support.md index cba3b2609..f6bc9206e 100644 --- a/articles/java/spring-framework/spring-messaging-support.md +++ b/articles/java/spring-framework/spring-messaging-support.md @@ -22,7 +22,7 @@ This article describes how you can use Spring Cloud Azure and Spring Messaging t ### Key concepts -Azure Event Hubs is a native data-streaming service in the cloud that can stream millions of events per second, with low latency, from any source to any destination. The Spring Messaging for Azure Event Hubs project applies core Spring concepts to the development of event hubs-based messaging solutions. It provides a *template* as a high-level abstraction for sending messages. It also provides support for message-driven plain old Java objects ( ) with `@EventHubsListener` annotations and a *listener container*. These libraries promote the use of dependency injection and declarative configuration. In all of these cases, you can see similarities to the JMS support in the Spring Framework and RabbitMQ support in Spring AMQP. +Azure Event Hubs is a native data-streaming service in the cloud that can stream millions of events per second, with low latency, from any source to any destination. The Spring Messaging for Azure Event Hubs project applies core Spring concepts to the development of event hubs-based messaging solutions. It provides a template as a high-level abstraction for sending messages. It also provides support for message-driven plain old Java objects ( ) with `@EventHubsListener` annotations and a listener container. These libraries promote the use of dependency injection and declarative configuration. In all of these cases, you can see similarities to the JMS support in the Spring Framework and RabbitMQ support in Spring AMQP. ### Dependency setup @@ -63,7 +63,7 @@ Use the following steps to send messages: 1. Fill in the credential configuration options using one of the following approaches: - * For credentials as `DefaultAzureCredential`, configure the following properties in your *application.yml* file: + * For credentials as `DefaultAzureCredential`, configure the following properties in your **application.yml** file: ```yaml spring: @@ -77,7 +77,7 @@ Use the following steps to send messages: account-name: ${CHECKPOINT-STORAGE-ACCOUNT} ``` - * For credentials as connection string, configure the following properties in your *application.yml* file: + * For credentials as connection string, configure the following properties in your **application.yml** file: ```yaml spring: @@ -92,7 +92,7 @@ Use the following steps to send messages: account-key: ${CHECKPOINT-ACCESS-KEY} ``` - * For credentials as managed identities, configure the following properties in your *application.yml* file: + * For credentials as managed identities, configure the following properties in your **application.yml** file: ```yaml spring: @@ -109,7 +109,7 @@ Use the following steps to send messages: account-name: ${ACCOUNT_NAME} ``` - * For credentials as service principal, configure the following properties in your *application.yml* file: + * For credentials as service principal, configure the following properties in your **application.yml** file: ```yaml spring: @@ -190,7 +190,7 @@ For more information, see the [azure-spring-boot-samples](https://github.com/Azu ### Key concepts -Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. The Spring Messaging for Azure Service Bus project applies core Spring concepts to the development of service bus-based messaging solutions. It provides a *template* as a high-level abstraction for sending messages. It also provides support for message-driven POJOs with `@ServiceBusListener` annotations and a *listener container*. These libraries promote the use of dependency injection and declarative configuration. In all of these cases, you can see similarities to the JMS support in the Spring Framework and RabbitMQ support in Spring AMQP. +Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. The Spring Messaging for Azure Service Bus project applies core Spring concepts to the development of service bus-based messaging solutions. It provides a template as a high-level abstraction for sending messages. It also provides support for message-driven POJOs with `@ServiceBusListener` annotations and a listener container. These libraries promote the use of dependency injection and declarative configuration. In all of these cases, you can see similarities to the JMS support in the Spring Framework and RabbitMQ support in Spring AMQP. ### Dependency setup @@ -226,7 +226,7 @@ Use the following steps to send messages: 1. Fill in the credential configuration options using one of the following approaches: - * For credentials as `DefaultAzureCredential`, configure the following properties in your *application.yml* file: + * For credentials as `DefaultAzureCredential`, configure the following properties in your **application.yml** file: ```yaml spring: @@ -237,7 +237,7 @@ Use the following steps to send messages: entity-type: ${AZURE_SERVICE_BUS_ENTITY_TYPE} ``` - * For credentials as connection string, configure the following properties in your *application.yml* file: + * For credentials as connection string, configure the following properties in your **application.yml** file: ```yaml spring: @@ -248,7 +248,7 @@ Use the following steps to send messages: entity-type: ${AZURE_SERVICE_BUS_ENTITY_TYPE} ``` - * For credentials as managed identities, configure the following properties in your *application.yml* file: + * For credentials as managed identities, configure the following properties in your **application.yml** file: ```yaml spring: @@ -267,7 +267,7 @@ Use the following steps to send messages: > [!NOTE] > The following values are allowed for `tenant-id`: `common`, `organizations`, `consumers`, or the tenant ID. For more information about these values, see the [Used the wrong endpoint (personal and organization accounts)](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist#cause-3-used-the-wrong-endpoint-personal-and-organization-accounts) section of [Error AADSTS50020 - User account from identity provider does not exist in tenant](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist). For information on converting your single-tenant app, see [Convert single-tenant app to multitenant on Microsoft Entra ID](/entra/identity-platform/howto-convert-app-to-be-multi-tenant). - * For credentials as service principal, configure the following properties in your *application.yml* file: + * For credentials as service principal, configure the following properties in your **application.yml** file: ```yaml spring: @@ -356,7 +356,7 @@ For more information, see the [azure-spring-boot-samples](https://github.com/Azu ### Key concepts -Azure Queue Storage is a service for storing large numbers of messages. You access messages from anywhere in the world via authenticated calls using HTTP or HTTPS. A queue message can be up to 64 KB in size. A queue can contain millions of messages, up to the total capacity limit of a storage account. Queues are commonly used to create a backlog of work to process asynchronously. The Spring Messaging for Azure Queue Storage project applies core Spring concepts to the development of service bus-based messaging solutions. It provides a *template* as a high-level abstraction for sending and receiving messages. These libraries promote the use of dependency injection and declarative configuration. +Azure Queue Storage is a service for storing large numbers of messages. You access messages from anywhere in the world via authenticated calls using HTTP or HTTPS. A queue message can be up to 64 KB in size. A queue can contain millions of messages, up to the total capacity limit of a storage account. Queues are commonly used to create a backlog of work to process asynchronously. The Spring Messaging for Azure Queue Storage project applies core Spring concepts to the development of service bus-based messaging solutions. It provides a template as a high-level abstraction for sending and receiving messages. These libraries promote the use of dependency injection and declarative configuration. ### Dependency setup @@ -391,7 +391,7 @@ Use the following steps to send and receive messages: 1. Fill in the credential configuration options using one of the following approaches: - * For credentials as `DefaultAzureCredential`, configure the following properties in your *application.yml* file: + * For credentials as `DefaultAzureCredential`, configure the following properties in your **application.yml** file: ```yaml spring: @@ -402,7 +402,7 @@ Use the following steps to send and receive messages: account-name: ${AZURE_STORAGE_QUEUE_ACCOUNT_NAME} ``` - * For credentials as connection string, configure the following properties in your *application.yml* file: + * For credentials as connection string, configure the following properties in your **application.yml** file: ```yaml spring: @@ -413,7 +413,7 @@ Use the following steps to send and receive messages: connection-string: ${AZURE_STORAGE_QUEUE_CONNECTION_STRING} ``` - * For credentials as managed identities, configure the following properties in your *application.yml* file: + * For credentials as managed identities, configure the following properties in your **application.yml** file: ```yaml spring: @@ -432,7 +432,7 @@ Use the following steps to send and receive messages: > [!NOTE] > The following values are allowed for `tenant-id`: `common`, `organizations`, `consumers`, or the tenant ID. For more information about these values, see the [Used the wrong endpoint (personal and organization accounts)](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist#cause-3-used-the-wrong-endpoint-personal-and-organization-accounts) section of [Error AADSTS50020 - User account from identity provider does not exist in tenant](/troubleshoot/azure/active-directory/error-code-aadsts50020-user-account-identity-provider-does-not-exist). For information on converting your single-tenant app, see [Convert single-tenant app to multitenant on Microsoft Entra ID](/entra/identity-platform/howto-convert-app-to-be-multi-tenant). - * For credentials as service principal, configure the following properties in your *application.yml* file: + * For credentials as service principal, configure the following properties in your **application.yml** file: ```yaml spring: diff --git a/articles/java/spring-framework/spring-security-support.md b/articles/java/spring-framework/spring-security-support.md index 67f455482..5737872f0 100644 --- a/articles/java/spring-framework/spring-security-support.md +++ b/articles/java/spring-framework/spring-security-support.md @@ -238,7 +238,7 @@ Developers can customize the redirect-uri. :::image type="content" source="media/spring-cloud-azure/system-diagram-redirect-uri.png" alt-text="System diagram for redirect URIs." border="false"::: -Add `redirect-uri-template` properties in your *application.yml* file. +Add `redirect-uri-template` properties in your **application.yml** file. ```yaml spring: @@ -642,8 +642,8 @@ By doing this, when access `/app-role1` endpoint, the following claims in access To use a JSON Web Token (JWT) for client authentication, use the following steps: 1. See the [Register your certificate with Microsoft identity platform](/azure/active-directory/develop/active-directory-certificate-credentials#register-your-certificate-with-microsoft-identity-platform) section of [Microsoft identity platform application authentication certificate credentials](/azure/active-directory/develop/active-directory-certificate-credentials). -1. Upload a *.pem* certificate to the application registered in the Azure portal. -1. Configure the certificate path and password of a *.PFX* or *.P12* certificate. +1. Upload a **.pem** certificate to the application registered in the Azure portal. +1. Configure the certificate path and password of a **.PFX** or **.P12** certificate. 1. Add the property `spring.cloud.azure.active-directory.authorization-clients.azure.client-authentication-method=private_key_jwt` configuration to the client to be authenticated through JWT client authentication. The following example configuration file is for a web application scenario. The certificate information is configured in the global properties. @@ -1055,7 +1055,7 @@ Grant admin consent for ***Graph*** permissions. :::image type="content" source="media/spring-cloud-azure/add-graph-permissions.png" alt-text="Azure portal screenshot showing API permissions screen for an app, with graph permissions highlighted." lightbox="media/spring-cloud-azure/add-graph-permissions.png"::: -Add the following dependencies to your *pom.xml* file. +Add the following dependencies to your **pom.xml** file. ##### [Spring Cloud Azure 5.x](#tab/SpringCloudAzure5x) @@ -1113,7 +1113,7 @@ Add the following dependencies to your *pom.xml* file. --- -Add properties to your *application.yml* file using the values you created earlier, as shown in the following example: +Add properties to your **application.yml** file using the values you created earlier, as shown in the following example: ```yaml spring: @@ -1216,9 +1216,9 @@ public class WebSecurityConfiguration extends WebSecurityConfigurerAdapter { --- -Copy the *home.html* from [aad-b2c-web-application sample](https://github.com/Azure-Samples/azure-spring-boot-samples/tree/main/aad/spring-cloud-azure-starter-active-directory-b2c/aad-b2c-web-application/src/main/resources/templates/home.html), and replace the `PROFILE_EDIT_USER_FLOW` and `PASSWORD_RESET_USER_FLOW` with your user flow names that you used previously. +Copy the **home.html** from [aad-b2c-web-application sample](https://github.com/Azure-Samples/azure-spring-boot-samples/tree/main/aad/spring-cloud-azure-starter-active-directory-b2c/aad-b2c-web-application/src/main/resources/templates/home.html), and replace the `PROFILE_EDIT_USER_FLOW` and `PASSWORD_RESET_USER_FLOW` with your user flow names that you used previously. -Build and test your app. Let `Webapp` run on port *8080*. +Build and test your app. Let `Webapp` run on port `8080`. After your application is built and started by Maven, open `http://localhost:8080/` in a web browser. You should be redirected to the login page. @@ -1334,7 +1334,7 @@ public class SampleConfiguration { To write your `WebApiA` Java code, see the **Accessing a resource server** section. -Build and test your app. Let `Webapp` and `WebApiA` run on port *8080* and *8081* respectively. Start the `Webapp` and `WebApiA` applications. Return to the home page after logging in successfully. You can then access `http://localhost:8080/webapp/webApiA` to get the `WebApiA` resource response. +Build and test your app. Let `Webapp` and `WebApiA` run on port `8080` and `8081` respectively. Start the `Webapp` and `WebApiA` applications. Return to the home page after logging in successfully. You can then access `http://localhost:8080/webapp/webApiA` to get the `WebApiA` resource response. #### Usage 3: Accessing a resource server @@ -1344,7 +1344,7 @@ To build your `WebApiA` permission, see [Usage 2: Web Application Accessing Reso Add `WebApiA` permission and grant admin consent for your web application. -Add the following dependencies to your *pom.xml* file. +Add the following dependencies to your **pom.xml** file. ```xml @@ -1446,7 +1446,7 @@ public class ResourceServerConfiguration extends WebSecurityConfigurerAdapter { --- -Build and test your app. Let `WebApiA` run on port *8081*. Get the access token for the `webApiA` resource and then access `http://localhost:8081/webApiA/sample` as the Bearer authorization header. +Build and test your app. Let `WebApiA` run on port `8081`. Get the access token for the `webApiA` resource and then access `http://localhost:8081/webApiA/sample` as the Bearer authorization header. #### Usage 4: Resource server accessing other resource servers @@ -1473,7 +1473,7 @@ Grant admin consent for `WebApiB` permissions. :::image type="content" source="media/spring-cloud-azure/application-api-permissions-web-api-a.png" alt-text="Azure portal screenshot showing application WebApiA API permissions screen." lightbox="media/spring-cloud-azure/application-api-permissions-web-api-a.png"::: -On the basis of **Accessing a resource server**, add the following dependency to your *pom.xml* file. +On the basis of **Accessing a resource server**, add the following dependency to your **pom.xml** file. ```xml @@ -1560,7 +1560,7 @@ public class SampleConfiguration { } ``` -Build and test your app. Let `WebApiA` and `WebApiB` run on port *8081* and *8082* respectively. Start the `WebApiA` and `WebApiB` applications, get the access token for `webApiA` resource, and access `http://localhost:8081/webApiA/webApiB/sample` as the Bearer authorization header. +Build and test your app. Let `WebApiA` and `WebApiB` run on port `8081` and `8082` respectively. Start the `WebApiA` and `WebApiB` applications, get the access token for `webApiA` resource, and access `http://localhost:8081/webApiA/webApiB/sample` as the Bearer authorization header. ### Samples diff --git a/articles/java/spring-framework/testcontainers-support.md b/articles/java/spring-framework/testcontainers-support.md index eefa47dda..029b56ba7 100644 --- a/articles/java/spring-framework/testcontainers-support.md +++ b/articles/java/spring-framework/testcontainers-support.md @@ -14,7 +14,7 @@ ms.custom: devx-track-java, devx-track-extended-java This article describes how to integrate Spring Cloud Azure with [Testcontainers](https://testcontainers.com/) to write effective integration tests for your applications. -*Testcontainers* is an open-source framework for providing throwaway, lightweight instances of databases, message brokers, web browsers, or just about anything that can run in a Docker container. It integrates with JUnit, enabling you to write a test class that can start up a container before any of the tests run. Testcontainers is especially useful for writing integration tests that talk to a real backend service. +Testcontainers is an open-source framework for providing throwaway, lightweight instances of databases, message brokers, web browsers, or just about anything that can run in a Docker container. It integrates with JUnit, enabling you to write a test class that can start up a container before any of the tests run. Testcontainers is especially useful for writing integration tests that talk to a real backend service. The `spring-cloud-azure-testcontainers` library now supports integration testing for the following Azure services: diff --git a/articles/java/spring-framework/using-event-hubs-in-spring-applications.md b/articles/java/spring-framework/using-event-hubs-in-spring-applications.md index edbb3d85c..ec2debff3 100644 --- a/articles/java/spring-framework/using-event-hubs-in-spring-applications.md +++ b/articles/java/spring-framework/using-event-hubs-in-spring-applications.md @@ -52,7 +52,7 @@ The [Spring Cloud Azure Event Hubs Starter](https://mvnrepository.com/artifact/c ### Add dependencies -To install the Spring Cloud Azure Event Hubs Starter module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Event Hubs Starter module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -72,7 +72,7 @@ To install the Spring Cloud Azure Event Hubs Starter module, add the following d > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Event Hubs artifact: @@ -356,7 +356,7 @@ You can build the client beans by yourself, but the process is complicated. In S The following list shows some reasons why this code isn't flexible or graceful: - The Event Hubs namespace and event hub name are hard coded. -- If you use `@Value` to get configurations from the Spring environment, you can't have IDE hints in your *application.properties* file. +- If you use `@Value` to get configurations from the Spring environment, you can't have IDE hints in your **application.properties** file. - If you have a microservice scenario, you must duplicate the code in each project, and it's easy to make mistakes and hard to be consistent. Fortunately, building the client beans by yourself isn't necessary with Spring Cloud Azure. Instead, you can directly inject them and use the configuration properties that you're already familiar with to configure Storage queue. For more information, see [Spring Cloud Azure configuration](configuration.md). @@ -382,7 +382,7 @@ This guide shows you how to use Spring Messaging Azure Event Hubs to send messag ### Add dependencies -To install the Spring Messaging Azure Event Hubs module, add the following dependencies to your *pom.xml* file: +To install the Spring Messaging Azure Event Hubs module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -402,7 +402,7 @@ To install the Spring Messaging Azure Event Hubs module, add the following depen > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure starter, Spring Messaging Event Hubs and Azure Event Hubs Checkpoint Store artifacts: @@ -506,7 +506,7 @@ This guide shows you how to use Spring Integration Azure Event Hubs to send mess ### Add dependencies -To install the Spring Cloud Azure Event Hubs Integration Starter module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Event Hubs Integration Starter module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -526,7 +526,7 @@ To install the Spring Cloud Azure Event Hubs Integration Starter module, add the > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Event Hubs Integration artifact: @@ -695,7 +695,7 @@ This guide shows you how to use Spring Cloud Stream Event Hubs Binder to send me ### Add dependencies -To install the Spring Cloud Azure Event Hubs Stream Binder module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Event Hubs Stream Binder module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -715,7 +715,7 @@ To install the Spring Cloud Azure Event Hubs Stream Binder module, add the follo > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Event Hubs Stream Binder artifact: @@ -803,7 +803,7 @@ This guide shows you how to use Azure Event Hubs and [Spring Kafka](https://mvnr ### Add dependencies -To install the Spring Cloud Azure starter and Spring Kafka modules, adding the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure starter and Spring Kafka modules, adding the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -823,7 +823,7 @@ To install the Spring Cloud Azure starter and Spring Kafka modules, adding the f > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure starter and Spring Kafka artifact: @@ -905,7 +905,7 @@ This guide shows you how to use Azure Event Hubs and [Spring Cloud Stream Kafka ### Add dependencies -To install the Spring Cloud Azure starter and Spring Cloud Stream binder Kafka modules, adding the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure starter and Spring Cloud Stream binder Kafka modules, adding the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -925,7 +925,7 @@ To install the Spring Cloud Azure starter and Spring Cloud Stream binder Kafka m > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure starter artifact: diff --git a/articles/java/spring-framework/using-service-bus-in-spring-applications.md b/articles/java/spring-framework/using-service-bus-in-spring-applications.md index 64019fa6d..4c9060bd2 100644 --- a/articles/java/spring-framework/using-service-bus-in-spring-applications.md +++ b/articles/java/spring-framework/using-service-bus-in-spring-applications.md @@ -14,7 +14,7 @@ This article shows you how to use Azure Service Bus in Java applications built w Azure provides an asynchronous messaging platform called [Azure Service Bus](/azure/service-bus-messaging/service-bus-messaging-overview) (Service Bus), which is based on the [Advanced Message Queueing Protocol 1.0](http://www.amqp.org/) (AMQP 1.0) standard. You can use Service Bus across the range of supported Azure platforms. -Spring Cloud Azure provides various modules for sending messages to and receiving messages from Service Bus *queues* and *topics*/*subscriptions* using Spring frameworks. +Spring Cloud Azure provides various modules for sending messages to and receiving messages from Service Bus queues and topics/subscriptions using Spring frameworks. You can use the following modules independently or combine them for different use cases: @@ -53,7 +53,7 @@ The [Spring Cloud Azure Service Bus Starter](https://mvnrepository.com/artifact/ ### Add the Service Bus dependency -To install the Spring Cloud Azure Service Bus Starter module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Service Bus Starter module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -73,7 +73,7 @@ To install the Spring Cloud Azure Service Bus Starter module, add the following > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Service Bus artifact: @@ -233,7 +233,7 @@ You can build those client beans by yourself, but the process is complicated. In ``` > [!NOTE] - > Be sure to replace the *``* placeholder with your Service Bus host name from the Azure portal. Replace the *``* placeholder with your own queue name configured in your Service Bus namespace. + > Be sure to replace the `` placeholder with your Service Bus host name from the Azure portal. Replace the `` placeholder with your own queue name configured in your Service Bus namespace. 1. Inject the client beans to your application, as shown in the following example: @@ -284,7 +284,7 @@ You can build those client beans by yourself, but the process is complicated. In The following list shows reasons why this code isn't flexible or graceful: - The namespace and queue/topic/subscription names are hard coded. -- If you use `@Value` to get configurations from the Spring environment, you can't have IDE hints in your *application.properties* file. +- If you use `@Value` to get configurations from the Spring environment, you can't have IDE hints in your **application.properties** file. - If you have a microservice scenario, you must duplicate the code in each project, and it's easy to make mistakes and hard to be consistent. Fortunately, building the client beans by yourself isn't necessary with Spring Cloud Azure. Instead, you can directly inject the beans and use the [configuration properties](spring-cloud-azure.md?tabs=maven#configuration-properties) that you're already familiar with to configure Service Bus. @@ -309,7 +309,7 @@ This guide shows you how to use Spring Cloud Azure Service Bus Starter for JMS A ### Add the Service Bus dependency -To install the Spring Cloud Azure Service Bus JMS Starter module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Service Bus JMS Starter module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -329,7 +329,7 @@ To install the Spring Cloud Azure Service Bus JMS Starter module, add the follow > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Service Bus JMS artifact: @@ -397,7 +397,7 @@ To install the Spring Cloud Azure Service Bus JMS Starter module, add the follow ``` > [!NOTE] - > Be sure to replace the *``* placeholder with your own queue name configured in your Service Bus namespace. + > Be sure to replace the `` placeholder with your own queue name configured in your Service Bus namespace. > > If you're using a topic/subscription, change the `destination` parameter as the topic name, and the `containerFactory` should be `topicJmsListenerContainerFactory`. Also, add the `subscription` parameter to describe the subscription name. @@ -422,7 +422,7 @@ To install the Spring Cloud Azure Service Bus JMS Starter module, add the follow ``` > [!NOTE] - > Be sure to replace the *``* placeholder with your own queue name configured in your Service Bus namespace. + > Be sure to replace the `` placeholder with your own queue name configured in your Service Bus namespace. > [!TIP] > Be sure to add the `@EnableIntegration` annotation, which triggers the discovery of methods annotated with `@JmsListener`, creating the message listener container under the covers. @@ -451,7 +451,7 @@ This guide shows you how to use Spring Messaging Azure Service Bus to send messa ### Add the Service Bus dependency -To install the Spring Messaging Azure Service Bus module, add the following dependencies to your *pom.xml* file: +To install the Spring Messaging Azure Service Bus module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -471,7 +471,7 @@ To install the Spring Messaging Azure Service Bus module, add the following depe > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Messaging Service Bus and Spring Cloud Azure starter artifacts: @@ -558,7 +558,7 @@ This guide shows you how to use Spring Integration Azure Service Bus to send mes ### Add the Service Bus dependency -To install the Spring Cloud Azure Service Bus Integration Starter module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Service Bus Integration Starter module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -578,7 +578,7 @@ To install the Spring Cloud Azure Service Bus Integration Starter module, add th > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Service Bus Integration artifact: @@ -717,7 +717,7 @@ This guide shows you how to use Spring Cloud Stream Service Bus Binder to send m ### Add the Service Bus dependency -To install the Spring Cloud Azure Service Bus Stream Binder module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Service Bus Stream Binder module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -737,7 +737,7 @@ To install the Spring Cloud Azure Service Bus Stream Binder module, add the foll > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Service Bus Integration artifact: @@ -772,7 +772,7 @@ To install the Spring Cloud Azure Service Bus Stream Binder module, add the foll } ``` - - Add the configuration to specify the `queue` name for consuming by replacing the *``* placeholder, as shown in the following example: + - Add the configuration to specify the `queue` name for consuming by replacing the `` placeholder, as shown in the following example: ```properties # name for the `Consumer` bean @@ -803,7 +803,7 @@ To install the Spring Cloud Azure Service Bus Stream Binder module, add the foll } ``` - - Add the configuration to specify the `queue` name for sending by replacing the *``* placeholder in the following example: + - Add the configuration to specify the `queue` name for sending by replacing the `` placeholder in the following example: ```properties # "consume" is added from the previous step diff --git a/articles/java/spring-framework/using-storage-queue-in-spring-applications.md b/articles/java/spring-framework/using-storage-queue-in-spring-applications.md index 7d6ab7318..c78fec0b6 100644 --- a/articles/java/spring-framework/using-storage-queue-in-spring-applications.md +++ b/articles/java/spring-framework/using-storage-queue-in-spring-applications.md @@ -42,7 +42,7 @@ The Spring Cloud Azure Storage Queue Starter module imports [Azure Storage Queue ### Add dependencies -To install the Spring Cloud Azure Storage Queue Starter module, add the following dependencies to your *pom.xml* file: +To install the Spring Cloud Azure Storage Queue Starter module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -62,7 +62,7 @@ To install the Spring Cloud Azure Storage Queue Starter module, add the followin > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure Queue Storage Queue artifact: @@ -155,7 +155,7 @@ To send messages to and receive messages from Azure Storage queues, use the foll You can build the client beans by yourself, but the process is complicated. In Spring Boot applications, you have to manage properties, learn the builder pattern, and register the clients to your Spring application context. The following steps show you how to do that. -1. Build the client programmatically in your Spring application, as shown in the following example. Be sure to replace the *``* placeholder with your own value. +1. Build the client programmatically in your Spring application, as shown in the following example. Be sure to replace the **``** placeholder with your own value. ```java import com.azure.identity.DefaultAzureCredentialBuilder; @@ -210,7 +210,7 @@ You can build the client beans by yourself, but the process is complicated. In S The following list shows reasons why this code isn't flexible or graceful: - The storage account and queue names are hard coded. -- If you use `@Value` to get configurations from the Spring environment, you can't have IDE hints in your *application.properties* file. +- If you use `@Value` to get configurations from the Spring environment, you can't have IDE hints in your **application.properties** file. - If you have a microservice scenario, you must duplicate the code in each project, and it's easy to make mistakes and hard to be consistent. Fortunately, building the client beans by yourself isn't necessary with Spring Cloud Azure. Instead, you can directly inject them and use the configuration properties that you're already familiar with to configure the storage queue. For more information, see [Spring Cloud Azure configuration properties](configuration-properties-all.md). @@ -232,7 +232,7 @@ The following sections show you how to use Spring Messaging Azure Storage Queue ### Add dependencies -To install the Spring Messaging Azure Storage Queue module, add the following dependencies to your *pom.xml* file: +To install the Spring Messaging Azure Storage Queue module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -252,7 +252,7 @@ To install the Spring Messaging Azure Storage Queue module, add the following de > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Cloud Azure starter and Spring Messaging Storage Queue artifacts: @@ -278,7 +278,7 @@ Use the following steps to configure and code your application: spring.cloud.azure.storage.queue.account-name= ``` -1. Wire up a sender and a receiver to send and receive messages with Spring, as shown in the following example. Be sure to replace the *``* placeholder with your own value. +1. Wire up a sender and a receiver to send and receive messages with Spring, as shown in the following example. Be sure to replace the `` placeholder with your own value. ```java import com.azure.spring.messaging.AzureHeaders; @@ -339,7 +339,7 @@ The following sections show you how to use Spring Integration Azure Storage Queu ### Add dependencies -To install the Spring Integration Azure Storage Queue module, add the following dependencies to your *pom.xml* file: +To install the Spring Integration Azure Storage Queue module, add the following dependencies to your **pom.xml** file: - The Spring Cloud Azure Bill of Materials (BOM): @@ -359,7 +359,7 @@ To install the Spring Integration Azure Storage Queue module, add the following > [!NOTE] > If you're using Spring Boot 2.x, be sure to set the `spring-cloud-azure-dependencies` version to `4.19.0`. - > This Bill of Material (BOM) should be configured in the `` section of your *pom.xml* file. This ensures that all Spring Cloud Azure dependencies are using the same version. + > This Bill of Material (BOM) should be configured in the `` section of your **pom.xml** file. This ensures that all Spring Cloud Azure dependencies are using the same version. > For more information about the version used for this BOM, see [Which Version of Spring Cloud Azure Should I Use](https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping#which-version-of-spring-cloud-azure-should-i-use). - The Spring Integration Azure Storage Queue artifacts: @@ -381,7 +381,7 @@ Use the following steps to configure and code your application: spring.cloud.azure.storage.queue.account-name= ``` -1. Create a new `QueueReceiveConfiguration` Java class as shown in the following example. This class is used to define a message receiver. Be sure to replace the *``* placeholder with your own value. +1. Create a new `QueueReceiveConfiguration` Java class as shown in the following example. This class is used to define a message receiver. Be sure to replace the `` placeholder with your own value. ```java import com.azure.spring.integration.storage.queue.inbound.StorageQueueMessageSource; @@ -419,7 +419,7 @@ Use the following steps to configure and code your application: } ``` -1. Create a new `QueueSendConfiguration` Java class as shown in the following example. This class is used to define a message sender. Be sure to replace the *``* placeholder with your own value. +1. Create a new `QueueSendConfiguration` Java class as shown in the following example. This class is used to define a message sender. Be sure to replace the **``** placeholder with your own value. ```java import com.azure.spring.integration.core.handler.DefaultMessageHandler; diff --git a/articles/java/toolkit-for-eclipse/create-hello-world-web-app.md b/articles/java/toolkit-for-eclipse/create-hello-world-web-app.md index def0fd5dd..3f83d9be2 100644 --- a/articles/java/toolkit-for-eclipse/create-hello-world-web-app.md +++ b/articles/java/toolkit-for-eclipse/create-hello-world-web-app.md @@ -43,15 +43,15 @@ The following steps walk you through the Azure sign in process in your Eclipse d 1. Once signed in, close your browser and switch back to your Eclipse IDE. In the **Select Subscriptions** dialog box, select the subscriptions that you want to use, then click **Select**. -### Install required software *(optional)* +### Install required software (optional) To ensure you have required components to work with web app projects, follow these steps: 1. Click the **Help** menu, and then click **Install New Software**. -1. In the **Available Software** dialog, click **Manage**, and make sure the latest Eclipse version is selected (e.g. *2020-06*). +1. In the **Available Software** dialog, click **Manage**, and make sure the latest Eclipse version is selected (e.g. **2020-06**). -1. Click **Apply and Close**. Expand the *Work with:* dropdown menu to show suggested sites. Select the latest Eclipse version site to query available software. +1. Click **Apply and Close**. Expand the **Work with:** dropdown menu to show suggested sites. Select the latest Eclipse version site to query available software. 1. Scroll down the list and select the **Web, XML, Java EE and OSGi Enterprise Development** item. Click **Next**. diff --git a/articles/java/toolkit-for-eclipse/installation.md b/articles/java/toolkit-for-eclipse/installation.md index c37095564..20e9b5bab 100644 --- a/articles/java/toolkit-for-eclipse/installation.md +++ b/articles/java/toolkit-for-eclipse/installation.md @@ -52,7 +52,7 @@ The Eclipse Marketplace wizard in the Eclipse IDE allows users to browse the [Ec ## Install new software -You can install the Azure Toolkit for Eclipse directly from the *Help* menu in the form of new software. +You can install the Azure Toolkit for Eclipse directly from the **Help** menu in the form of new software. 1. Click the **Help** menu, and then click **Install New Software**. diff --git a/articles/java/toolkit-for-eclipse/managing-redis-caches-using-azure-explorer.md b/articles/java/toolkit-for-eclipse/managing-redis-caches-using-azure-explorer.md index c58d932e0..43eda26ee 100644 --- a/articles/java/toolkit-for-eclipse/managing-redis-caches-using-azure-explorer.md +++ b/articles/java/toolkit-for-eclipse/managing-redis-caches-using-azure-explorer.md @@ -30,7 +30,7 @@ The following steps walk you through the steps to create a redis cache using the ![Create New Redis Cache Dialog Box][CR02] - a. **DNS Name**: Specifies the DNS subdomain for the new redis cache, which is prepended to ".redis.cache.windows.net"; for example: *wingtiptoys.redis.cache.windows.net*. + a. **DNS Name**: Specifies the DNS subdomain for the new redis cache, which is prepended to ".redis.cache.windows.net"; for example: **wingtiptoys.redis.cache.windows.net**. b. **Subscription**: Specifies the Azure subscription you want to use for the new redis cache. @@ -38,7 +38,7 @@ The following steps walk you through the steps to create a redis cache using the * **Create New**: Specifies that you want to create a new resource group. * **Use Existing**: Specifies that you will choose from a list of resource groups associated with your Azure account. - d. **Location**: Specifies the location where your redis cache is created; for example, *West US*. + d. **Location**: Specifies the location where your redis cache is created; for example, **West US**. e. **Pricing Tier**: Specifies which pricing tier your redis cache uses; this setting determines the number of client connections. (For more information, see [Redis Cache Pricing].) diff --git a/articles/java/toolkit-for-eclipse/managing-virtual-machines-using-azure-explorer.md b/articles/java/toolkit-for-eclipse/managing-virtual-machines-using-azure-explorer.md index ccf85b23e..fff67f871 100644 --- a/articles/java/toolkit-for-eclipse/managing-virtual-machines-using-azure-explorer.md +++ b/articles/java/toolkit-for-eclipse/managing-virtual-machines-using-azure-explorer.md @@ -26,14 +26,14 @@ The Azure Explorer, which is part of the Azure Toolkit for Eclipse, provides Jav 1. In the **Choose a Subscription** window, select your subscription, and then click **Next**. -1. In the **Select a Virtual Machine Image** window, select your **Location** (e.g. *West US*). You'll have the option to proceed with a recommended image or select a custom image. For this quickstart, we will proceed with the recommended image. +1. In the **Select a Virtual Machine Image** window, select your **Location**, for example, **West US**. You'll have the option to proceed with a recommended image or select a custom image. For this quickstart, we will proceed with the recommended image. If you choose to select a custom image, enter the following information: - * **Publisher**: Specifies the publisher that created the image you'll use to create your virtual machine (for example, *Microsoft*). + * **Publisher**: Specifies the publisher that created the image you'll use to create your virtual machine (for example, **Microsoft**). - * **Offer**: Specifies the virtual machine offering to use from the selected publisher (for example, *JDK*). + * **Offer**: Specifies the virtual machine offering to use from the selected publisher (for example, **JDK**). - * **Sku**: Specifies the stockkeeping unit (SKU) to use from the selected offering (for example, *JDK_8*). + * **Sku**: Specifies the stockkeeping unit (SKU) to use from the selected offering (for example, **JDK_8**). * **Version #**: Specifies which version of the selected SKU to use. diff --git a/articles/java/toolkit-for-intellij/chatgpt-intellij.md b/articles/java/toolkit-for-intellij/chatgpt-intellij.md index 40516cedb..905d3a486 100644 --- a/articles/java/toolkit-for-intellij/chatgpt-intellij.md +++ b/articles/java/toolkit-for-intellij/chatgpt-intellij.md @@ -44,7 +44,7 @@ The following steps walk you through the Azure sign-in process in your IntelliJ 1. After the sign-in workflow, right-click the Azure OpenAI item in Azure Explorer and select **Create Azure OpenAI Service**. 1. In the **Create Azure OpenAI Service** dialog box, specify the following information and then select **OK**: - - **Name**: A descriptive name for your Azure OpenAI Service resource, such as *MyOpenAIResource*. This name is also your custom domain name in your endpoint. Your resource name can only include alphanumeric characters and hyphens, and can't start or end with a hyphen. + - **Name**: A descriptive name for your Azure OpenAI Service resource, such as **MyOpenAIResource**. This name is also your custom domain name in your endpoint. Your resource name can only include alphanumeric characters and hyphens, and can't start or end with a hyphen. - **Region**: The location of your instance. Certain models are only available in specific regions. For more information, see [Azure OpenAI Service models](/azure/ai-services/openai/concepts/models). - **Sku**: Standard Azure OpenAI resources are billed based on token usage. For more information, see [Azure OpenAI Service pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/). From 45e98ca72f1fb39e2c0ee8853beac68373d4442b Mon Sep 17 00:00:00 2001 From: JoshTheTechWriter <183134486+JoshTheTechWriter@users.noreply.github.com> Date: Mon, 20 Jan 2025 15:10:53 -0500 Subject: [PATCH 18/21] Removed backticks from three files. --- .../spring-framework/resource-handling.md | 16 ++++++------ .../spring-framework/secret-management.md | 24 ++++++++--------- .../spring-framework/spring-data-support.md | 26 +++++++++---------- 3 files changed, 33 insertions(+), 33 deletions(-) diff --git a/articles/java/spring-framework/resource-handling.md b/articles/java/spring-framework/resource-handling.md index 18034ce63..5d5b2e0e8 100644 --- a/articles/java/spring-framework/resource-handling.md +++ b/articles/java/spring-framework/resource-handling.md @@ -53,20 +53,20 @@ The following table lists the configurable properties of `spring-cloud-azure-sta > [!div class="mx-tdBreakAll"] > | Property | Default | Description | > |------------------------------------------------|---------|--------------------------------------------------------------------------| -> | `*spring.cloud.azure.storage.blob*.enabled` | true | A value that indicates whether an Azure Blob Storage service is enabled. | -> | `*spring.cloud.azure.storage.blob*.endpoint` | | The URI to connect to Azure Blob Storage. | -> | `*spring.cloud.azure.storage.blob*.account-key` | | The private key to connect to Azure Blob Storage. | -> | `*spring.cloud.azure.storage.blob*.account-name` | | The Azure Storage Blob account name. +> | *spring.cloud.azure.storage.blob*.enabled | true | A value that indicates whether an Azure Blob Storage service is enabled. | +> | *spring.cloud.azure.storage.blob*.endpoint | | The URI to connect to Azure Blob Storage. | +> | *spring.cloud.azure.storage.blob*.account-key | | The private key to connect to Azure Blob Storage. | +> | *spring.cloud.azure.storage.blob*.account-name | | The Azure Storage Blob account name. The following table lists the configurable properties of `spring-cloud-azure-starter-storage-file-share`: > [!div class="mx-tdBreakAll"] > | Property | Default | Description | > |-----------------------------------------------------|---------|-----------------------------------------------------------------------| -> | `*spring.cloud.azure.storage.fileshare*.enabled` | true | A value that indicates whether Azure File Storage service is enabled. | -> | `*spring.cloud.azure.storage.fileshare*.endpoint` | | The URI to connect to Azure File Storage. | -> | `*spring.cloud.azure.storage.fileshare*.account-key` | | The private key to connect to Azure File Storage. | -> | `*spring.cloud.azure.storage.fileshare*.account-name` | | The Azure Storage File Share account name. | +> | *spring.cloud.azure.storage.fileshare*.enabled | true | A value that indicates whether Azure File Storage service is enabled. | +> | *spring.cloud.azure.storage.fileshare*.endpoint | | The URI to connect to Azure File Storage. | +> | *spring.cloud.azure.storage.fileshare*.account-key | | The private key to connect to Azure File Storage. | +> | *spring.cloud.azure.storage.fileshare*.account-name | | The Azure Storage File Share account name. | ## Basic usage diff --git a/articles/java/spring-framework/secret-management.md b/articles/java/spring-framework/secret-management.md index 8e8114595..bd428bec8 100644 --- a/articles/java/spring-framework/secret-management.md +++ b/articles/java/spring-framework/secret-management.md @@ -136,18 +136,18 @@ public static void main(String[] args) { > [!div class="mx-tdBreakAll"] > | Property | Default value | Description | > |--------------------------------------------------------------------------|---------------|--------------------------------------------------------------------------------------------------------| -> | `*spring.cloud.azure.keyvault.secret*.property-source-enabled` | true | Whether to enable the Key Vault property source. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].name` | | Name of this property source. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].endpoint` | | Azure Key Vault endpoint. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].case-sensitive` | false | Whether the secret keys are case-sensitive. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].secret-keys` | | The secret keys supported for this property source. All keys be retrieved if this property is missing. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].refresh-interval` | 30m | Time interval to refresh all Key Vault secrets. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].service-version` | | Secret service version used when making API requests. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].client` | | Client related properties. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].credential` | | Credential related properties. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].profile` | | Profile related properties. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].proxy` | | Proxy related properties. | -> | `*spring.cloud.azure.keyvault.secret*.property-sources[].retry` | | Retry related properties. | +> | *spring.cloud.azure.keyvault.secret*.property-source-enabled | true | Whether to enable the Key Vault property source. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].name | | Name of this property source. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].endpoint | | Azure Key Vault endpoint. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].case-sensitive | false | Whether the secret keys are case-sensitive. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].secret-keys | | The secret keys supported for this property source. All keys be retrieved if this property is missing. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].refresh-interval | 30m | Time interval to refresh all Key Vault secrets. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].service-version | | Secret service version used when making API requests. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].client | | Client related properties. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].credential | | Credential related properties. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].profile | | Profile related properties. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].proxy | | Proxy related properties. | +> | *spring.cloud.azure.keyvault.secret*.property-sources[].retry | | Retry related properties. | * See [Authorize access with Microsoft Entra ID](authentication.md#authorize-access-with-azure-active-directory) to make sure the [security principal](/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object) has been granted the sufficient permission to access the Azure Key Vault Secrets. * If common properties like `client`, `credential`, `profile`, `proxy`, `retry` aren't configured in `spring.cloud.azure.keyvault.secret.property-sources[].xxx`, `spring.cloud.azure.xxx` will be used. See [Spring Cloud Azure configuration](configuration-properties-global.md) to get more information about these common properties. diff --git a/articles/java/spring-framework/spring-data-support.md b/articles/java/spring-framework/spring-data-support.md index aae433ede..78ff612da 100644 --- a/articles/java/spring-framework/spring-data-support.md +++ b/articles/java/spring-framework/spring-data-support.md @@ -37,19 +37,19 @@ The following table lists the configurable properties of `spring-cloud-azure-sta > [!div class="mx-tdBreakAll"] > | Property | Description | > |--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| -> | `*spring.cloud.azure.cosmos*.enabled` | A value that indicates whether Azure Cosmos DB Service is enabled. The default value is `true`. | -> | `*spring.cloud.azure.cosmos*.database` | The Azure Cosmos DB database ID. | -> | `*spring.cloud.azure.cosmos*.endpoint` | The URI to connect Azure Cosmos DB. | -> | `*spring.cloud.azure.cosmos*.key` | The PrivateKey to connect Azure Cosmos DB. | -> | `*spring.cloud.azure.cosmos*.credential.client-certificate-password` | The password of the certificate file. | -> | `*spring.cloud.azure.cosmos*.credential.client-certificate-path` | The path of a PEM certificate file to use when performing service principal authentication with Azure. | -> | `*spring.cloud.azure.cosmos*.credential.client-id` | The client ID to use when performing service principal authentication with Azure. | -> | `*spring.cloud.azure.cosmos*.credential.client-secret` | The client secret to use when performing service principal authentication with Azure. | -> | `*spring.cloud.azure.cosmos*.credential.managed-identity-enabled` | Whether to enable managed identity. The default value is `false`. | -> | `*spring.cloud.azure.cosmos*.credential.password` | The password to use when performing username/password authentication with Azure. | -> | `*spring.cloud.azure.cosmos*.credential.username` | The username to use when performing username/password authentication with Azure. | -> | `*spring.cloud.azure.cosmos*.populate-query-metrics` | A value that indicates whether to populate diagnostics strings and query metrics. The default value is `false`. | -> | `*spring.cloud.azure.cosmos*.consistency-level` | A [consistency level](/azure/cosmos-db/consistency-levels) for Azure Cosmos DB. | +> | *spring.cloud.azure.cosmos*.enabled | A value that indicates whether Azure Cosmos DB Service is enabled. The default value is `true`. | +> | *spring.cloud.azure.cosmos*.database | The Azure Cosmos DB database ID. | +> | *spring.cloud.azure.cosmos*.endpoint | The URI to connect Azure Cosmos DB. | +> | *spring.cloud.azure.cosmos*.key | The PrivateKey to connect Azure Cosmos DB. | +> | *spring.cloud.azure.cosmos*.credential.client-certificate-password | The password of the certificate file. | +> | *spring.cloud.azure.cosmos*.credential.client-certificate-path | The path of a PEM certificate file to use when performing service principal authentication with Azure. | +> | *spring.cloud.azure.cosmos*.credential.client-id | The client ID to use when performing service principal authentication with Azure. | +> | *spring.cloud.azure.cosmos*.credential.client-secret | The client secret to use when performing service principal authentication with Azure. | +> | *spring.cloud.azure.cosmos*.credential.managed-identity-enabled | Whether to enable managed identity. The default value is `false`. | +> | *spring.cloud.azure.cosmos*.credential.password | The password to use when performing username/password authentication with Azure. | +> | *spring.cloud.azure.cosmos*.credential.username | The username to use when performing username/password authentication with Azure. | +> | *spring.cloud.azure.cosmos*.populate-query-metrics | A value that indicates whether to populate diagnostics strings and query metrics. The default value is `false`. | +> | *spring.cloud.azure.cosmos*.consistency-level | A [consistency level](/azure/cosmos-db/consistency-levels) for Azure Cosmos DB. | ### Key concepts From 9c6c24475fb44d9cdd77c6682be231c325c9c4c7 Mon Sep 17 00:00:00 2001 From: azure-sdk Date: Tue, 21 Jan 2025 02:25:28 +0000 Subject: [PATCH 19/21] Update package index with latest published versions --- articles/includes/dotnet-all.md | 6 +++--- articles/includes/dotnet-new.md | 6 +++--- articles/includes/go-all.md | 2 +- articles/includes/go-new.md | 2 +- articles/includes/javascript-all.md | 10 +++++----- articles/includes/javascript-new.md | 2 +- articles/includes/python-all.md | 10 +++++----- articles/includes/python-new.md | 10 +++++----- 8 files changed, 24 insertions(+), 24 deletions(-) diff --git a/articles/includes/dotnet-all.md b/articles/includes/dotnet-all.md index 212a49e03..81b068d86 100644 --- a/articles/includes/dotnet-all.md +++ b/articles/includes/dotnet-all.md @@ -60,7 +60,7 @@ | Key Vault - Keys | NuGet [4.7.0](https://www.nuget.org/packages/Azure.Security.KeyVault.Keys/4.7.0) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Keys-readme) | GitHub [4.7.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Keys_4.7.0/sdk/keyvault/Azure.Security.KeyVault.Keys/) | | Key Vault - Secrets | NuGet [4.7.0](https://www.nuget.org/packages/Azure.Security.KeyVault.Secrets/4.7.0) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Secrets-readme) | GitHub [4.7.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Secrets_4.7.0/sdk/keyvault/Azure.Security.KeyVault.Secrets/) | | Language Text | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.AI.Language.Text/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/AI.Language.Text-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.Language.Text_1.0.0-beta.2/sdk/cognitivelanguage/Azure.AI.Language.Text/) | -| Load Testing | NuGet [1.0.1](https://www.nuget.org/packages/Azure.Developer.LoadTesting/1.0.1) | [docs](/dotnet/api/overview/azure/Developer.LoadTesting-readme) | GitHub [1.0.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Developer.LoadTesting_1.0.1/sdk/loadtestservice/Azure.Developer.LoadTesting/) | +| Load Testing | NuGet [1.0.2](https://www.nuget.org/packages/Azure.Developer.LoadTesting/1.0.2) | [docs](/dotnet/api/overview/azure/Developer.LoadTesting-readme) | GitHub [1.0.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Developer.LoadTesting_1.0.2/sdk/loadtestservice/Azure.Developer.LoadTesting/) | | Maps Common | NuGet [1.0.0-beta.4](https://www.nuget.org/packages/Azure.Maps.Common/1.0.0-beta.4) | [docs](/dotnet/api/overview/azure/Maps.Common-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.4](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Maps.Common_1.0.0-beta.4/sdk/maps/Azure.Maps.Common/) | | Maps Geolocation | NuGet [1.0.0-beta.3](https://www.nuget.org/packages/Azure.Maps.Geolocation/1.0.0-beta.3) | [docs](/dotnet/api/overview/azure/Maps.Geolocation-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.3](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Maps.Geolocation_1.0.0-beta.3/sdk/maps/Azure.Maps.Geolocation/) | | Maps Render | NuGet [2.0.0-beta.1](https://www.nuget.org/packages/Azure.Maps.Rendering/2.0.0-beta.1) | [docs](/dotnet/api/overview/azure/Maps.Rendering-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [2.0.0-beta.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Maps.Rendering_2.0.0-beta.1/sdk/maps/Azure.Maps.Rendering/) | @@ -95,7 +95,7 @@ | Question Answering | NuGet [1.1.0](https://www.nuget.org/packages/Azure.AI.Language.QuestionAnswering/1.1.0) | [docs](/dotnet/api/overview/azure/AI.Language.QuestionAnswering-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.Language.QuestionAnswering_1.1.0/sdk/cognitivelanguage/Azure.AI.Language.QuestionAnswering/) | | Schema Registry | NuGet [1.4.0](https://www.nuget.org/packages/Azure.Data.SchemaRegistry/1.4.0) | [docs](/dotnet/api/overview/azure/Data.SchemaRegistry-readme) | GitHub [1.4.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Data.SchemaRegistry_1.4.0/sdk/schemaregistry/Azure.Data.SchemaRegistry/) | | Schema Registry - Avro | NuGet [1.0.1](https://www.nuget.org/packages/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro/1.0.1) | [docs](/dotnet/api/overview/azure/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro-readme) | GitHub [1.0.1](https://github.com/Azure/azure-sdk-for-net/tree/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro_1.0.1/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro/) | -| Service Bus | NuGet [7.18.2](https://www.nuget.org/packages/Azure.Messaging.ServiceBus/7.18.2) | [docs](/dotnet/api/overview/azure/Messaging.ServiceBus-readme) | GitHub [7.18.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Messaging.ServiceBus_7.18.2/sdk/servicebus/Azure.Messaging.ServiceBus/) | +| Service Bus | NuGet [7.18.3](https://www.nuget.org/packages/Azure.Messaging.ServiceBus/7.18.3) | [docs](/dotnet/api/overview/azure/Messaging.ServiceBus-readme) | GitHub [7.18.3](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Messaging.ServiceBus_7.18.3/sdk/servicebus/Azure.Messaging.ServiceBus/) | | Storage - Blobs | NuGet [12.23.0](https://www.nuget.org/packages/Azure.Storage.Blobs/12.23.0) | [docs](/dotnet/api/overview/azure/Storage.Blobs-readme) | GitHub [12.23.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Storage.Blobs_12.23.0/sdk/storage/Azure.Storage.Blobs/) | | Storage - Blobs Batch | NuGet [12.20.0](https://www.nuget.org/packages/Azure.Storage.Blobs.Batch/12.20.0) | [docs](/dotnet/api/overview/azure/Storage.Blobs.Batch-readme) | GitHub [12.20.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Storage.Blobs.Batch_12.20.0/sdk/storage/Azure.Storage.Blobs.Batch/) | | Storage - Blobs ChangeFeed | NuGet [12.0.0-preview.52](https://www.nuget.org/packages/Azure.Storage.Blobs.ChangeFeed/12.0.0-preview.52) | [docs](/dotnet/api/overview/azure/Storage.Blobs.ChangeFeed-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [12.0.0-preview.52](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Storage.Blobs.ChangeFeed_12.0.0-preview.52/sdk/storage/Azure.Storage.Blobs.ChangeFeed/) | @@ -306,7 +306,7 @@ | Resource Management - Purview | NuGet [1.1.0](https://www.nuget.org/packages/Azure.ResourceManager.Purview/1.1.0)
NuGet [1.2.0-beta.1](https://www.nuget.org/packages/Azure.ResourceManager.Purview/1.2.0-beta.1) | [docs](/dotnet/api/overview/azure/ResourceManager.Purview-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Purview_1.1.0/sdk/purview/Azure.ResourceManager.Purview/)
GitHub [1.2.0-beta.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Purview_1.2.0-beta.1/sdk/purview/Azure.ResourceManager.Purview/) | | Resource Management - Quantum | NuGet [1.0.0-beta.5](https://www.nuget.org/packages/Azure.ResourceManager.Quantum/1.0.0-beta.5) | [docs](/dotnet/api/overview/azure/ResourceManager.Quantum-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.5](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quantum_1.0.0-beta.5/sdk/quantum/Azure.ResourceManager.Quantum/) | | Resource Management - Qumulo | NuGet [1.1.0](https://www.nuget.org/packages/Azure.ResourceManager.Qumulo/1.1.0) | [docs](/dotnet/api/overview/azure/ResourceManager.Qumulo-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Qumulo_1.1.0/sdk/qumulo/Azure.ResourceManager.Qumulo/) | -| Resource Management - Quota | NuGet [1.0.0](https://www.nuget.org/packages/Azure.ResourceManager.Quota/1.0.0)
NuGet [1.1.0-beta.2](https://www.nuget.org/packages/Azure.ResourceManager.Quota/1.1.0-beta.2) | [docs](/dotnet/api/overview/azure/ResourceManager.Quota-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quota_1.0.0/sdk/quota/Azure.ResourceManager.Quota/)
GitHub [1.1.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quota_1.1.0-beta.2/sdk/quota/Azure.ResourceManager.Quota/) | +| Resource Management - Quota | NuGet [1.0.0](https://www.nuget.org/packages/Azure.ResourceManager.Quota/1.0.0)
NuGet [1.1.0-beta.3](https://www.nuget.org/packages/Azure.ResourceManager.Quota/1.1.0-beta.3) | [docs](/dotnet/api/overview/azure/ResourceManager.Quota-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quota_1.0.0/sdk/quota/Azure.ResourceManager.Quota/)
GitHub [1.1.0-beta.3](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quota_1.1.0-beta.3/sdk/quota/Azure.ResourceManager.Quota/) | | Resource Management - Recovery Services | NuGet [1.1.1](https://www.nuget.org/packages/Azure.ResourceManager.RecoveryServices/1.1.1)
NuGet [1.2.0-beta.1](https://www.nuget.org/packages/Azure.ResourceManager.RecoveryServices/1.2.0-beta.1) | [docs](/dotnet/api/overview/azure/ResourceManager.RecoveryServices-readme) | GitHub [1.1.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.RecoveryServices_1.1.1/sdk/recoveryservices/Azure.ResourceManager.RecoveryServices/)
GitHub [1.2.0-beta.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.RecoveryServices_1.2.0-beta.1/sdk/recoveryservices/Azure.ResourceManager.RecoveryServices/) | | Resource Management - Recovery Services Backup | NuGet [1.2.0](https://www.nuget.org/packages/Azure.ResourceManager.RecoveryServicesBackup/1.2.0) | [docs](/dotnet/api/overview/azure/ResourceManager.RecoveryServicesBackup-readme) | GitHub [1.2.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.RecoveryServicesBackup_1.2.0/sdk/recoveryservices-backup/Azure.ResourceManager.RecoveryServicesBackup/) | | Resource Management - Recovery Services Data Replication | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.ResourceManager.RecoveryServicesDataReplication/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/ResourceManager.RecoveryServicesDataReplication-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.RecoveryServicesDataReplication_1.0.0-beta.2/sdk/recoveryservices-datareplication/Azure.ResourceManager.RecoveryServicesDataReplication/) | diff --git a/articles/includes/dotnet-new.md b/articles/includes/dotnet-new.md index 2e4dd5a32..91864963e 100644 --- a/articles/includes/dotnet-new.md +++ b/articles/includes/dotnet-new.md @@ -61,7 +61,7 @@ | Key Vault - Keys | NuGet [4.7.0](https://www.nuget.org/packages/Azure.Security.KeyVault.Keys/4.7.0) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Keys-readme) | GitHub [4.7.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Keys_4.7.0/sdk/keyvault/Azure.Security.KeyVault.Keys/) | | Key Vault - Secrets | NuGet [4.7.0](https://www.nuget.org/packages/Azure.Security.KeyVault.Secrets/4.7.0) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Secrets-readme) | GitHub [4.7.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Secrets_4.7.0/sdk/keyvault/Azure.Security.KeyVault.Secrets/) | | Language Text | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.AI.Language.Text/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/AI.Language.Text-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.Language.Text_1.0.0-beta.2/sdk/cognitivelanguage/Azure.AI.Language.Text/) | -| Load Testing | NuGet [1.0.1](https://www.nuget.org/packages/Azure.Developer.LoadTesting/1.0.1) | [docs](/dotnet/api/overview/azure/Developer.LoadTesting-readme) | GitHub [1.0.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Developer.LoadTesting_1.0.1/sdk/loadtestservice/Azure.Developer.LoadTesting/) | +| Load Testing | NuGet [1.0.2](https://www.nuget.org/packages/Azure.Developer.LoadTesting/1.0.2) | [docs](/dotnet/api/overview/azure/Developer.LoadTesting-readme) | GitHub [1.0.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Developer.LoadTesting_1.0.2/sdk/loadtestservice/Azure.Developer.LoadTesting/) | | Maps Common | NuGet [1.0.0-beta.4](https://www.nuget.org/packages/Azure.Maps.Common/1.0.0-beta.4) | [docs](/dotnet/api/overview/azure/Maps.Common-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.4](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Maps.Common_1.0.0-beta.4/sdk/maps/Azure.Maps.Common/) | | Maps Geolocation | NuGet [1.0.0-beta.3](https://www.nuget.org/packages/Azure.Maps.Geolocation/1.0.0-beta.3) | [docs](/dotnet/api/overview/azure/Maps.Geolocation-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.3](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Maps.Geolocation_1.0.0-beta.3/sdk/maps/Azure.Maps.Geolocation/) | | Maps Render | NuGet [2.0.0-beta.1](https://www.nuget.org/packages/Azure.Maps.Rendering/2.0.0-beta.1) | [docs](/dotnet/api/overview/azure/Maps.Rendering-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [2.0.0-beta.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Maps.Rendering_2.0.0-beta.1/sdk/maps/Azure.Maps.Rendering/) | @@ -99,7 +99,7 @@ | Question Answering | NuGet [1.1.0](https://www.nuget.org/packages/Azure.AI.Language.QuestionAnswering/1.1.0) | [docs](/dotnet/api/overview/azure/AI.Language.QuestionAnswering-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.Language.QuestionAnswering_1.1.0/sdk/cognitivelanguage/Azure.AI.Language.QuestionAnswering/) | | Schema Registry | NuGet [1.4.0](https://www.nuget.org/packages/Azure.Data.SchemaRegistry/1.4.0) | [docs](/dotnet/api/overview/azure/Data.SchemaRegistry-readme) | GitHub [1.4.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Data.SchemaRegistry_1.4.0/sdk/schemaregistry/Azure.Data.SchemaRegistry/) | | Schema Registry - Avro | NuGet [1.0.1](https://www.nuget.org/packages/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro/1.0.1) | [docs](/dotnet/api/overview/azure/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro-readme) | GitHub [1.0.1](https://github.com/Azure/azure-sdk-for-net/tree/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro_1.0.1/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro/) | -| Service Bus | NuGet [7.18.2](https://www.nuget.org/packages/Azure.Messaging.ServiceBus/7.18.2) | [docs](/dotnet/api/overview/azure/Messaging.ServiceBus-readme) | GitHub [7.18.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Messaging.ServiceBus_7.18.2/sdk/servicebus/Azure.Messaging.ServiceBus/) | +| Service Bus | NuGet [7.18.3](https://www.nuget.org/packages/Azure.Messaging.ServiceBus/7.18.3) | [docs](/dotnet/api/overview/azure/Messaging.ServiceBus-readme) | GitHub [7.18.3](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Messaging.ServiceBus_7.18.3/sdk/servicebus/Azure.Messaging.ServiceBus/) | | Storage - Blobs | NuGet [12.23.0](https://www.nuget.org/packages/Azure.Storage.Blobs/12.23.0) | [docs](/dotnet/api/overview/azure/Storage.Blobs-readme) | GitHub [12.23.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Storage.Blobs_12.23.0/sdk/storage/Azure.Storage.Blobs/) | | Storage - Blobs Batch | NuGet [12.20.0](https://www.nuget.org/packages/Azure.Storage.Blobs.Batch/12.20.0) | [docs](/dotnet/api/overview/azure/Storage.Blobs.Batch-readme) | GitHub [12.20.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Storage.Blobs.Batch_12.20.0/sdk/storage/Azure.Storage.Blobs.Batch/) | | Storage - Blobs ChangeFeed | NuGet [12.0.0-preview.52](https://www.nuget.org/packages/Azure.Storage.Blobs.ChangeFeed/12.0.0-preview.52) | [docs](/dotnet/api/overview/azure/Storage.Blobs.ChangeFeed-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [12.0.0-preview.52](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Storage.Blobs.ChangeFeed_12.0.0-preview.52/sdk/storage/Azure.Storage.Blobs.ChangeFeed/) | @@ -313,7 +313,7 @@ | Resource Management - Purview | NuGet [1.1.0](https://www.nuget.org/packages/Azure.ResourceManager.Purview/1.1.0)
NuGet [1.2.0-beta.1](https://www.nuget.org/packages/Azure.ResourceManager.Purview/1.2.0-beta.1) | [docs](/dotnet/api/overview/azure/ResourceManager.Purview-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Purview_1.1.0/sdk/purview/Azure.ResourceManager.Purview/)
GitHub [1.2.0-beta.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Purview_1.2.0-beta.1/sdk/purview/Azure.ResourceManager.Purview/) | | Resource Management - Quantum | NuGet [1.0.0-beta.5](https://www.nuget.org/packages/Azure.ResourceManager.Quantum/1.0.0-beta.5) | [docs](/dotnet/api/overview/azure/ResourceManager.Quantum-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.5](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quantum_1.0.0-beta.5/sdk/quantum/Azure.ResourceManager.Quantum/) | | Resource Management - Qumulo | NuGet [1.1.0](https://www.nuget.org/packages/Azure.ResourceManager.Qumulo/1.1.0) | [docs](/dotnet/api/overview/azure/ResourceManager.Qumulo-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Qumulo_1.1.0/sdk/qumulo/Azure.ResourceManager.Qumulo/) | -| Resource Management - Quota | NuGet [1.0.0](https://www.nuget.org/packages/Azure.ResourceManager.Quota/1.0.0)
NuGet [1.1.0-beta.2](https://www.nuget.org/packages/Azure.ResourceManager.Quota/1.1.0-beta.2) | [docs](/dotnet/api/overview/azure/ResourceManager.Quota-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quota_1.0.0/sdk/quota/Azure.ResourceManager.Quota/)
GitHub [1.1.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quota_1.1.0-beta.2/sdk/quota/Azure.ResourceManager.Quota/) | +| Resource Management - Quota | NuGet [1.0.0](https://www.nuget.org/packages/Azure.ResourceManager.Quota/1.0.0)
NuGet [1.1.0-beta.3](https://www.nuget.org/packages/Azure.ResourceManager.Quota/1.1.0-beta.3) | [docs](/dotnet/api/overview/azure/ResourceManager.Quota-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quota_1.0.0/sdk/quota/Azure.ResourceManager.Quota/)
GitHub [1.1.0-beta.3](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.Quota_1.1.0-beta.3/sdk/quota/Azure.ResourceManager.Quota/) | | Resource Management - Recovery Services | NuGet [1.1.1](https://www.nuget.org/packages/Azure.ResourceManager.RecoveryServices/1.1.1)
NuGet [1.2.0-beta.1](https://www.nuget.org/packages/Azure.ResourceManager.RecoveryServices/1.2.0-beta.1) | [docs](/dotnet/api/overview/azure/ResourceManager.RecoveryServices-readme) | GitHub [1.1.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.RecoveryServices_1.1.1/sdk/recoveryservices/Azure.ResourceManager.RecoveryServices/)
GitHub [1.2.0-beta.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.RecoveryServices_1.2.0-beta.1/sdk/recoveryservices/Azure.ResourceManager.RecoveryServices/) | | Resource Management - Recovery Services Backup | NuGet [1.2.0](https://www.nuget.org/packages/Azure.ResourceManager.RecoveryServicesBackup/1.2.0) | [docs](/dotnet/api/overview/azure/ResourceManager.RecoveryServicesBackup-readme) | GitHub [1.2.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.RecoveryServicesBackup_1.2.0/sdk/recoveryservices-backup/Azure.ResourceManager.RecoveryServicesBackup/) | | Resource Management - Recovery Services Data Replication | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.ResourceManager.RecoveryServicesDataReplication/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/ResourceManager.RecoveryServicesDataReplication-readme?view=azure-dotnet-preview&preserve-view=true) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.ResourceManager.RecoveryServicesDataReplication_1.0.0-beta.2/sdk/recoveryservices-datareplication/Azure.ResourceManager.RecoveryServicesDataReplication/) | diff --git a/articles/includes/go-all.md b/articles/includes/go-all.md index 58414fbd3..7522c4037 100644 --- a/articles/includes/go-all.md +++ b/articles/includes/go-all.md @@ -213,7 +213,7 @@ | Resource Management - Policy Insights | module [0.8.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/policyinsights/armpolicyinsights/v0.8.0/sdk/resourcemanager/policyinsights/armpolicyinsights/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/policyinsights/armpolicyinsights) | GitHub [0.8.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/policyinsights/armpolicyinsights/v0.8.0/sdk/resourcemanager/policyinsights/armpolicyinsights/) | | Resource Management - Portal | module [0.7.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/portal/armportal/v0.7.0/sdk/resourcemanager/portal/armportal/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/portal/armportal) | GitHub [0.7.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/portal/armportal/v0.7.0/sdk/resourcemanager/portal/armportal/) | | Resource Management - PostgreSQL | module [1.2.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresql/v1.2.0/sdk/resourcemanager/postgresql/armpostgresql/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresql/armpostgresql) | GitHub [1.2.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresql/v1.2.0/sdk/resourcemanager/postgresql/armpostgresql/) | -| Resource Management - PostgreSQL Flexible Server | module [3.1.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v3.1.0/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/)
module [4.0.0-beta.5](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v4.0.0-beta.5/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers) | GitHub [3.1.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v3.1.0/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/)
GitHub [4.0.0-beta.5](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v4.0.0-beta.5/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/) | +| Resource Management - PostgreSQL Flexible Server | module [4.0.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v4.0.0/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers) | GitHub [4.0.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v4.0.0/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/) | | Resource Management - PostgreSQL HSC | module [0.6.1](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc/v0.6.1/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc) | GitHub [0.6.1](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc/v0.6.1/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc/) | | Resource Management - Power BI Private Links | module [2.1.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks/v2.1.0/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks) | GitHub [2.1.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks/v2.1.0/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks/) | | Resource Management - Power BI Dedicated | module [1.2.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/powerbidedicated/armpowerbidedicated/v1.2.0/sdk/resourcemanager/powerbidedicated/armpowerbidedicated/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/powerbidedicated/armpowerbidedicated) | GitHub [1.2.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/powerbidedicated/armpowerbidedicated/v1.2.0/sdk/resourcemanager/powerbidedicated/armpowerbidedicated/) | diff --git a/articles/includes/go-new.md b/articles/includes/go-new.md index ee332fbdb..b1fd69f34 100644 --- a/articles/includes/go-new.md +++ b/articles/includes/go-new.md @@ -214,7 +214,7 @@ | Resource Management - Policy Insights | module [0.8.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/policyinsights/armpolicyinsights/v0.8.0/sdk/resourcemanager/policyinsights/armpolicyinsights/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/policyinsights/armpolicyinsights) | GitHub [0.8.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/policyinsights/armpolicyinsights/v0.8.0/sdk/resourcemanager/policyinsights/armpolicyinsights/) | | Resource Management - Portal | module [0.7.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/portal/armportal/v0.7.0/sdk/resourcemanager/portal/armportal/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/portal/armportal) | GitHub [0.7.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/portal/armportal/v0.7.0/sdk/resourcemanager/portal/armportal/) | | Resource Management - PostgreSQL | module [1.2.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresql/v1.2.0/sdk/resourcemanager/postgresql/armpostgresql/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresql/armpostgresql) | GitHub [1.2.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresql/v1.2.0/sdk/resourcemanager/postgresql/armpostgresql/) | -| Resource Management - PostgreSQL Flexible Server | module [3.1.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v3.1.0/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/)
module [4.0.0-beta.5](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v4.0.0-beta.5/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers) | GitHub [3.1.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v3.1.0/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/)
GitHub [4.0.0-beta.5](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v4.0.0-beta.5/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/) | +| Resource Management - PostgreSQL Flexible Server | module [4.0.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v4.0.0/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers) | GitHub [4.0.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/v4.0.0/sdk/resourcemanager/postgresql/armpostgresqlflexibleservers/) | | Resource Management - PostgreSQL HSC | module [0.6.1](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc/v0.6.1/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc) | GitHub [0.6.1](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc/v0.6.1/sdk/resourcemanager/postgresqlhsc/armpostgresqlhsc/) | | Resource Management - Power BI Private Links | module [2.1.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks/v2.1.0/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks) | GitHub [2.1.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks/v2.1.0/sdk/resourcemanager/powerbiprivatelinks/armpowerbiprivatelinks/) | | Resource Management - Power BI Dedicated | module [1.2.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/powerbidedicated/armpowerbidedicated/v1.2.0/sdk/resourcemanager/powerbidedicated/armpowerbidedicated/) | [docs](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/powerbidedicated/armpowerbidedicated) | GitHub [1.2.0](https://github.com/Azure/azure-sdk-for-go/tree/sdk/resourcemanager/powerbidedicated/armpowerbidedicated/v1.2.0/sdk/resourcemanager/powerbidedicated/armpowerbidedicated/) | diff --git a/articles/includes/javascript-all.md b/articles/includes/javascript-all.md index c0a0ccb4b..5e0ab4d33 100644 --- a/articles/includes/javascript-all.md +++ b/articles/includes/javascript-all.md @@ -79,7 +79,7 @@ | Key Vault - Keys | npm [4.9.0](https://www.npmjs.com/package/@azure/keyvault-keys/v/4.9.0) | [docs](/javascript/api/overview/azure/keyvault-keys-readme) | GitHub [4.9.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure/keyvault-keys_4.9.0/sdk/keyvault/keyvault-keys/) | | Key Vault - Secrets | npm [4.9.0](https://www.npmjs.com/package/@azure/keyvault-secrets/v/4.9.0) | [docs](/javascript/api/overview/azure/keyvault-secrets-readme) | GitHub [4.9.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure/keyvault-secrets_4.9.0/sdk/keyvault/keyvault-secrets/) | | Language Text | npm [1.1.0](https://www.npmjs.com/package/@azure/ai-language-text/v/1.1.0) | [docs](/javascript/api/overview/azure/ai-language-text-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure/ai-language-text_1.1.0/sdk/cognitivelanguage/ai-language-text/) | -| Load Testing | npm [1.0.0](https://www.npmjs.com/package/@azure-rest/load-testing/v/1.0.0) | | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure-rest/load-testing_1.0.0/sdk/loadtesting/load-testing-rest/) | +| Load Testing | npm [1.0.1](https://www.npmjs.com/package/@azure-rest/load-testing/v/1.0.1) | | GitHub [1.0.1](https://github.com/Azure/azure-sdk-for-js/tree/@azure-rest/load-testing_1.0.1/sdk/loadtesting/load-testing-rest/) | | Managed Private Endpoints | npm [1.0.0-beta.4](https://www.npmjs.com/package/@azure/synapse-managed-private-endpoints/v/1.0.0-beta.4) | [docs](/javascript/api/overview/azure/synapse-managed-private-endpoints-readme) | GitHub [1.0.0-beta.4](https://github.com/Azure/azure-sdk-for-js/tree/@azure/synapse-managed-private-endpoints_1.0.0-beta.4/sdk/synapse/synapse-managed-private-endpoints/) | | Maps Common | npm [1.0.0-beta.2](https://www.npmjs.com/package/@azure/maps-common/v/1.0.0-beta.2) | [docs](/javascript/api/overview/azure/maps-common-readme) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-js/tree/@azure/maps-common_1.0.0-beta.2/sdk/maps/maps-common/) | | Maps Geolocation | npm [1.0.0-beta.4](https://www.npmjs.com/package/@azure-rest/maps-geolocation/v/1.0.0-beta.4) | | GitHub [1.0.0-beta.4](https://github.com/Azure/azure-sdk-for-js/tree/@azure-rest/maps-geolocation_1.0.0-beta.4/sdk/maps/maps-geolocation-rest/) | @@ -370,7 +370,7 @@ | Resource Management - Workloads SAP Virtual Instance | npm [1.0.0-beta.1](https://www.npmjs.com/package/@azure/arm-workloadssapvirtualinstance/v/1.0.0-beta.1) | [docs](/javascript/api/overview/azure/arm-workloadssapvirtualinstance-readme) | GitHub [1.0.0-beta.1](https://github.com/Azure/azure-sdk-for-js/tree/@azure/arm-workloadssapvirtualinstance_1.0.0-beta.1/sdk/workloads/arm-workloadssapvirtualinstance/) | | Resource Management - Workspaces | npm [1.1.0](https://www.npmjs.com/package/@azure/arm-workspaces/v/1.1.0) | [docs](/javascript/api/overview/azure/arm-workspaces-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/machinelearning/arm-workspaces) | | Resource Management - Template Specs | npm [2.1.0](https://www.npmjs.com/package/@azure/arm-templatespecs/v/2.1.0) | [docs](/javascript/api/overview/azure/arm-templatespecs-readme) | GitHub [2.1.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure/arm-templatespecs_2.1.0/sdk/templatespecs/arm-templatespecs/) | -| @autorest/openapi-to-typespec | npm [0.10.6](https://www.npmjs.com/package/@autorest/openapi-to-typespec/v/0.10.6) | | | +| @autorest/openapi-to-typespec | npm [0.10.7](https://www.npmjs.com/package/@autorest/openapi-to-typespec/v/0.10.7) | | | | @azure-rest/core-client-lro | npm [1.0.0-beta.1](https://www.npmjs.com/package/@azure-rest/core-client-lro/v/1.0.0-beta.1) | | | | @azure-tools/rest-api-diff | npm [0.1.8](https://www.npmjs.com/package/@azure-tools/rest-api-diff/v/0.1.8) | | | | @azure-tools/test-perf | npm [1.0.0](https://www.npmjs.com/package/@azure-tools/test-perf/v/1.0.0) | | | @@ -378,7 +378,7 @@ | @azure-tools/typespec-autorest-canonical | npm [0.11.0](https://www.npmjs.com/package/@azure-tools/typespec-autorest-canonical/v/0.11.0) | | | | @azure-tools/typespec-azure-portal-core | npm [0.50.0](https://www.npmjs.com/package/@azure-tools/typespec-azure-portal-core/v/0.50.0) | | | | @azure-tools/typespec-azure-rulesets | npm [0.50.0](https://www.npmjs.com/package/@azure-tools/typespec-azure-rulesets/v/0.50.0) | | | -| @azure-tools/typespec-client-generator-cli | npm [0.15.1](https://www.npmjs.com/package/@azure-tools/typespec-client-generator-cli/v/0.15.1) | | | +| @azure-tools/typespec-client-generator-cli | npm [0.15.3](https://www.npmjs.com/package/@azure-tools/typespec-client-generator-cli/v/0.15.3) | | | | @azure-tools/typespec-go | npm [0.3.5](https://www.npmjs.com/package/@azure-tools/typespec-go/v/0.3.5) | | | | @azure-tools/typespec-liftr-base | npm [0.7.0](https://www.npmjs.com/package/@azure-tools/typespec-liftr-base/v/0.7.0) | | | | @azure-tools/typespec-liftr-data | npm [0.3.0](https://www.npmjs.com/package/@azure-tools/typespec-liftr-data/v/0.3.0) | | | @@ -405,10 +405,10 @@ | tmlanguage-generator | npm [0.5.10](https://www.npmjs.com/package/tmlanguage-generator/v/0.5.10) | | | | Unknown Display Name | npm [1.0.0-beta.1](https://www.npmjs.com/package/@azure-rest/maps-timezone/v/1.0.0-beta.1) | | | | Unknown Display Name | npm [0.1.3](https://www.npmjs.com/package/@azure-tools/spec-gen-sdk/v/0.1.3) | | | -| Unknown Display Name | npm [0.6.0](https://www.npmjs.com/package/@azure-tools/typespec-rust/v/0.6.0) | | | +| Unknown Display Name | npm [0.7.0](https://www.npmjs.com/package/@azure-tools/typespec-rust/v/0.7.0) | | | | Unknown Display Name | npm [1.0.0-beta.2](https://www.npmjs.com/package/@azure/ai-projects/v/1.0.0-beta.2) | | | | Unknown Display Name | npm [0.64.0](https://www.npmjs.com/package/@typespec/events/v/0.64.0) | | | -| Unknown Display Name | npm [0.1.7](https://www.npmjs.com/package/@typespec/http-client-java/v/0.1.7) | | | +| Unknown Display Name | npm [0.1.9](https://www.npmjs.com/package/@typespec/http-client-java/v/0.1.9) | | | | Unknown Display Name | npm [0.6.6](https://www.npmjs.com/package/@typespec/http-client-python/v/0.6.6) | | | | Unknown Display Name | npm [0.1.0-alpha.7](https://www.npmjs.com/package/@typespec/http-specs/v/0.1.0-alpha.7) | | | | Unknown Display Name | npm [0.64.0](https://www.npmjs.com/package/@typespec/sse/v/0.64.0) | | | diff --git a/articles/includes/javascript-new.md b/articles/includes/javascript-new.md index 7279318e8..85ca12839 100644 --- a/articles/includes/javascript-new.md +++ b/articles/includes/javascript-new.md @@ -81,7 +81,7 @@ | Key Vault - Keys | npm [4.9.0](https://www.npmjs.com/package/@azure/keyvault-keys/v/4.9.0) | [docs](/javascript/api/overview/azure/keyvault-keys-readme) | GitHub [4.9.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure/keyvault-keys_4.9.0/sdk/keyvault/keyvault-keys/) | | Key Vault - Secrets | npm [4.9.0](https://www.npmjs.com/package/@azure/keyvault-secrets/v/4.9.0) | [docs](/javascript/api/overview/azure/keyvault-secrets-readme) | GitHub [4.9.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure/keyvault-secrets_4.9.0/sdk/keyvault/keyvault-secrets/) | | Language Text | npm [1.1.0](https://www.npmjs.com/package/@azure/ai-language-text/v/1.1.0) | [docs](/javascript/api/overview/azure/ai-language-text-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure/ai-language-text_1.1.0/sdk/cognitivelanguage/ai-language-text/) | -| Load Testing | npm [1.0.0](https://www.npmjs.com/package/@azure-rest/load-testing/v/1.0.0) | | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-js/tree/@azure-rest/load-testing_1.0.0/sdk/loadtesting/load-testing-rest/) | +| Load Testing | npm [1.0.1](https://www.npmjs.com/package/@azure-rest/load-testing/v/1.0.1) | | GitHub [1.0.1](https://github.com/Azure/azure-sdk-for-js/tree/@azure-rest/load-testing_1.0.1/sdk/loadtesting/load-testing-rest/) | | Managed Private Endpoints | npm [1.0.0-beta.4](https://www.npmjs.com/package/@azure/synapse-managed-private-endpoints/v/1.0.0-beta.4) | [docs](/javascript/api/overview/azure/synapse-managed-private-endpoints-readme) | GitHub [1.0.0-beta.4](https://github.com/Azure/azure-sdk-for-js/tree/@azure/synapse-managed-private-endpoints_1.0.0-beta.4/sdk/synapse/synapse-managed-private-endpoints/) | | Maps Common | npm [1.0.0-beta.2](https://www.npmjs.com/package/@azure/maps-common/v/1.0.0-beta.2) | [docs](/javascript/api/overview/azure/maps-common-readme) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-js/tree/@azure/maps-common_1.0.0-beta.2/sdk/maps/maps-common/) | | Maps Geolocation | npm [1.0.0-beta.4](https://www.npmjs.com/package/@azure-rest/maps-geolocation/v/1.0.0-beta.4) | | GitHub [1.0.0-beta.4](https://github.com/Azure/azure-sdk-for-js/tree/@azure-rest/maps-geolocation_1.0.0-beta.4/sdk/maps/maps-geolocation-rest/) | diff --git a/articles/includes/python-all.md b/articles/includes/python-all.md index a603eb80f..b832fbc05 100644 --- a/articles/includes/python-all.md +++ b/articles/includes/python-all.md @@ -3,7 +3,7 @@ | AI Evaluation | PyPI [1.1.0](https://pypi.org/project/azure-ai-evaluation/1.1.0) | [docs](/python/api/overview/azure/ai-evaluation-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-evaluation_1.1.0/sdk/evaluation/azure-ai-evaluation/) | | AI Generative | PyPI [1.0.0b11](https://pypi.org/project/azure-ai-generative/1.0.0b11) | [docs](/python/api/overview/azure/ai-generative-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b11](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-generative_1.0.0b11/sdk/ai/azure-ai-generative/) | | AI Model Inference | PyPI [1.0.0b7](https://pypi.org/project/azure-ai-inference/1.0.0b7) | [docs](/python/api/overview/azure/ai-inference-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b7](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-inference_1.0.0b7/sdk/ai/azure-ai-inference/) | -| AI Projects | PyPI [1.0.0b4](https://pypi.org/project/azure-ai-projects/1.0.0b4) | [docs](/python/api/overview/azure/ai-projects-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b4](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-projects_1.0.0b4/sdk/ai/azure-ai-projects/) | +| AI Projects | PyPI [1.0.0b5](https://pypi.org/project/azure-ai-projects/1.0.0b5) | [docs](/python/api/overview/azure/ai-projects-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b5](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-projects_1.0.0b5/sdk/ai/azure-ai-projects/) | | AI Resources | PyPI [1.0.0b8](https://pypi.org/project/azure-ai-resources/1.0.0b8) | [docs](/python/api/overview/azure/ai-resources-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b8](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-resources_1.0.0b8/sdk/ai/azure-ai-resources/) | | Anomaly Detector | PyPI [3.0.0b6](https://pypi.org/project/azure-ai-anomalydetector/3.0.0b6) | [docs](/python/api/overview/azure/ai-anomalydetector-readme?view=azure-python-preview&preserve-view=true) | GitHub [3.0.0b6](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-anomalydetector_3.0.0b6/sdk/anomalydetector/azure-ai-anomalydetector/) | | App Configuration | PyPI [1.7.1](https://pypi.org/project/azure-appconfiguration/1.7.1) | [docs](/python/api/overview/azure/appconfiguration-readme) | GitHub [1.7.1](https://github.com/Azure/azure-sdk-for-python/tree/azure-appconfiguration_1.7.1/sdk/appconfiguration/azure-appconfiguration/) | @@ -56,7 +56,7 @@ | Key Vault - Keys | PyPI [4.10.0](https://pypi.org/project/azure-keyvault-keys/4.10.0) | [docs](/python/api/overview/azure/keyvault-keys-readme) | GitHub [4.10.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-keyvault-keys_4.10.0/sdk/keyvault/azure-keyvault-keys/) | | Key Vault - Secrets | PyPI [4.9.0](https://pypi.org/project/azure-keyvault-secrets/4.9.0) | [docs](/python/api/overview/azure/keyvault-secrets-readme) | GitHub [4.9.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-keyvault-secrets_4.9.0/sdk/keyvault/azure-keyvault-secrets/) | | Load Testing | PyPI [1.0.0](https://pypi.org/project/azure-developer-loadtesting/1.0.0) | [docs](/python/api/overview/azure/developer-loadtesting-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-developer-loadtesting_1.0.0/sdk/loadtesting/azure-developer-loadtesting/) | -| Machine Learning | PyPI [1.23.1](https://pypi.org/project/azure-ai-ml/1.23.1) | [docs](/python/api/overview/azure/ai-ml-readme) | GitHub [1.23.1](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-ml_1.23.1/sdk/ml/azure-ai-ml/) | +| Machine Learning | PyPI [1.24.0](https://pypi.org/project/azure-ai-ml/1.24.0) | [docs](/python/api/overview/azure/ai-ml-readme) | GitHub [1.24.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-ml_1.24.0/sdk/ml/azure-ai-ml/) | | Machine Learning - Feature Store | PyPI [1.0.1](https://pypi.org/project/azureml-featurestore/1.0.1) | | GitHub [1.0.1](https://msdata.visualstudio.com/Vienna/_git/sdk-cli-v2?path=/src/azureml-featurestore) | | Managed Private Endpoints | PyPI [0.4.0](https://pypi.org/project/azure-synapse-managedprivateendpoints/0.4.0) | [docs](/python/api/overview/azure/synapse-managedprivateendpoints-readme?view=azure-python-preview&preserve-view=true) | GitHub [0.4.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-synapse-managedprivateendpoints_0.4.0/sdk/synapse/azure-synapse-managedprivateendpoints/) | | Maps Geolocation | PyPI [1.0.0b3](https://pypi.org/project/azure-maps-geolocation/1.0.0b3) | [docs](/python/api/overview/azure/maps-geolocation-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b3](https://github.com/Azure/azure-sdk-for-python/tree/azure-maps-geolocation_1.0.0b3/sdk/maps/azure-maps-geolocation/) | @@ -128,7 +128,7 @@ | Resource Management - Cognitive Services | PyPI [13.6.0](https://pypi.org/project/azure-mgmt-cognitiveservices/13.6.0) | [docs](/python/api/overview/azure/mgmt-cognitiveservices-readme) | GitHub [13.6.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-cognitiveservices_13.6.0/sdk/cognitiveservices/azure-mgmt-cognitiveservices/) | | Resource Management - Commerce | PyPI [6.0.0](https://pypi.org/project/azure-mgmt-commerce/6.0.0)
PyPI [6.1.0b1](https://pypi.org/project/azure-mgmt-commerce/6.1.0b1) | [docs](/python/api/overview/azure/mgmt-commerce-readme) | GitHub [6.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-commerce_6.0.0/sdk/commerce/azure-mgmt-commerce/)
GitHub [6.1.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-commerce_6.1.0b1/sdk/commerce/azure-mgmt-commerce/) | | Resource Management - Communication | PyPI [2.1.0](https://pypi.org/project/azure-mgmt-communication/2.1.0) | [docs](/python/api/overview/azure/mgmt-communication-readme) | GitHub [2.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-communication_2.1.0/sdk/communication/azure-mgmt-communication/) | -| Resource Management - Compute | PyPI [33.1.0](https://pypi.org/project/azure-mgmt-compute/33.1.0) | [docs](/python/api/overview/azure/mgmt-compute-readme) | GitHub [33.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-compute_33.1.0/sdk/compute/azure-mgmt-compute/) | +| Resource Management - Compute | PyPI [34.0.0](https://pypi.org/project/azure-mgmt-compute/34.0.0) | [docs](/python/api/overview/azure/mgmt-compute-readme) | GitHub [34.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-compute_34.0.0/sdk/compute/azure-mgmt-compute/) | | Resource Management - Compute Fleet | PyPI [1.0.0](https://pypi.org/project/azure-mgmt-computefleet/1.0.0) | [docs](/python/api/overview/azure/mgmt-computefleet-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-computefleet_1.0.0/sdk/computefleet/azure-mgmt-computefleet/) | | Resource Management - Computeschedule | PyPI [1.0.0b1](https://pypi.org/project/azure-mgmt-computeschedule/1.0.0b1) | [docs](/python/api/overview/azure/mgmt-computeschedule-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-computeschedule_1.0.0b1/sdk/computeschedule/azure-mgmt-computeschedule/) | | Resource Management - Confidential Ledger | PyPI [1.0.0](https://pypi.org/project/azure-mgmt-confidentialledger/1.0.0)
PyPI [2.0.0b4](https://pypi.org/project/azure-mgmt-confidentialledger/2.0.0b4) | [docs](/python/api/overview/azure/mgmt-confidentialledger-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-confidentialledger_1.0.0/sdk/confidentialledger/azure-mgmt-confidentialledger/)
GitHub [2.0.0b4](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-confidentialledger_2.0.0b4/sdk/confidentialledger/azure-mgmt-confidentialledger/) | @@ -139,7 +139,7 @@ | Resource Management - Container Apps | PyPI [3.1.0](https://pypi.org/project/azure-mgmt-appcontainers/3.1.0)
PyPI [3.2.0b1](https://pypi.org/project/azure-mgmt-appcontainers/3.2.0b1) | [docs](/python/api/overview/azure/mgmt-appcontainers-readme) | GitHub [3.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-appcontainers_3.1.0/sdk/appcontainers/azure-mgmt-appcontainers/)
GitHub [3.2.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-appcontainers_3.2.0b1/sdk/appcontainers/azure-mgmt-appcontainers/) | | Resource Management - Container Instances | PyPI [10.1.0](https://pypi.org/project/azure-mgmt-containerinstance/10.1.0)
PyPI [10.2.0b1](https://pypi.org/project/azure-mgmt-containerinstance/10.2.0b1) | [docs](/python/api/overview/azure/mgmt-containerinstance-readme) | GitHub [10.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerinstance_10.1.0/sdk/containerinstance/azure-mgmt-containerinstance/)
GitHub [10.2.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerinstance_10.2.0b1/sdk/containerinstance/azure-mgmt-containerinstance/) | | Resource Management - Container Registry | PyPI [10.3.0](https://pypi.org/project/azure-mgmt-containerregistry/10.3.0) | [docs](/python/api/overview/azure/mgmt-containerregistry-readme) | GitHub [10.3.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerregistry_10.3.0/sdk/containerregistry/azure-mgmt-containerregistry/) | -| Resource Management - Container Service | PyPI [33.0.0](https://pypi.org/project/azure-mgmt-containerservice/33.0.0) | [docs](/python/api/overview/azure/mgmt-containerservice-readme) | GitHub [33.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerservice_33.0.0/sdk/containerservice/azure-mgmt-containerservice/) | +| Resource Management - Container Service | PyPI [34.0.0](https://pypi.org/project/azure-mgmt-containerservice/34.0.0) | [docs](/python/api/overview/azure/mgmt-containerservice-readme) | GitHub [34.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerservice_34.0.0/sdk/containerservice/azure-mgmt-containerservice/) | | Resource Management - Container Service Fleet | PyPI [3.0.0](https://pypi.org/project/azure-mgmt-containerservicefleet/3.0.0) | [docs](/python/api/overview/azure/mgmt-containerservicefleet-readme) | GitHub [3.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerservicefleet_3.0.0/sdk/containerservice/azure-mgmt-containerservicefleet/) | | Resource Management - Containerorchestratorruntime | PyPI [1.0.0b1](https://pypi.org/project/azure-mgmt-containerorchestratorruntime/1.0.0b1) | [docs](/python/api/overview/azure/mgmt-containerorchestratorruntime-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerorchestratorruntime_1.0.0b1/sdk/containerorchestratorruntime/azure-mgmt-containerorchestratorruntime/) | | Resource Management - Content Delivery Network | PyPI [13.1.1](https://pypi.org/project/azure-mgmt-cdn/13.1.1) | [docs](/python/api/overview/azure/mgmt-cdn-readme) | GitHub [13.1.1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-cdn_13.1.1/sdk/cdn/azure-mgmt-cdn/) | @@ -259,7 +259,7 @@ | Resource Management - Recovery Services Data Replication | PyPI [1.0.0b1](https://pypi.org/project/azure-mgmt-recoveryservicesdatareplication/1.0.0b1) | [docs](/python/api/overview/azure/mgmt-recoveryservicesdatareplication-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-recoveryservicesdatareplication_1.0.0b1/sdk/recoveryservicesdatareplication/azure-mgmt-recoveryservicesdatareplication/) | | Resource Management - Recovery Services Site Recovery | PyPI [1.2.0](https://pypi.org/project/azure-mgmt-recoveryservicessiterecovery/1.2.0) | [docs](/python/api/overview/azure/mgmt-recoveryservicessiterecovery-readme) | GitHub [1.2.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-recoveryservicessiterecovery_1.2.0/sdk/recoveryservices/azure-mgmt-recoveryservicessiterecovery/) | | Resource Management - Red Hat OpenShift | PyPI [2.0.0](https://pypi.org/project/azure-mgmt-redhatopenshift/2.0.0) | [docs](/python/api/overview/azure/mgmt-redhatopenshift-readme) | GitHub [2.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redhatopenshift_2.0.0/sdk/redhatopenshift/azure-mgmt-redhatopenshift/) | -| Resource Management - Redis | PyPI [14.4.0](https://pypi.org/project/azure-mgmt-redis/14.4.0) | [docs](/python/api/overview/azure/mgmt-redis-readme) | GitHub [14.4.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redis_14.4.0/sdk/redis/azure-mgmt-redis/) | +| Resource Management - Redis | PyPI [14.5.0](https://pypi.org/project/azure-mgmt-redis/14.5.0) | [docs](/python/api/overview/azure/mgmt-redis-readme) | GitHub [14.5.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redis_14.5.0/sdk/redis/azure-mgmt-redis/) | | Resource Management - Redis Enterprise | PyPI [3.0.0](https://pypi.org/project/azure-mgmt-redisenterprise/3.0.0)
PyPI [3.1.0b2](https://pypi.org/project/azure-mgmt-redisenterprise/3.1.0b2) | [docs](/python/api/overview/azure/mgmt-redisenterprise-readme) | GitHub [3.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redisenterprise_3.0.0/sdk/redisenterprise/azure-mgmt-redisenterprise/)
GitHub [3.1.0b2](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redisenterprise_3.1.0b2/sdk/redisenterprise/azure-mgmt-redisenterprise/) | | Resource Management - Relay | PyPI [1.1.0](https://pypi.org/project/azure-mgmt-relay/1.1.0)
PyPI [2.0.0b1](https://pypi.org/project/azure-mgmt-relay/2.0.0b1) | [docs](/python/api/overview/azure/mgmt-relay-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-relay_1.1.0/sdk/relay/azure-mgmt-relay/)
GitHub [2.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-relay_2.0.0b1/sdk/relay/azure-mgmt-relay/) | | Resource Management - Reservations | PyPI [2.3.0](https://pypi.org/project/azure-mgmt-reservations/2.3.0) | [docs](/python/api/overview/azure/mgmt-reservations-readme) | GitHub [2.3.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-reservations_2.3.0/sdk/reservations/azure-mgmt-reservations/) | diff --git a/articles/includes/python-new.md b/articles/includes/python-new.md index bf337a686..7ca05c3fe 100644 --- a/articles/includes/python-new.md +++ b/articles/includes/python-new.md @@ -3,7 +3,7 @@ | AI Evaluation | PyPI [1.1.0](https://pypi.org/project/azure-ai-evaluation/1.1.0) | [docs](/python/api/overview/azure/ai-evaluation-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-evaluation_1.1.0/sdk/evaluation/azure-ai-evaluation/) | | AI Generative | PyPI [1.0.0b11](https://pypi.org/project/azure-ai-generative/1.0.0b11) | [docs](/python/api/overview/azure/ai-generative-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b11](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-generative_1.0.0b11/sdk/ai/azure-ai-generative/) | | AI Model Inference | PyPI [1.0.0b7](https://pypi.org/project/azure-ai-inference/1.0.0b7) | [docs](/python/api/overview/azure/ai-inference-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b7](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-inference_1.0.0b7/sdk/ai/azure-ai-inference/) | -| AI Projects | PyPI [1.0.0b4](https://pypi.org/project/azure-ai-projects/1.0.0b4) | [docs](/python/api/overview/azure/ai-projects-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b4](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-projects_1.0.0b4/sdk/ai/azure-ai-projects/) | +| AI Projects | PyPI [1.0.0b5](https://pypi.org/project/azure-ai-projects/1.0.0b5) | [docs](/python/api/overview/azure/ai-projects-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b5](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-projects_1.0.0b5/sdk/ai/azure-ai-projects/) | | AI Resources | PyPI [1.0.0b8](https://pypi.org/project/azure-ai-resources/1.0.0b8) | [docs](/python/api/overview/azure/ai-resources-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b8](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-resources_1.0.0b8/sdk/ai/azure-ai-resources/) | | Anomaly Detector | PyPI [3.0.0b6](https://pypi.org/project/azure-ai-anomalydetector/3.0.0b6) | [docs](/python/api/overview/azure/ai-anomalydetector-readme?view=azure-python-preview&preserve-view=true) | GitHub [3.0.0b6](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-anomalydetector_3.0.0b6/sdk/anomalydetector/azure-ai-anomalydetector/) | | App Configuration | PyPI [1.7.1](https://pypi.org/project/azure-appconfiguration/1.7.1) | [docs](/python/api/overview/azure/appconfiguration-readme) | GitHub [1.7.1](https://github.com/Azure/azure-sdk-for-python/tree/azure-appconfiguration_1.7.1/sdk/appconfiguration/azure-appconfiguration/) | @@ -59,7 +59,7 @@ | Key Vault - Keys | PyPI [4.10.0](https://pypi.org/project/azure-keyvault-keys/4.10.0) | [docs](/python/api/overview/azure/keyvault-keys-readme) | GitHub [4.10.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-keyvault-keys_4.10.0/sdk/keyvault/azure-keyvault-keys/) | | Key Vault - Secrets | PyPI [4.9.0](https://pypi.org/project/azure-keyvault-secrets/4.9.0) | [docs](/python/api/overview/azure/keyvault-secrets-readme) | GitHub [4.9.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-keyvault-secrets_4.9.0/sdk/keyvault/azure-keyvault-secrets/) | | Load Testing | PyPI [1.0.0](https://pypi.org/project/azure-developer-loadtesting/1.0.0) | [docs](/python/api/overview/azure/developer-loadtesting-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-developer-loadtesting_1.0.0/sdk/loadtesting/azure-developer-loadtesting/) | -| Machine Learning | PyPI [1.23.1](https://pypi.org/project/azure-ai-ml/1.23.1) | [docs](/python/api/overview/azure/ai-ml-readme) | GitHub [1.23.1](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-ml_1.23.1/sdk/ml/azure-ai-ml/) | +| Machine Learning | PyPI [1.24.0](https://pypi.org/project/azure-ai-ml/1.24.0) | [docs](/python/api/overview/azure/ai-ml-readme) | GitHub [1.24.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-ml_1.24.0/sdk/ml/azure-ai-ml/) | | Machine Learning - Feature Store | PyPI [1.0.1](https://pypi.org/project/azureml-featurestore/1.0.1) | | GitHub [1.0.1](https://msdata.visualstudio.com/Vienna/_git/sdk-cli-v2?path=/src/azureml-featurestore) | | Managed Private Endpoints | PyPI [0.4.0](https://pypi.org/project/azure-synapse-managedprivateendpoints/0.4.0) | [docs](/python/api/overview/azure/synapse-managedprivateendpoints-readme?view=azure-python-preview&preserve-view=true) | GitHub [0.4.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-synapse-managedprivateendpoints_0.4.0/sdk/synapse/azure-synapse-managedprivateendpoints/) | | Maps Geolocation | PyPI [1.0.0b3](https://pypi.org/project/azure-maps-geolocation/1.0.0b3) | [docs](/python/api/overview/azure/maps-geolocation-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b3](https://github.com/Azure/azure-sdk-for-python/tree/azure-maps-geolocation_1.0.0b3/sdk/maps/azure-maps-geolocation/) | @@ -139,7 +139,7 @@ | Resource Management - Cognitive Services | PyPI [13.6.0](https://pypi.org/project/azure-mgmt-cognitiveservices/13.6.0) | [docs](/python/api/overview/azure/mgmt-cognitiveservices-readme) | GitHub [13.6.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-cognitiveservices_13.6.0/sdk/cognitiveservices/azure-mgmt-cognitiveservices/) | | Resource Management - Commerce | PyPI [6.0.0](https://pypi.org/project/azure-mgmt-commerce/6.0.0)
PyPI [6.1.0b1](https://pypi.org/project/azure-mgmt-commerce/6.1.0b1) | [docs](/python/api/overview/azure/mgmt-commerce-readme) | GitHub [6.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-commerce_6.0.0/sdk/commerce/azure-mgmt-commerce/)
GitHub [6.1.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-commerce_6.1.0b1/sdk/commerce/azure-mgmt-commerce/) | | Resource Management - Communication | PyPI [2.1.0](https://pypi.org/project/azure-mgmt-communication/2.1.0) | [docs](/python/api/overview/azure/mgmt-communication-readme) | GitHub [2.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-communication_2.1.0/sdk/communication/azure-mgmt-communication/) | -| Resource Management - Compute | PyPI [33.1.0](https://pypi.org/project/azure-mgmt-compute/33.1.0) | [docs](/python/api/overview/azure/mgmt-compute-readme) | GitHub [33.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-compute_33.1.0/sdk/compute/azure-mgmt-compute/) | +| Resource Management - Compute | PyPI [34.0.0](https://pypi.org/project/azure-mgmt-compute/34.0.0) | [docs](/python/api/overview/azure/mgmt-compute-readme) | GitHub [34.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-compute_34.0.0/sdk/compute/azure-mgmt-compute/) | | Resource Management - Compute Fleet | PyPI [1.0.0](https://pypi.org/project/azure-mgmt-computefleet/1.0.0) | [docs](/python/api/overview/azure/mgmt-computefleet-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-computefleet_1.0.0/sdk/computefleet/azure-mgmt-computefleet/) | | Resource Management - Computeschedule | PyPI [1.0.0b1](https://pypi.org/project/azure-mgmt-computeschedule/1.0.0b1) | [docs](/python/api/overview/azure/mgmt-computeschedule-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-computeschedule_1.0.0b1/sdk/computeschedule/azure-mgmt-computeschedule/) | | Resource Management - Confidential Ledger | PyPI [1.0.0](https://pypi.org/project/azure-mgmt-confidentialledger/1.0.0)
PyPI [2.0.0b4](https://pypi.org/project/azure-mgmt-confidentialledger/2.0.0b4) | [docs](/python/api/overview/azure/mgmt-confidentialledger-readme) | GitHub [1.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-confidentialledger_1.0.0/sdk/confidentialledger/azure-mgmt-confidentialledger/)
GitHub [2.0.0b4](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-confidentialledger_2.0.0b4/sdk/confidentialledger/azure-mgmt-confidentialledger/) | @@ -150,7 +150,7 @@ | Resource Management - Container Apps | PyPI [3.1.0](https://pypi.org/project/azure-mgmt-appcontainers/3.1.0)
PyPI [3.2.0b1](https://pypi.org/project/azure-mgmt-appcontainers/3.2.0b1) | [docs](/python/api/overview/azure/mgmt-appcontainers-readme) | GitHub [3.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-appcontainers_3.1.0/sdk/appcontainers/azure-mgmt-appcontainers/)
GitHub [3.2.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-appcontainers_3.2.0b1/sdk/appcontainers/azure-mgmt-appcontainers/) | | Resource Management - Container Instances | PyPI [10.1.0](https://pypi.org/project/azure-mgmt-containerinstance/10.1.0)
PyPI [10.2.0b1](https://pypi.org/project/azure-mgmt-containerinstance/10.2.0b1) | [docs](/python/api/overview/azure/mgmt-containerinstance-readme) | GitHub [10.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerinstance_10.1.0/sdk/containerinstance/azure-mgmt-containerinstance/)
GitHub [10.2.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerinstance_10.2.0b1/sdk/containerinstance/azure-mgmt-containerinstance/) | | Resource Management - Container Registry | PyPI [10.3.0](https://pypi.org/project/azure-mgmt-containerregistry/10.3.0) | [docs](/python/api/overview/azure/mgmt-containerregistry-readme) | GitHub [10.3.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerregistry_10.3.0/sdk/containerregistry/azure-mgmt-containerregistry/) | -| Resource Management - Container Service | PyPI [33.0.0](https://pypi.org/project/azure-mgmt-containerservice/33.0.0) | [docs](/python/api/overview/azure/mgmt-containerservice-readme) | GitHub [33.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerservice_33.0.0/sdk/containerservice/azure-mgmt-containerservice/) | +| Resource Management - Container Service | PyPI [34.0.0](https://pypi.org/project/azure-mgmt-containerservice/34.0.0) | [docs](/python/api/overview/azure/mgmt-containerservice-readme) | GitHub [34.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerservice_34.0.0/sdk/containerservice/azure-mgmt-containerservice/) | | Resource Management - Container Service Fleet | PyPI [3.0.0](https://pypi.org/project/azure-mgmt-containerservicefleet/3.0.0) | [docs](/python/api/overview/azure/mgmt-containerservicefleet-readme) | GitHub [3.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerservicefleet_3.0.0/sdk/containerservice/azure-mgmt-containerservicefleet/) | | Resource Management - Containerorchestratorruntime | PyPI [1.0.0b1](https://pypi.org/project/azure-mgmt-containerorchestratorruntime/1.0.0b1) | [docs](/python/api/overview/azure/mgmt-containerorchestratorruntime-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerorchestratorruntime_1.0.0b1/sdk/containerorchestratorruntime/azure-mgmt-containerorchestratorruntime/) | | Resource Management - Content Delivery Network | PyPI [13.1.1](https://pypi.org/project/azure-mgmt-cdn/13.1.1) | [docs](/python/api/overview/azure/mgmt-cdn-readme) | GitHub [13.1.1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-cdn_13.1.1/sdk/cdn/azure-mgmt-cdn/) | @@ -271,7 +271,7 @@ | Resource Management - Recovery Services Data Replication | PyPI [1.0.0b1](https://pypi.org/project/azure-mgmt-recoveryservicesdatareplication/1.0.0b1) | [docs](/python/api/overview/azure/mgmt-recoveryservicesdatareplication-readme?view=azure-python-preview&preserve-view=true) | GitHub [1.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-recoveryservicesdatareplication_1.0.0b1/sdk/recoveryservicesdatareplication/azure-mgmt-recoveryservicesdatareplication/) | | Resource Management - Recovery Services Site Recovery | PyPI [1.2.0](https://pypi.org/project/azure-mgmt-recoveryservicessiterecovery/1.2.0) | [docs](/python/api/overview/azure/mgmt-recoveryservicessiterecovery-readme) | GitHub [1.2.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-recoveryservicessiterecovery_1.2.0/sdk/recoveryservices/azure-mgmt-recoveryservicessiterecovery/) | | Resource Management - Red Hat OpenShift | PyPI [2.0.0](https://pypi.org/project/azure-mgmt-redhatopenshift/2.0.0) | [docs](/python/api/overview/azure/mgmt-redhatopenshift-readme) | GitHub [2.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redhatopenshift_2.0.0/sdk/redhatopenshift/azure-mgmt-redhatopenshift/) | -| Resource Management - Redis | PyPI [14.4.0](https://pypi.org/project/azure-mgmt-redis/14.4.0) | [docs](/python/api/overview/azure/mgmt-redis-readme) | GitHub [14.4.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redis_14.4.0/sdk/redis/azure-mgmt-redis/) | +| Resource Management - Redis | PyPI [14.5.0](https://pypi.org/project/azure-mgmt-redis/14.5.0) | [docs](/python/api/overview/azure/mgmt-redis-readme) | GitHub [14.5.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redis_14.5.0/sdk/redis/azure-mgmt-redis/) | | Resource Management - Redis Enterprise | PyPI [3.0.0](https://pypi.org/project/azure-mgmt-redisenterprise/3.0.0)
PyPI [3.1.0b2](https://pypi.org/project/azure-mgmt-redisenterprise/3.1.0b2) | [docs](/python/api/overview/azure/mgmt-redisenterprise-readme) | GitHub [3.0.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redisenterprise_3.0.0/sdk/redisenterprise/azure-mgmt-redisenterprise/)
GitHub [3.1.0b2](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-redisenterprise_3.1.0b2/sdk/redisenterprise/azure-mgmt-redisenterprise/) | | Resource Management - Region Move | PyPI [1.0.0b1](https://pypi.org/project/azure-mgmt-regionmove/1.0.0b1) | | GitHub [1.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-regionmove_1.0.0b1/sdk/regionmove/azure-mgmt-regionmove/) | | Resource Management - Relay | PyPI [1.1.0](https://pypi.org/project/azure-mgmt-relay/1.1.0)
PyPI [2.0.0b1](https://pypi.org/project/azure-mgmt-relay/2.0.0b1) | [docs](/python/api/overview/azure/mgmt-relay-readme) | GitHub [1.1.0](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-relay_1.1.0/sdk/relay/azure-mgmt-relay/)
GitHub [2.0.0b1](https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-relay_2.0.0b1/sdk/relay/azure-mgmt-relay/) | From c788994f9312c529ffe10032063ca74cbf38bd21 Mon Sep 17 00:00:00 2001 From: Joshua Goldstein <183134486+JoshTheTechWriter@users.noreply.github.com> Date: Tue, 21 Jan 2025 10:00:26 -0500 Subject: [PATCH 20/21] Apply suggestions from code review --- .../spring-boot-starter-for-entra-developer-guide.md | 6 +++--- articles/java/spring-framework/spring-data-support.md | 2 +- articles/java/spring-framework/spring-messaging-support.md | 6 +++--- articles/java/spring-framework/spring-security-support.md | 2 +- articles/java/spring-framework/testcontainers-support.md | 2 +- .../using-service-bus-in-spring-applications.md | 2 +- .../using-storage-queue-in-spring-applications.md | 4 ++-- .../managing-redis-caches-using-azure-explorer.md | 2 +- .../managing-virtual-machines-using-azure-explorer.md | 2 +- 9 files changed, 14 insertions(+), 14 deletions(-) diff --git a/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md b/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md index a277db36e..c5c63b900 100644 --- a/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md +++ b/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md @@ -54,7 +54,7 @@ This scenario uses the [The OAuth 2.0 authorization code grant](/azure/active-di To use the Microsoft Entra starter in this scenario, use the following steps: -Set the redirect URI to `application-base-uri>/login/oauth2/code/`. For example: `http://localhost:8080/login/oauth2/code/`. Be sure to include the trailing `/`. For more information about the redirect URI, see [Add a redirect URI](/azure/active-directory/develop/quickstart-register-app#add-a-redirect-uri) in [Quickstart: Register an application with the Microsoft identity platform](/azure/active-directory/develop/quickstart-register-app). +Set the redirect URI to `/login/oauth2/code/`. For example: `http://localhost:8080/login/oauth2/code/`. Be sure to include the trailing `/`. For more information about the redirect URI, see [Add a redirect URI](/azure/active-directory/develop/quickstart-register-app#add-a-redirect-uri) in [Quickstart: Register an application with the Microsoft identity platform](/azure/active-directory/develop/quickstart-register-app). :::image type="content" source="media/spring-boot-starter-for-entra-developer-guide/web-application-set-redirect-uri-2.png" alt-text="Screenshot of Azure portal showing web app authentication page with redirect URI highlighted."::: @@ -527,7 +527,7 @@ The Spring Boot Starter for Microsoft Entra ID provides the following properties | spring.cloud.azure.active-directory.app-id-uri | Used by the resource server to validate the audience in the access token. The access token is valid only when the audience is equal to the `` or `` values described previously. | | spring.cloud.azure.active-directory.authorization-clients | A map that configures the resource APIs the application is going to visit. Each item corresponds to one resource API the application is going to visit. In your Spring code, each item corresponds to one `OAuth2AuthorizedClient` object. | | `spring.cloud.azure.active-directory.authorization-clients..scopes` | The API permissions of a resource server that the application is going to acquire. | -| `spring.cloud.azure.active-directory.authorization-clients..authorization-grant-type` | The type of authorization client. Supported types are [authorization_code](/azure/active-directory/develop/v2-oauth2-auth-code-flow) (default type for webapp), [on_behalf_of](/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow) (default type for resource-server), [client_credentials](/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow). | +| `spring.cloud.azure.active-directory.authorization-clients..authorization-grant-type` | The type of authorization client. Supported types are [`authorization_code`](/azure/active-directory/develop/v2-oauth2-auth-code-flow) (default type for webapp), [`on_behalf_of`](/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow) (default type for resource-server), [`client_credentials`](/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow). | | spring.cloud.azure.active-directory.application-type | Refer to [Application type](#application-type). | | spring.cloud.azure.active-directory.profile.environment.active-directory-endpoint | The base URI for the authorization server. The default value is `https://login.microsoftonline.com/`. | | spring.cloud.azure.active-directory.credential.client-id | The registered application ID in Microsoft Entra ID. | @@ -758,7 +758,7 @@ The Azure SDKs for Java offer a consistent logging story to help troubleshoot an ### Enable Spring logging -Spring enables all the supported logging systems to set logger levels in the Spring environment (for example, in **application.properties**) by using `logging.level.=` where level is one of TRACE, DEBUG, INFO, WARN, ERROR, FATAL, or OFF. You can configure the root logger by using `logging.level.root`. +Spring enables all the supported logging systems to set logger levels in the Spring environment (for example, in **application.properties**) by using `logging.level.=` where `` is one of `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`, or `OFF`. You can configure the root logger by using `logging.level.root`. The following example shows potential logging settings in the **application.properties** file: diff --git a/articles/java/spring-framework/spring-data-support.md b/articles/java/spring-framework/spring-data-support.md index 78ff612da..ad8e9fa49 100644 --- a/articles/java/spring-framework/spring-data-support.md +++ b/articles/java/spring-framework/spring-data-support.md @@ -67,7 +67,7 @@ The following list shows the key concepts of the Spring Data support: * The Spring Data [@Id](https://github.com/spring-projects/spring-data-commons/blob/db62390de90c93a78743c97cc2cc9ccd964994a5/src/main/java/org/springframework/data/annotation/Id.java) annotation. There are two ways to map a field in a domain class to the `id` of an Azure Cosmos DB document: * Annotate a field in domain class with `@Id`. This field will be mapped to document `id` in Azure Cosmos DB. - `*` Set the name of this field to `id`. This field will be mapped to document `id` in Azure Cosmos DB. + * Set the name of this field to `id`. This field will be mapped to document `id` in Azure Cosmos DB. > [!NOTE] > If both ways are applied, the `@Id` annotation has higher priority. diff --git a/articles/java/spring-framework/spring-messaging-support.md b/articles/java/spring-framework/spring-messaging-support.md index f6bc9206e..c4d837260 100644 --- a/articles/java/spring-framework/spring-messaging-support.md +++ b/articles/java/spring-framework/spring-messaging-support.md @@ -22,7 +22,7 @@ This article describes how you can use Spring Cloud Azure and Spring Messaging t ### Key concepts -Azure Event Hubs is a native data-streaming service in the cloud that can stream millions of events per second, with low latency, from any source to any destination. The Spring Messaging for Azure Event Hubs project applies core Spring concepts to the development of event hubs-based messaging solutions. It provides a template as a high-level abstraction for sending messages. It also provides support for message-driven plain old Java objects ( ) with `@EventHubsListener` annotations and a listener container. These libraries promote the use of dependency injection and declarative configuration. In all of these cases, you can see similarities to the JMS support in the Spring Framework and RabbitMQ support in Spring AMQP. +Azure Event Hubs is a native data-streaming service in the cloud that can stream millions of events per second, with low latency, from any source to any destination. The Spring Messaging for Azure Event Hubs project applies core Spring concepts to the development of event hubs-based messaging solutions. It provides a *template* as a high-level abstraction for sending messages. It also provides support for message-driven plain old Java objects ( ) with `@EventHubsListener` annotations and a *listener container*. These libraries promote the use of dependency injection and declarative configuration. In all of these cases, you can see similarities to the JMS support in the Spring Framework and RabbitMQ support in Spring AMQP. ### Dependency setup @@ -190,7 +190,7 @@ For more information, see the [azure-spring-boot-samples](https://github.com/Azu ### Key concepts -Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. The Spring Messaging for Azure Service Bus project applies core Spring concepts to the development of service bus-based messaging solutions. It provides a template as a high-level abstraction for sending messages. It also provides support for message-driven POJOs with `@ServiceBusListener` annotations and a listener container. These libraries promote the use of dependency injection and declarative configuration. In all of these cases, you can see similarities to the JMS support in the Spring Framework and RabbitMQ support in Spring AMQP. +Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. The Spring Messaging for Azure Service Bus project applies core Spring concepts to the development of service bus-based messaging solutions. It provides a *template* as a high-level abstraction for sending messages. It also provides support for message-driven POJOs with `@ServiceBusListener` annotations and a *listener container*. These libraries promote the use of dependency injection and declarative configuration. In all of these cases, you can see similarities to the JMS support in the Spring Framework and RabbitMQ support in Spring AMQP. ### Dependency setup @@ -356,7 +356,7 @@ For more information, see the [azure-spring-boot-samples](https://github.com/Azu ### Key concepts -Azure Queue Storage is a service for storing large numbers of messages. You access messages from anywhere in the world via authenticated calls using HTTP or HTTPS. A queue message can be up to 64 KB in size. A queue can contain millions of messages, up to the total capacity limit of a storage account. Queues are commonly used to create a backlog of work to process asynchronously. The Spring Messaging for Azure Queue Storage project applies core Spring concepts to the development of service bus-based messaging solutions. It provides a template as a high-level abstraction for sending and receiving messages. These libraries promote the use of dependency injection and declarative configuration. +Azure Queue Storage is a service for storing large numbers of messages. You access messages from anywhere in the world via authenticated calls using HTTP or HTTPS. A queue message can be up to 64 KB in size. A queue can contain millions of messages, up to the total capacity limit of a storage account. Queues are commonly used to create a backlog of work to process asynchronously. The Spring Messaging for Azure Queue Storage project applies core Spring concepts to the development of service bus-based messaging solutions. It provides a *template* as a high-level abstraction for sending and receiving messages. These libraries promote the use of dependency injection and declarative configuration. ### Dependency setup diff --git a/articles/java/spring-framework/spring-security-support.md b/articles/java/spring-framework/spring-security-support.md index 5737872f0..b3d723fae 100644 --- a/articles/java/spring-framework/spring-security-support.md +++ b/articles/java/spring-framework/spring-security-support.md @@ -1216,7 +1216,7 @@ public class WebSecurityConfiguration extends WebSecurityConfigurerAdapter { --- -Copy the **home.html** from [aad-b2c-web-application sample](https://github.com/Azure-Samples/azure-spring-boot-samples/tree/main/aad/spring-cloud-azure-starter-active-directory-b2c/aad-b2c-web-application/src/main/resources/templates/home.html), and replace the `PROFILE_EDIT_USER_FLOW` and `PASSWORD_RESET_USER_FLOW` with your user flow names that you used previously. +Copy the **home.html** from [`aad-b2c-web-application` sample](https://github.com/Azure-Samples/azure-spring-boot-samples/tree/main/aad/spring-cloud-azure-starter-active-directory-b2c/aad-b2c-web-application/src/main/resources/templates/home.html), and replace the `PROFILE_EDIT_USER_FLOW` and `PASSWORD_RESET_USER_FLOW` with your user flow names that you used previously. Build and test your app. Let `Webapp` run on port `8080`. diff --git a/articles/java/spring-framework/testcontainers-support.md b/articles/java/spring-framework/testcontainers-support.md index 029b56ba7..eefa47dda 100644 --- a/articles/java/spring-framework/testcontainers-support.md +++ b/articles/java/spring-framework/testcontainers-support.md @@ -14,7 +14,7 @@ ms.custom: devx-track-java, devx-track-extended-java This article describes how to integrate Spring Cloud Azure with [Testcontainers](https://testcontainers.com/) to write effective integration tests for your applications. -Testcontainers is an open-source framework for providing throwaway, lightweight instances of databases, message brokers, web browsers, or just about anything that can run in a Docker container. It integrates with JUnit, enabling you to write a test class that can start up a container before any of the tests run. Testcontainers is especially useful for writing integration tests that talk to a real backend service. +*Testcontainers* is an open-source framework for providing throwaway, lightweight instances of databases, message brokers, web browsers, or just about anything that can run in a Docker container. It integrates with JUnit, enabling you to write a test class that can start up a container before any of the tests run. Testcontainers is especially useful for writing integration tests that talk to a real backend service. The `spring-cloud-azure-testcontainers` library now supports integration testing for the following Azure services: diff --git a/articles/java/spring-framework/using-service-bus-in-spring-applications.md b/articles/java/spring-framework/using-service-bus-in-spring-applications.md index 4c9060bd2..6f51555f9 100644 --- a/articles/java/spring-framework/using-service-bus-in-spring-applications.md +++ b/articles/java/spring-framework/using-service-bus-in-spring-applications.md @@ -14,7 +14,7 @@ This article shows you how to use Azure Service Bus in Java applications built w Azure provides an asynchronous messaging platform called [Azure Service Bus](/azure/service-bus-messaging/service-bus-messaging-overview) (Service Bus), which is based on the [Advanced Message Queueing Protocol 1.0](http://www.amqp.org/) (AMQP 1.0) standard. You can use Service Bus across the range of supported Azure platforms. -Spring Cloud Azure provides various modules for sending messages to and receiving messages from Service Bus queues and topics/subscriptions using Spring frameworks. +Spring Cloud Azure provides various modules for sending messages to and receiving messages from Service Bus *queues* and *topics*/*subscriptions* using Spring frameworks. You can use the following modules independently or combine them for different use cases: diff --git a/articles/java/spring-framework/using-storage-queue-in-spring-applications.md b/articles/java/spring-framework/using-storage-queue-in-spring-applications.md index c78fec0b6..ae1b70e0c 100644 --- a/articles/java/spring-framework/using-storage-queue-in-spring-applications.md +++ b/articles/java/spring-framework/using-storage-queue-in-spring-applications.md @@ -155,7 +155,7 @@ To send messages to and receive messages from Azure Storage queues, use the foll You can build the client beans by yourself, but the process is complicated. In Spring Boot applications, you have to manage properties, learn the builder pattern, and register the clients to your Spring application context. The following steps show you how to do that. -1. Build the client programmatically in your Spring application, as shown in the following example. Be sure to replace the **``** placeholder with your own value. +1. Build the client programmatically in your Spring application, as shown in the following example. Be sure to replace the `` placeholder with your own value. ```java import com.azure.identity.DefaultAzureCredentialBuilder; @@ -419,7 +419,7 @@ Use the following steps to configure and code your application: } ``` -1. Create a new `QueueSendConfiguration` Java class as shown in the following example. This class is used to define a message sender. Be sure to replace the **``** placeholder with your own value. +1. Create a new `QueueSendConfiguration` Java class as shown in the following example. This class is used to define a message sender. Be sure to replace the `` placeholder with your own value. ```java import com.azure.spring.integration.core.handler.DefaultMessageHandler; diff --git a/articles/java/toolkit-for-eclipse/managing-redis-caches-using-azure-explorer.md b/articles/java/toolkit-for-eclipse/managing-redis-caches-using-azure-explorer.md index 43eda26ee..d03d14c90 100644 --- a/articles/java/toolkit-for-eclipse/managing-redis-caches-using-azure-explorer.md +++ b/articles/java/toolkit-for-eclipse/managing-redis-caches-using-azure-explorer.md @@ -30,7 +30,7 @@ The following steps walk you through the steps to create a redis cache using the ![Create New Redis Cache Dialog Box][CR02] - a. **DNS Name**: Specifies the DNS subdomain for the new redis cache, which is prepended to ".redis.cache.windows.net"; for example: **wingtiptoys.redis.cache.windows.net**. + a. **DNS Name**: Specifies the DNS subdomain for the new redis cache, which is prepended to **.redis.cache.windows.net**, for example, **wingtiptoys.redis.cache.windows.net**. b. **Subscription**: Specifies the Azure subscription you want to use for the new redis cache. diff --git a/articles/java/toolkit-for-eclipse/managing-virtual-machines-using-azure-explorer.md b/articles/java/toolkit-for-eclipse/managing-virtual-machines-using-azure-explorer.md index fff67f871..2226dfa36 100644 --- a/articles/java/toolkit-for-eclipse/managing-virtual-machines-using-azure-explorer.md +++ b/articles/java/toolkit-for-eclipse/managing-virtual-machines-using-azure-explorer.md @@ -26,7 +26,7 @@ The Azure Explorer, which is part of the Azure Toolkit for Eclipse, provides Jav 1. In the **Choose a Subscription** window, select your subscription, and then click **Next**. -1. In the **Select a Virtual Machine Image** window, select your **Location**, for example, **West US**. You'll have the option to proceed with a recommended image or select a custom image. For this quickstart, we will proceed with the recommended image. +1. In the **Select a Virtual Machine Image** window, select your **Location** (for example, **West US**). You'll have the option to proceed with a recommended image or select a custom image. For this quickstart, we will proceed with the recommended image. If you choose to select a custom image, enter the following information: * **Publisher**: Specifies the publisher that created the image you'll use to create your virtual machine (for example, **Microsoft**). From adf2a9f3f744a651707fb252352034434350bc5a Mon Sep 17 00:00:00 2001 From: Karl Erickson <1775795+KarlErickson@users.noreply.github.com> Date: Tue, 21 Jan 2025 07:37:41 -0800 Subject: [PATCH 21/21] fixes --- .../migration-guide-for-4.0.md | 116 +++++++++--------- ...-boot-starter-for-entra-developer-guide.md | 4 +- .../spring-framework/spring-jms-support.md | 2 +- .../create-hello-world-web-app.md | 2 +- .../hello-world-web-app-linux.md | 4 +- 5 files changed, 64 insertions(+), 64 deletions(-) diff --git a/articles/java/spring-framework/migration-guide-for-4.0.md b/articles/java/spring-framework/migration-guide-for-4.0.md index 4461b5014..cb12e75d6 100644 --- a/articles/java/spring-framework/migration-guide-for-4.0.md +++ b/articles/java/spring-framework/migration-guide-for-4.0.md @@ -429,23 +429,23 @@ The following table shows the property mappings from `azure-spring-boot-starter- > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |-----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| -> | *azure.activedirectory.b2c*.authenticate-additional-parameters | *spring.cloud.azure.active-directory.b2c*.authenticate-additional-parameters | -> | *azure.activedirectory.b2c*.authorization-clients | *spring.cloud.azure.active-directory.b2c*.authorization-clients | -> | *azure.activedirectory.b2c*.authorization-clients..authorization-grant-type | *spring.cloud.azure.active-directory.b2c*.authorization-clients..authorization-grant-type | -> | *azure.activedirectory.b2c*.authorization-clients..scopes | *spring.cloud.azure.active-directory.b2c*.authorization-clients..scopes | -> | *azure.activedirectory.b2c*.app-id-uri | *spring.cloud.azure.active-directory.b2c*.app-id-uri | -> | *azure.activedirectory.b2c*.base-uri | *spring.cloud.azure.active-directory.b2c*.base-uri | -> | *azure.activedirectory.b2c*.client-id | *spring.cloud.azure.active-directory.b2c*.credential.client-id | -> | *azure.activedirectory.b2c*.client-secret | *spring.cloud.azure.active-directory.b2c*.credential.client-secret | -> | *azure.activedirectory.b2c*.jwt-connect-timeout | *spring.cloud.azure.active-directory.b2c*.jwt-connect-timeout | -> | *azure.activedirectory.b2c*.jwt-read-timeout | *spring.cloud.azure.active-directory.b2c*.jwt-read-timeout | -> | *azure.activedirectory.b2c*.jwt-size-limit | *spring.cloud.azure.active-directory.b2c*.jwt-size-limit | -> | *azure.activedirectory.b2c*.login-flow | *spring.cloud.azure.active-directory.b2c*.login-flow | -> | *azure.activedirectory.b2c*.logout-success-url | *spring.cloud.azure.active-directory.b2c*.logout-success-url | -> | *azure.activedirectory.b2c*.reply-url | *spring.cloud.azure.active-directory.b2c*.reply-url | -> | *azure.activedirectory.b2c*.tenant-id | *spring.cloud.azure.active-directory.b2c*.profile.tenant-id | -> | *azure.activedirectory.b2c*.user-flows | *spring.cloud.azure.active-directory.b2c*.user-flows | -> | *azure.activedirectory.b2c*.user-name-attribute-name | *spring.cloud.azure.active-directory.b2c*.user-name-attribute-name | +> | *azure.activedirectory.b2c*.authenticate-additional-parameters | *spring.cloud.azure.active-directory.b2c*.authenticate-additional-parameters | +> | *azure.activedirectory.b2c*.authorization-clients | *spring.cloud.azure.active-directory.b2c*.authorization-clients | +> | *azure.activedirectory.b2c*.authorization-clients..authorization-grant-type | *spring.cloud.azure.active-directory.b2c*.authorization-clients..authorization-grant-type | +> | *azure.activedirectory.b2c*.authorization-clients..scopes | *spring.cloud.azure.active-directory.b2c*.authorization-clients..scopes | +> | *azure.activedirectory.b2c*.app-id-uri | *spring.cloud.azure.active-directory.b2c*.app-id-uri | +> | *azure.activedirectory.b2c*.base-uri | *spring.cloud.azure.active-directory.b2c*.base-uri | +> | *azure.activedirectory.b2c*.client-id | *spring.cloud.azure.active-directory.b2c*.credential.client-id | +> | *azure.activedirectory.b2c*.client-secret | *spring.cloud.azure.active-directory.b2c*.credential.client-secret | +> | *azure.activedirectory.b2c*.jwt-connect-timeout | *spring.cloud.azure.active-directory.b2c*.jwt-connect-timeout | +> | *azure.activedirectory.b2c*.jwt-read-timeout | *spring.cloud.azure.active-directory.b2c*.jwt-read-timeout | +> | *azure.activedirectory.b2c*.jwt-size-limit | *spring.cloud.azure.active-directory.b2c*.jwt-size-limit | +> | *azure.activedirectory.b2c*.login-flow | *spring.cloud.azure.active-directory.b2c*.login-flow | +> | *azure.activedirectory.b2c*.logout-success-url | *spring.cloud.azure.active-directory.b2c*.logout-success-url | +> | *azure.activedirectory.b2c*.reply-url | *spring.cloud.azure.active-directory.b2c*.reply-url | +> | *azure.activedirectory.b2c*.tenant-id | *spring.cloud.azure.active-directory.b2c*.profile.tenant-id | +> | *azure.activedirectory.b2c*.user-flows | *spring.cloud.azure.active-directory.b2c*.user-flows | +> | *azure.activedirectory.b2c*.user-name-attribute-name | *spring.cloud.azure.active-directory.b2c*.user-name-attribute-name | * Removed properties from azure-spring-boot-starter-active-directory-b2c: @@ -523,17 +523,17 @@ The following table shows the property mappings from `azure-spring-boot-starter- > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| -> | *azure.keyvault*.case-sensitive-keys | *spring.cloud.azure.keyvault.secret*.property-source[n].case-sensitive | -> | *azure.keyvault*.certificate-password | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-password | -> | *azure.keyvault*.certificate-path | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-path | -> | *azure.keyvault*.client-id | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-id | -> | *azure.keyvault*.client-key | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-secret | -> | *azure.keyvault*.enabled | *spring.cloud.azure.keyvault.secret*.property-source-enabled and *spring.cloud.azure.keyvault.secret*.property-source-enabled | -> | *azure.keyvault*.order | No longer supported. Use the order in property-source[n] instead. | -> | *azure.keyvault*.refresh-interval | *spring.cloud.azure.keyvault.secret*.property-source[n].refresh-interval | -> | *azure.keyvault*.secret-keys | *spring.cloud.azure.keyvault.secret*.property-source[n].secret-keys | -> | *azure.keyvault*.tenant-id | *spring.cloud.azure.keyvault.secret*.property-source[n].profile.tenant-id | -> | *azure.keyvault*.uri | *spring.cloud.azure.keyvault.secret*.property-source[n].endpoint | +> | *azure.keyvault*.case-sensitive-keys | *spring.cloud.azure.keyvault.secret*.property-source[n].case-sensitive | +> | *azure.keyvault*.certificate-password | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-password | +> | *azure.keyvault*.certificate-path | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-certificate-path | +> | *azure.keyvault*.client-id | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-id | +> | *azure.keyvault*.client-key | *spring.cloud.azure.keyvault.secret*.property-source[n].credential.client-secret | +> | *azure.keyvault*.enabled | *spring.cloud.azure.keyvault.secret*.property-source-enabled and *spring.cloud.azure.keyvault.secret*.property-source-enabled | +> | *azure.keyvault*.order | No longer supported. Use the order in property-source[n] instead. | +> | *azure.keyvault*.refresh-interval | *spring.cloud.azure.keyvault.secret*.property-source[n].refresh-interval | +> | *azure.keyvault*.secret-keys | *spring.cloud.azure.keyvault.secret*.property-source[n].secret-keys | +> | *azure.keyvault*.tenant-id | *spring.cloud.azure.keyvault.secret*.property-source[n].profile.tenant-id | +> | *azure.keyvault*.uri | *spring.cloud.azure.keyvault.secret*.property-source[n].endpoint | * Removed properties from spring-cloud-azure-starter-keyvault-secrets @@ -586,9 +586,9 @@ The following table shows the property mappings from `azure-spring-boot-starter- | Legacy properties | Modern properties | |-------------------------------|------------------------------------------------| -| *azure.storage*.account-name | *spring.cloud.azure.storage.blob*.account-name | -| *azure.storage*.account-key | *spring.cloud.azure.storage.blob*.account-key | -| *azure.storage*.blob-endpoint | *spring.cloud.azure.storage.blob*.endpoint | +| *azure.storage*.account-name | *spring.cloud.azure.storage.blob*.account-name | +| *azure.storage*.account-key | *spring.cloud.azure.storage.blob*.account-key | +| *azure.storage*.blob-endpoint | *spring.cloud.azure.storage.blob*.endpoint | #### API changes @@ -622,9 +622,9 @@ The following table shows the property mappings from `azure-spring-boot-starter- | Legacy properties | Modern properties | |-------------------------------|-----------------------------------------------------| -| *azure.storage*.account-name | *spring.cloud.azure.storage.fileshare*.account-name | -| *azure.storage*.account-key | *spring.cloud.azure.storage.fileshare*.account-key | -| *azure.storage*.file-endpoint | *spring.cloud.azure.storage.fileshare*.endpoint | +| *azure.storage*.account-name | *spring.cloud.azure.storage.fileshare*.account-name | +| *azure.storage*.account-key | *spring.cloud.azure.storage.fileshare*.account-key | +| *azure.storage*.file-endpoint | *spring.cloud.azure.storage.fileshare*.endpoint | #### API changes @@ -662,12 +662,12 @@ The following table shows property mappings from `azure-spring-cloud-starter-eve > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |----------------------------------------------------------|--------------------------------------------------------------------------| -> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.eventhubs*.resource.resource-group | -> | *spring.cloud.azure.eventhub*.namespace | *spring.cloud.azure.eventhubs*.namespace | -> | *spring.cloud.azure.eventhub*.connection-string | *spring.cloud.azure.eventhubs*.connection-string | -> | *spring.cloud.azure.eventhub*.checkpoint-storage-account | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name | -> | *spring.cloud.azure.eventhub*.checkpoint-access-key | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key | -> | *spring.cloud.azure.eventhub*.checkpoint-container | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name | +> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.eventhubs*.resource.resource-group | +> | *spring.cloud.azure.eventhub*.namespace | *spring.cloud.azure.eventhubs*.namespace | +> | *spring.cloud.azure.eventhub*.connection-string | *spring.cloud.azure.eventhubs*.connection-string | +> | *spring.cloud.azure.eventhub*.checkpoint-storage-account | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name | +> | *spring.cloud.azure.eventhub*.checkpoint-access-key | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key | +> | *spring.cloud.azure.eventhub*.checkpoint-container | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name | For example, change from: @@ -1104,9 +1104,9 @@ The following table shows the property mappings from `azure-spring-cloud-starter > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |---------------------------------------------|------------------------------------------------------------| -> | *spring.cloud.azure.storage*.account | *spring.cloud.azure.storage.queue*.account-name | -> | *spring.cloud.azure.storage*.access-key | *spring.cloud.azure.storage.queue*.account-key | -> | *spring.cloud.azure.storage*.resource-group | *spring.cloud.azure.storage.queue*.resource.resource-group | +> | *spring.cloud.azure.storage*.account | *spring.cloud.azure.storage.queue*.account-name | +> | *spring.cloud.azure.storage*.access-key | *spring.cloud.azure.storage.queue*.account-key | +> | *spring.cloud.azure.storage*.resource-group | *spring.cloud.azure.storage.queue*.resource.resource-group | #### API changes @@ -1178,18 +1178,18 @@ The following table shows property mappings from `azure-spring-cloud-stream-bind > [!div class="mx-tdBreakAll"] > | Legacy properties | Modern properties | > |-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| -> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.eventhubs*.resource.resource-group | -> | *spring.cloud.azure.eventhub*.namespace | *spring.cloud.azure.eventhubs*.namespace | -> | *spring.cloud.azure.eventhub*.connection-string | *spring.cloud.azure.eventhubs*.connection-string | -> | *spring.cloud.azure.eventhub*.checkpoint-storage-account | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name | -> | *spring.cloud.azure.eventhub*.checkpoint-access-key | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key | -> | *spring.cloud.azure.eventhub*.checkpoint-container | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-batch-size | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-size | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-wait-time | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-wait-time | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-mode | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.mode | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-count | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.count | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-interval | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.interval | -> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.start-position | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.initial-partition-event-position | +> | *spring.cloud.azure*.resource-group | *spring.cloud.azure.eventhubs*.resource.resource-group | +> | *spring.cloud.azure.eventhub*.namespace | *spring.cloud.azure.eventhubs*.namespace | +> | *spring.cloud.azure.eventhub*.connection-string | *spring.cloud.azure.eventhubs*.connection-string | +> | *spring.cloud.azure.eventhub*.checkpoint-storage-account | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-name | +> | *spring.cloud.azure.eventhub*.checkpoint-access-key | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.account-key | +> | *spring.cloud.azure.eventhub*.checkpoint-container | *spring.cloud.azure.eventhubs.processor*.checkpoint-store.container-name | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-batch-size | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-size | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.max-wait-time | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.batch.max-wait-time | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-mode | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.mode | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-count | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.count | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.checkpoint-interval | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.checkpoint.interval | +> | *spring.cloud.stream.eventhub.bindings.binding-name.consumer*.start-position | *spring.cloud.stream.eventhubs.bindings.binding-name.consumer*.initial-partition-event-position | > [!NOTE] > The value type of the `start-position` configuration is also changed from an enum of `com.azure.spring.integration.core.api.StartPosition` to a `map` of `StartPositionProperties` for each partition. Thus, the key is the partition ID, and the value is of `com.azure.spring.cloud.service.eventhubs.properties.StartPositionProperties` which includes properties of offset, sequence number, enqueued date time and whether inclusive. @@ -1372,7 +1372,7 @@ The following table lists the new configuration properties of `spring-cloud-azur > [!div class="mx-tdBreakAll"] > | Modern properties | Description | > |-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| -> | *spring.cloud.stream.servicebus*.bindings.binding-name.producer.entity-type | If you use the sending function, you need to set the entity-type, which you can set to topic or queue. | +> | *spring.cloud.stream.servicebus*.bindings.binding-name.producer.entity-type | If you use the sending function, you need to set the entity-type, which you can set to topic or queue. | The following table shows the property mappings from `azure-spring-cloud-stream-binder-servicebus-*` to `spring-cloud-azure-stream-binder-servicebus`: @@ -1386,10 +1386,10 @@ The following table shows the property mappings from `azure-spring-cloud-stream- > | *spring.cloud.azure.servicebus*.retry-options.delay | *spring.cloud.azure.servicebus*.retry.exponential.base-delay or *spring.cloud.azure.servicebus*.retry.fixed.delay, should be configured depending on *spring.cloud.azure.servicebus*.retry.mode=*fixed* or *exponential* | > | *spring.cloud.azure.servicebus*.retry-options.max-delay | *spring.cloud.azure.servicebus*.retry.exponential.max-delay | > | *spring.cloud.azure.servicebus*.retry-options.try-timeout | *spring.cloud.azure.servicebus*.retry.try-timeout | -> | *spring.cloud.stream.servicebus*.queue.bindings.* | *spring.cloud.stream.servicebus.bindings*.* | +> | *spring.cloud.stream.servicebus*.queue.bindings.* | *spring.cloud.stream.servicebus.bindings*.* | > | *spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*concurrency* | *spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls | > | *spring.cloud.stream.servicebus.queue*.bindings.binding-name.consumer.*checkpoint-mode* | *spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete* | -> | *spring.cloud.stream.servicebus*.topic.bindings.* | *spring.cloud.stream.servicebus.bindings*.* | +> | *spring.cloud.stream.servicebus*.topic.bindings.* | *spring.cloud.stream.servicebus.bindings*.* | > | *spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*concurrency* | *spring.cloud.stream.servicebus*.bindings.binding-name.consumer.max-concurrent-sessions/max-concurrent-calls | > | *spring.cloud.stream.servicebus.topic*.bindings.binding-name.consumer.*checkpoint-mode* | *spring.cloud.stream.servicebus*.bindings.binding-name.consumer.*auto-complete* | diff --git a/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md b/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md index c5c63b900..c521d66dd 100644 --- a/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md +++ b/articles/java/spring-framework/spring-boot-starter-for-entra-developer-guide.md @@ -526,8 +526,8 @@ The Spring Boot Starter for Microsoft Entra ID provides the following properties |----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | spring.cloud.azure.active-directory.app-id-uri | Used by the resource server to validate the audience in the access token. The access token is valid only when the audience is equal to the `` or `` values described previously. | | spring.cloud.azure.active-directory.authorization-clients | A map that configures the resource APIs the application is going to visit. Each item corresponds to one resource API the application is going to visit. In your Spring code, each item corresponds to one `OAuth2AuthorizedClient` object. | -| `spring.cloud.azure.active-directory.authorization-clients..scopes` | The API permissions of a resource server that the application is going to acquire. | -| `spring.cloud.azure.active-directory.authorization-clients..authorization-grant-type` | The type of authorization client. Supported types are [`authorization_code`](/azure/active-directory/develop/v2-oauth2-auth-code-flow) (default type for webapp), [`on_behalf_of`](/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow) (default type for resource-server), [`client_credentials`](/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow). | +| spring.cloud.azure.active-directory.authorization-clients.``.scopes | The API permissions of a resource server that the application is going to acquire. | +| spring.cloud.azure.active-directory.authorization-clients.``.authorization-grant-type | The type of authorization client. Supported types are [`authorization_code`](/azure/active-directory/develop/v2-oauth2-auth-code-flow) (default type for webapp), [`on_behalf_of`](/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow) (default type for resource-server), [`client_credentials`](/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow). | | spring.cloud.azure.active-directory.application-type | Refer to [Application type](#application-type). | | spring.cloud.azure.active-directory.profile.environment.active-directory-endpoint | The base URI for the authorization server. The default value is `https://login.microsoftonline.com/`. | | spring.cloud.azure.active-directory.credential.client-id | The registered application ID in Microsoft Entra ID. | diff --git a/articles/java/spring-framework/spring-jms-support.md b/articles/java/spring-framework/spring-jms-support.md index fed729f07..c1b1c6034 100644 --- a/articles/java/spring-framework/spring-jms-support.md +++ b/articles/java/spring-framework/spring-jms-support.md @@ -54,7 +54,7 @@ The following table describes the configurable properties when using the Spring > | **spring.jms.servicebus**.enabled | A value that indicates whether to enable Service Bus JMS autoconfiguration. The default value is `true`. | > | **spring.jms.servicebus**.idle-timeout | The connection idle timeout duration that indicates how long the client expects Service Bus to keep a connection alive when no messages are delivered. The default value is `2m`. | > | **spring.jms.servicebus**.passwordless-enabled | Whether to enable passwordless for Azure Service Bus JMS. The default value is `false`. | -> | **spring.jms.servicebus**.pricing-tier | The Azure Service Bus Price Tier. Supported values are `premium and `standard`. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | +> | **spring.jms.servicebus**.pricing-tier | The Azure Service Bus Price Tier. Supported values are `premium` and `standard`. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus. | > | **spring.jms.servicebus**.listener.reply-pub-sub-domain | A value that indicates whether the reply destination type is a topic. Only works for the `topicJmsListenerContainerFactory` bean. | > | **spring.jms.servicebus**.listener.phase | The phase in which this container should be started and stopped. | > | **spring.jms.servicebus**.listener.reply-qos-settings | Configures the `QosSettings` to use when sending a reply. | diff --git a/articles/java/toolkit-for-eclipse/create-hello-world-web-app.md b/articles/java/toolkit-for-eclipse/create-hello-world-web-app.md index 3f83d9be2..35c064e9b 100644 --- a/articles/java/toolkit-for-eclipse/create-hello-world-web-app.md +++ b/articles/java/toolkit-for-eclipse/create-hello-world-web-app.md @@ -49,7 +49,7 @@ To ensure you have required components to work with web app projects, follow the 1. Click the **Help** menu, and then click **Install New Software**. -1. In the **Available Software** dialog, click **Manage**, and make sure the latest Eclipse version is selected (e.g. **2020-06**). +1. In the **Available Software** dialog, click **Manage**, and make sure the latest Eclipse version is selected - for example, **2020-06**. 1. Click **Apply and Close**. Expand the **Work with:** dropdown menu to show suggested sites. Select the latest Eclipse version site to query available software. diff --git a/articles/java/toolkit-for-intellij/hello-world-web-app-linux.md b/articles/java/toolkit-for-intellij/hello-world-web-app-linux.md index 7d819c25e..fafc274e4 100644 --- a/articles/java/toolkit-for-intellij/hello-world-web-app-linux.md +++ b/articles/java/toolkit-for-intellij/hello-world-web-app-linux.md @@ -56,8 +56,8 @@ The following steps walk you through the Azure sign in process in your IntelliJ 1. Expand the **Artifact Coordinates** dropdown to view all input fields and specify the following information for your new web app and click **Next**: * **Name**: The name of your web app. This will automatically fill in the web app's **ArtifactId** field. - * **GroupId**: The name of the artifact group, usually a company domain. (e.g. *com.microsoft.azure*) - * **Version**: We'll keep the default version *1.0-SNAPSHOT*. + * **GroupId**: The name of the artifact group, usually a company domain. - for example, **com.microsoft.azure**. + * **Version**: We'll keep the default version **1.0-SNAPSHOT**. 1. Customize any Maven settings or accept the defaults, and then click **Finish**.