deploy from the command line using a single script and argument

[glennmusa]

Description

This change updates terraform variables in src/core to use well-known defaults and introduces two new scripts that make it easier to deploy an instance of MissionLZ and clean-up afterwards. This change also fixes #100 and allows for deployments into other clouds.

TL;DR: an end user can now deploy MissionLZ with just these three commands (given that they are using the .devcontainer or have Azure CLI and Terraform CLI installed):

az login
git clone https://github.com/Azure/missionlz.git
src/deploy.sh -s {my_subscription_id}

and when the deployment is complete, they can run this to remove all resources and clean it all up:

src/clean.sh -z {mlz_env_name}

See the docs for the full argument list and how to deploy into another cloud.

1. deploy.sh

   • creates an MLZ configuration file using inputs or defaults
   • creates a global terraform variables .tfvars file using inputs or defaults
   • calls src/build/apply.tf with this generated MLZ configuration and generated terraform .tfvars

2. clean.sh

   • accepts an MLZ environment name as input and tries to source the generated MLZ configuration and terraform variables (future work could be done to regenerate these files if they are not found)
   • calls src/build/destroy.tf if the generated configuration and tfvars are found
   • removes all MLZ configuration resources (rgs, storage accounts)
   • deletes the MLZ service principal associated with that deployment

Issue reference

The issue this PR will close: #100, #146

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles or validates correctly
• BASH scripts have been validated using shellcheck
• All tests pass (manual and automated)
• The documentation is updated to cover any new or changed features
• Markdown files have been linted using the recommended linter. (See .vscode/extensions.json.)
• Relevant issues are linked to this PR