Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add flags to deployment script for T3 deployment. #245

Merged
merged 4 commits into from
Jun 10, 2021
Merged

Add flags to deployment script for T3 deployment. #245

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4134454
Flag patch.
Jun 8, 2021
9916ec5
Spelling Fix.
Jun 8, 2021
a8a9bff
Merge branch 'main' into bree/t3deployflagfix
Breanna-Stryker Jun 8, 2021
45a6762
Update deploy.sh
Breanna-Stryker Jun 8, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/docs/workload-deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
<!-- markdownlint-enable MD028 -->

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
Expand Down
4 changes: 4 additions & 0 deletions src/scripts/deploy.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
}
Expand Down Expand Up @@ -211,6 +212,9 @@ while [ $# -gt 0 ] ; do
-2 | --tier2-sub-id)
shift
subs_args+=("-2 ${1}") ;;
-3 | --tier3-sub-id)
Breanna-Stryker marked this conversation as resolved.
Show resolved Hide resolved
shift
subs_args+=("-3 ${1}") ;;
-h | --help)
show_help
exit 0 ;;
Expand Down