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/operator-nexus/howto-run-instance-readiness-testing.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
@@ -56,15 +56,15 @@ There are multiple dependencies expected to be available during execution. Revie
56
56
57
57
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.
58
58
59
-
> [NOTE]
59
+
> [!NOTE]
60
60
> `setup.sh` assumes a nonroot user and attempts to use `sudo`
61
61
62
62
### All in one setup
63
63
64
64
`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.
65
65
### Step-by-Step setup
66
66
67
-
> [NOTE]
67
+
> [!NOTE]
68
68
> Only use this section if you're NOT using `all-in-one.sh`
69
69
70
70
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:
99
99
./create-managed-identity.sh irt-input.yml
100
100
```
101
101
102
-
> [NOTE]
102
+
> [!NOTE]
103
103
> if `MANAGED_IDENTITY_ID` is set in the input yaml or as an environment variable the script won't create anything.
104
104
105
105
**RESULT:** This script prints a value for `MANAGED_IDENTITY_ID` and sets it to the input.yml.
@@ -138,7 +138,7 @@ SERVICE_PRINCIPAL:
138
138
./create-service-principal.sh irt-input.yml
139
139
```
140
140
141
-
> [NOTE]
141
+
> [!NOTE]
142
142
> 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.
143
143
144
144
**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:
194
194
* `SUBSCRIPTION` - The subscription where the resource group is created in.
195
195
* `LOCATION` - The location where the resource group is created in.
196
196
197
-
> [NOTE]
197
+
> [!NOTE]
198
198
> if `PUBLISH_RESULTS_TO` is set in the input yaml or as an environment variable the script skips creating a new one.
0 commit comments