From 4134454a461d517441590f9acdf26398faa9fe6c Mon Sep 17 00:00:00 2001 From: Bree Stryker Date: Tue, 8 Jun 2021 11:17:20 -0400 Subject: [PATCH 1/3] Flag patch. --- src/scripts/deploy.sh | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/scripts/deploy.sh b/src/scripts/deploy.sh index 2dabe0926..f10f89376 100755 --- a/src/scripts/deploy.sh +++ b/src/scripts/deploy.sh @@ -188,6 +188,9 @@ while [ $# -gt 0 ] ; do -2 | --tier2-sub-id) shift subs_args+=("-2 ${1}") ;; + -3 | --tier3-sub-id) + shift + subs_args+=("-3 ${1}") ;; -h | --help) show_help exit 0 ;; From 9916ec585ba0e9a81ce4b3e99c597d2ee0d28cae Mon Sep 17 00:00:00 2001 From: Bree Stryker Date: Tue, 8 Jun 2021 11:24:10 -0400 Subject: [PATCH 2/3] Spelling Fix. --- src/docs/workload-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/workload-deployment.md b/src/docs/workload-deployment.md index 7619f2e5b..7201da0d7 100644 --- a/src/docs/workload-deployment.md +++ b/src/docs/workload-deployment.md @@ -36,7 +36,7 @@ A production usage of tier 3 workloads will require a more advanced setup than a > **NOTE** Like the other Mission LZ tiers, each tier 3 workload can be deployed into its own subscription or they can be deployed into a single subscription. For production deployments we recommend that each tier 3 is deployed into its own subscription to simplify managing security and access. -1. First, moidfy the MLZ Configuration file `mlz.config` file using the `mlz.config.sample` as a template, this file should be a copy of the file used to deploy MLZ. You will need to modify the following to include the actual subscription number: +1. First, modify the MLZ Configuration file `mlz.config` file using the `mlz.config.sample` as a template, this file should be a copy of the file used to deploy MLZ. You will need to modify the following to include the actual subscription number: ```plaintext mlz_tier3_subid="{MLZ_TIER3_SUBID}" # Optional if not currently deploying a tier 3 From 45a6762bd52f0beddaf3051f9ac6803d8d0451cf Mon Sep 17 00:00:00 2001 From: Breanna-Stryker <74314422+Breanna-Stryker@users.noreply.github.com> Date: Tue, 8 Jun 2021 14:17:40 -0400 Subject: [PATCH 3/3] Update deploy.sh Add tier 3 help string. --- src/scripts/deploy.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/src/scripts/deploy.sh b/src/scripts/deploy.sh index 2a12c1bbf..33f92a700 100755 --- a/src/scripts/deploy.sh +++ b/src/scripts/deploy.sh @@ -29,6 +29,7 @@ show_help() { print_formatted "--tier0-sub-id" "-0" "[OPTIONAL] subscription ID for tier 0 network and resources (defaults to the value provided for -s --subscription-id)" print_formatted "--tier1-sub-id" "-1" "[OPTIONAL] subscription ID for tier 1 network and resources (defaults to the value provided for -s --subscription-id)" print_formatted "--tier2-sub-id" "-2" "[OPTIONAL] subscription ID for tier 2 network and resources (defaults to the value provided for -s --subscription-id)" + print_formatted "--tier3-sub-id" "-3" "[OPTIONAL] subscription ID for tier 3 network and resources (defaults to the value provided for -s --subscription-id), input is used in conjunction with deploy_t3.sh" print_formatted "--no-bastion" "" "[OPTIONAL] when present, do not create a Bastion Host and Jumpbox VM" print_formatted "--help" "-h" "Print this message" }