From df936ecd2aecae0368dd211106e2138b679a878d Mon Sep 17 00:00:00 2001 From: kaiqianyang Date: Mon, 23 Oct 2023 17:23:20 +0800 Subject: [PATCH 1/2] update azure-database-config messages --- .../azure/azure-database-config.windup.xml | 48 ++++++++++++------- 1 file changed, 30 insertions(+), 18 deletions(-) diff --git a/rules/rules-reviewed/azure/azure-database-config.windup.xml b/rules/rules-reviewed/azure/azure-database-config.windup.xml index 5d73a1c9..4243179a 100644 --- a/rules/rules-reviewed/azure/azure-database-config.windup.xml +++ b/rules/rules-reviewed/azure/azure-database-config.windup.xml @@ -33,18 +33,22 @@ - + - The application uses a JDBC connection string, username or password in the configuration file. - Checkout the different types of databases that are fully managed on Azure. + The application uses a JDBC connection string, username or password in the configuration file. To migrate a Java application that uses a JDBC connection string to Azure, you can follow these recommendations: + + * **Use a database that is fully managed on Azure**: Use databases such as Azure SQL, Azure Database for MySQL, or Azure Database for PostgreSQL. + + * **Connect to databases using Service Connector**: Create service connection using **Service Connector** to connect your application to Azure SQL, Azure Database for MySQL, or Azure Database for PostgreSQL. Service Connector provides a secure and easy way to connect your application to Azure services without having to manage secrets or credentials in your application code. + + * **Passwordless connections for Azure services**: Consider using passwordless connections for Azure services. You can provide an additional layer of security and convenience for accessing resources in Azure by eliminating the need for passwords. This way you can reduce the risk of password-related vulnerabilities, such as weak passwords or password theft. - - - + + jdbc @@ -62,15 +66,19 @@ - + - The application uses a MongoDB connection string. - Checkout the different types of databases that are fully managed on Azure. + The application uses a MongoDB connection string. To migrate a Java application that uses a MongoDB connection string to Azure, you can follow these recommendations: + + * Use a managed **Azure Cosmos DB for MongoDB**: Create a managed Cosmos DB for MongoDB database in Azure and choose the appropriate pricing tier based on your application's requirements for performance, storage, and availability. + + * **Connect to Azure Cosmos DB for MongoDB using Service Connector**: Create service connection using **Service Connector** to connect your application to Azure Cosmos DB for MongoDB. Service Connector provides a secure and easy way to connect your application to Azure services without having to manage secrets or credentials in your application code. + + * **Passwordless connections for Azure services**: Consider using passwordless connections for Azure services. You can provide an additional layer of security and convenience for accessing resources in Azure by eliminating the need for passwords. This way you can reduce the risk of password-related vulnerabilities, such as weak passwords or password theft. - - - + + mongodb @@ -90,15 +98,19 @@ - + - The application uses a R2DBC connection string, username or password in the configuration file. - Checkout the different types of databases that are fully managed on Azure. + The application uses a R2DBC connection string, username or password in the configuration file. To migrate a Java application that uses a R2DBC connection string to Azure, you can follow these recommendations: + + * **Use a database that is fully managed on Azure**: Use databases such as Azure SQL, Azure Database for MySQL, or Azure Database for PostgreSQL. + + * **Connect to databases using Service Connector**: Create service connection using **Service Connector** to connect your application to Azure SQL, Azure Database for MySQL, or Azure Database for PostgreSQL. Service Connector provides a secure and easy way to connect your application to Azure services without having to manage secrets or credentials in your application code. + + * **Passwordless connections for Azure services**: Consider using passwordless connections for Azure services. You can provide an additional layer of security and convenience for accessing resources in Azure by eliminating the need for passwords. This way you can reduce the risk of password-related vulnerabilities, such as weak passwords or password theft. - - - + + From aaa88960e6d20c50bd0c327133ee417607e9f839 Mon Sep 17 00:00:00 2001 From: kaiqianyang Date: Mon, 23 Oct 2023 17:25:34 +0800 Subject: [PATCH 2/2] remove localization link --- rules/rules-reviewed/azure/azure-database-config.windup.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rules/rules-reviewed/azure/azure-database-config.windup.xml b/rules/rules-reviewed/azure/azure-database-config.windup.xml index 4243179a..b8e716fc 100644 --- a/rules/rules-reviewed/azure/azure-database-config.windup.xml +++ b/rules/rules-reviewed/azure/azure-database-config.windup.xml @@ -47,7 +47,7 @@ - + jdbc @@ -77,7 +77,7 @@ * **Passwordless connections for Azure services**: Consider using passwordless connections for Azure services. You can provide an additional layer of security and convenience for accessing resources in Azure by eliminating the need for passwords. This way you can reduce the risk of password-related vulnerabilities, such as weak passwords or password theft. - + @@ -109,7 +109,7 @@ * **Passwordless connections for Azure services**: Consider using passwordless connections for Azure services. You can provide an additional layer of security and convenience for accessing resources in Azure by eliminating the need for passwords. This way you can reduce the risk of password-related vulnerabilities, such as weak passwords or password theft. - +