You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/spring-apps/enterprise/includes/quickstart-deploy-java-native-image-app/deploy-enterprise-plan.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ Azure Spring Apps is used to host the Spring Petclinic app. Use the following st
110
110
--build-pool-size S7
111
111
```
112
112
113
-
1. Create a *builder-native.json* file in the current directory and then add the following content:
113
+
1. Create a **builder-native.json** file in the current directory and then add the following content:
Copy file name to clipboardExpand all lines: articles/spring-apps/enterprise/includes/quickstart-deploy-restful-api-app/clean-up-resources.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Use the following steps to delete the entire resource group, including the newly
27
27
28
28
1. On the navigation menu, select **Resource groups**. Then, select the name of your resource group - for example, **myresourcegroup**.
29
29
30
-
1. On your resource group page, select **Delete**. Enter the name of your resource group in the text box to confirm deletion - for example, *myresourcegroup*. Then, select **Delete**.
30
+
1. On your resource group page, select **Delete**. Enter the name of your resource group in the text box to confirm deletion - for example, **myresourcegroup**. Then, select **Delete**.
Copy file name to clipboardExpand all lines: articles/spring-apps/enterprise/includes/quickstart-deploy-restful-api-app/deploy-restful-api-app-with-consumption-plan.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,17 +91,17 @@ Use the following steps to create a service instance:
|**Subscription**| Your subscription name. | The Azure subscription that you want to use for your server. If you have multiple subscriptions, choose the subscription in which you'd like to be billed for the resource. |
94
-
|**Resource group**|*myresourcegroup*| A new resource group name or an existing one from your subscription. |
95
-
|**Name**|*myasa*| A unique name that identifies your Azure Spring Apps service. The name must be between 4 and 32 characters long and can contain only lowercase letters, numbers, and hyphens. The first character of the service name must be a letter and the last character must be either a letter or a number. |
94
+
|**Resource group**|**myresourcegroup**| A new resource group name or an existing one from your subscription. |
95
+
|**Name**|**myasa**| A unique name that identifies your Azure Spring Apps service. The name must be between 4 and 32 characters long and can contain only lowercase letters, numbers, and hyphens. The first character of the service name must be a letter and the last character must be either a letter or a number. |
96
96
|**Plan**|**Standard consumption & dedicated (preview)**| The pricing plan determines the resources and cost associated with your instance. |
97
97
|**Region**| The region closest to your users. | The location that's closest to your users. |
98
-
|**Container Apps Environment**|*myenvironment*| The option to select which Container Apps environment instance to share the same virtual network with other services and resources. |
98
+
|**Container Apps Environment**|**myenvironment**| The option to select which Container Apps environment instance to share the same virtual network with other services and resources. |
99
99
100
100
Use the following table as a guide for the Container Apps Environment creation:
Copy file name to clipboardExpand all lines: articles/spring-apps/enterprise/includes/quickstart-deploy-restful-api-app/deploy-restful-api-app-with-enterprise-plan.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ Use the following steps to connect your service instances:
59
59
60
60
1. From the navigation menu, open **Apps**, and then select **Create App**.
61
61
62
-
1. On the **Create App** page, fill in the app name *simple-todo-api*, and then select **Java artifacts** as the deployment type.
62
+
1. On the **Create App** page, fill in the app name **simple-todo-api**, and then select **Java artifacts** as the deployment type.
63
63
64
64
1. Select **Create** to finish the app creation and then select the app to view the details.
65
65
@@ -74,7 +74,7 @@ Use the following steps to connect your service instances:
74
74
-**Service type**: **DB for PostgreSQL flexible server**
75
75
-**Connection name**: An automatically generated name is populated, which can also be modified.
:::image type="content" source="../../media/quickstart-deploy-restful-api-app/app-service-connector-authentication.png" alt-text="Screenshot of the Azure portal that shows the Authentication tab of the Create connection pane with the Connection string option highlighted." lightbox="../../media/quickstart-deploy-restful-api-app/app-service-connector-authentication.png":::
Copy file name to clipboardExpand all lines: articles/spring-apps/enterprise/includes/quickstart-deploy-restful-api-app/expose-restful-apis.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Use the following steps to expose your RESTful APIs in Microsoft Entra ID:
23
23
24
24
1. Under **Manage**, select **App registrations** > **New registration**.
25
25
26
-
1. Enter a name for your application in the **Name** field - for example, *Todo*. Users of your app might see this name, and you can change it later.
26
+
1. Enter a name for your application in the **Name** field - for example, **Todo**. Users of your app might see this name, and you can change it later.
27
27
28
28
1. For **Supported account types**, select **Accounts in any organizational directory (Any Microsoft Entra directory - Multitenant) and personal Microsoft accounts**.
29
29
@@ -37,13 +37,13 @@ Use the following steps to expose your RESTful APIs in Microsoft Entra ID:
37
37
38
38
1. Under **Manage**, select **Expose an API** > **Add a scope**, and then enter the following information:
39
39
40
-
- For **Scope name**, enter *ToDo.Read*.
40
+
- For **Scope name**, enter **ToDo.Read**.
41
41
- For **Who can consent**, select **Admins only**.
42
42
- For **Admin consent display name**, enter *Read the ToDo data*.
43
43
- For **Admin consent description**, enter *Allows authenticated users to read the ToDo data.*.
44
44
- For **State**, keep it enabled.
45
45
- Select **Add scope**.
46
46
47
-
1. Repeat the previous steps to add the other two scopes: *ToDo.Write* and *ToDo.Delete*.
47
+
1. Repeat the previous steps to add the other two scopes: **ToDo.Write** and **ToDo.Delete**.
48
48
49
49
:::image type="content" source="../../media/quickstart-deploy-restful-api-app/expose-an-api.png" alt-text="Screenshot of the Azure portal that shows the Expose an API page of a RESTful API application." lightbox="../../media/quickstart-deploy-restful-api-app/expose-an-api.png":::
Copy file name to clipboardExpand all lines: articles/spring-apps/enterprise/troubleshoot-build-exit-code.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,23 +28,23 @@ The following list describes some common exit codes:
28
28
29
29
-**20** - All buildpack groups have failed to detect.
30
30
31
-
Consider the following possible causes of an exit code of *20*:
31
+
Consider the following possible causes of an exit code of `20`:
32
32
33
33
- The builder you're using doesn't support the language your project used.
34
34
35
35
If you're using the default builder, check the language the default builder supports. For more information, see the [Supported APM types](how-to-enterprise-configure-apm-integration-and-ca-certificates.md#supported-apm-types) section of [How to configure APM integration and CA certificates](how-to-enterprise-configure-apm-integration-and-ca-certificates.md).
36
36
37
37
If you're using the custom builder, check whether your custom builder's buildpack supports the language your project used.
38
38
39
-
- You're running against the wrong path; for example, your Maven project's *pom.xml* file isn't in the root path.
39
+
- You're running against the wrong path; for example, your Maven project's **pom.xml** file isn't in the root path.
40
40
41
-
Set `BP_MAVEN_POM_FILE` to specify the location of the project's *pom.xml* file.
41
+
Set `BP_MAVEN_POM_FILE` to specify the location of the project's **pom.xml** file.
42
42
43
-
- There's something wrong with your application; for example, your *.jar* file doesn't have a */META-INF/MANIFEST.MF* file that contains a `Main-Class` entry.
43
+
- There's something wrong with your application; for example, your **.jar** file doesn't have a **/META-INF/MANIFEST.MF** file that contains a `Main-Class` entry.
44
44
45
45
-**51** - Buildpack build error.
46
46
47
-
Consider the following possible causes of an exit code of *51*:
47
+
Consider the following possible causes of an exit code of `51`:
48
48
49
49
- If Azure Spring Apps displays the error message `Build failed in stage build with reason OOMKilled` in the Azure CLI console, the build failed due to insufficient memory.
50
50
@@ -68,7 +68,7 @@ The following list describes some common exit codes:
68
68
69
69
- **62** - Failed to write image to Azure Container Registry.
70
70
71
-
Consider the following possible cause of an exit code of *62*:
71
+
Consider the following possible cause of an exit code of `62`:
72
72
73
73
- If Azure Spring Apps displays the error message `Failed to write image to the following tags` in the build log, the build failed because of a network issue.
0 commit comments