Skip to content

Commit ee14290

Browse files
Merge pull request #270997 from KarlErickson/karler-fix
fix numbering and indentation
2 parents ccb3c79 + f489d5b commit ee14290

File tree

1 file changed

+18
-21
lines changed

1 file changed

+18
-21
lines changed

articles/aks/howto-deploy-java-liberty-app.md

Lines changed: 18 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -59,21 +59,19 @@ The following steps guide you to create a Liberty runtime on AKS. After completi
5959
1. Create a new resource group. Because resource groups must be unique within a subscription, pick a unique name. An easy way to have unique names is to use a combination of your initials, today's date, and some identifier. For example, `ejb0913-java-liberty-project-rg`.
6060
1. Select *East US* as **Region**.
6161

62-
Create environment variables in your shell for the resource group name for the cluster.
63-
64-
### [Bash](#tab/in-bash)
65-
66-
```bash
67-
export RESOURCE_GROUP_NAME=<your-resource-group-name>
68-
```
69-
70-
### [PowerShell](#tab/in-powershell)
71-
72-
```powershell
73-
$Env:RESOURCE_GROUP_NAME="<your-resource-group-name>"
74-
```
75-
76-
---
62+
1. Create environment variables in your shell for the resource group name for the cluster.
63+
64+
### [Bash](#tab/in-bash)
65+
66+
```bash
67+
export RESOURCE_GROUP_NAME=<your-resource-group-name>
68+
```
69+
70+
### [PowerShell](#tab/in-powershell)
71+
72+
```powershell
73+
$Env:RESOURCE_GROUP_NAME="<your-resource-group-name>"
74+
```
7775

7876
1. Select **Next**, enter the **AKS** pane. This pane allows you to select an existing AKS cluster and Azure Container Registry (ACR), instead of causing the deployment to create a new one, if desired. This capability enables you to use the sidecar pattern, as shown in the [Azure architecture center](/azure/architecture/patterns/sidecar). You can also adjust the settings for the size and number of the virtual machines in the AKS node pool. For our purposes, just keep all the defaults on this pane.
7977

@@ -118,12 +116,12 @@ If you navigated away from the **Deployment is in progress** page, the following
118116
119117
---
120118
121-
These values are used later in this article. Note that several other useful commands are listed in the outputs.
119+
These values are used later in this article. Note that several other useful commands are listed in the outputs.
122120
123-
> [!NOTE]
124-
> You may notice a similar output named **appDeploymentYaml**. The difference between output *appDeploymentTemplateYaml* and *appDeploymentYaml* is:
125-
> * *appDeploymentTemplateYaml* is populated if and only if the deployment **does not include** an application.
126-
> * *appDeploymentYaml* is populated if and only if the deployment **does include** an application.
121+
> [!NOTE]
122+
> You may notice a similar output named **appDeploymentYaml**. The difference between output *appDeploymentTemplateYaml* and *appDeploymentYaml* is:
123+
> * *appDeploymentTemplateYaml* is populated if and only if the deployment **does not include** an application.
124+
> * *appDeploymentYaml* is populated if and only if the deployment **does include** an application.
127125
128126
## Create an Azure SQL Database
129127
@@ -213,7 +211,6 @@ Now that you gathered the necessary properties, you can build the application. T
213211
214212
#### [Bash](#tab/in-bash)
215213
216-
217214
```bash
218215
cd $BASE_DIR/java-app
219216
# The following variables are used for deployment file generation into target.

0 commit comments

Comments
 (0)