Skip to content

Commit 1351bd6

Browse files
author
Robel Herarso
committed
add exclamation for all notes
1 parent c6c3b22 commit 1351bd6

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/operator-nexus/howto-run-instance-readiness-testing.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -56,15 +56,15 @@ There are multiple dependencies expected to be available during execution. Revie
5656

5757
The `setup.sh` script is provided to aid with installing the listed dependencies. It installs any dependencies that aren't available in PATH. It doesn't upgrade any dependencies that don't meet the minimum required versions.
5858

59-
> [NOTE]
59+
> [!NOTE]
6060
> `setup.sh` assumes a nonroot user and attempts to use `sudo`
6161
6262
### All in one setup
6363

6464
`all-in-one-setup.sh` is provided to create all of the Azure resources required to run IRT. This process includes creating a managed identity, a service principal, a security group, isolation domains, and a storage account to archive the test results. These resources can be created during the all in one script, or they can be created step by step per the instructions in this document. Each of the script, individually and via the all in one script, writes updates to your `irt-input.yml` file with the key value pairs needed to utilize the resources you created. Review the `irt-input.example.yml` file for the required inputs needed for one or more of the scripts, regardless of the methodology you pursue. All of the scripts are idempotent, and also allow you to use existing resources if desired.
6565
### Step-by-Step setup
6666

67-
> [NOTE]
67+
> [!NOTE]
6868
> Only use this section if you're NOT using `all-in-one.sh`
6969
7070
If your workflow is incompatible with `all-in-one.sh`, each resource needed for IRT can be created manually with each supplemental script. Like `all-in-one.sh`, running these scripts writes key/value pairs to your `irt-input.yml` for you to use during your run. These four scripts make up the `all-in-one.sh`.
@@ -99,7 +99,7 @@ MANAGED_IDENTITY:
9999
./create-managed-identity.sh irt-input.yml
100100
```
101101

102-
> [NOTE]
102+
> [!NOTE]
103103
> if `MANAGED_IDENTITY_ID` is set in the input yaml or as an environment variable the script won't create anything.
104104

105105
**RESULT:** This script prints a value for `MANAGED_IDENTITY_ID` and sets it to the input.yml.
@@ -138,7 +138,7 @@ SERVICE_PRINCIPAL:
138138
./create-service-principal.sh irt-input.yml
139139
```
140140

141-
> [NOTE]
141+
> [!NOTE]
142142
> if all `SP_ID`,`SP_PASSWORD`,`SP_TENANT_ID`,`AAD_GROUP_ID` are set in the yaml or as an environment variable the script skips creating them.
143143

144144
**RESULT:** This script prints values for `AAD_GROUP_ID`, `SP_ID`, `SP_PASSWORD`, and `SP_TENANT` and sets the values back to the input yaml.
@@ -194,7 +194,7 @@ ARCHIVE_STORAGE:
194194
* `SUBSCRIPTION` - The subscription where the resource group is created in.
195195
* `LOCATION` - The location where the resource group is created in.
196196

197-
> [NOTE]
197+
> [!NOTE]
198198
> if `PUBLISH_RESULTS_TO` is set in the input yaml or as an environment variable the script skips creating a new one.
199199

200200
```bash

0 commit comments

Comments
 (0)