optionally deploy Azure Bastion Host from the base deployment #406
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change introduces the
examples/remoteAccess
module into the base deployment, allowing a user to deploy Azure Bastion Host and the jumpbox(es) by specifyingdeployRemoteAccess=true
and a value forlinuxVmAdminPasswordOrKey
at deployment time.To demo this (it's easiest to use the .devcontainer to generate a password with
openssl
) try:If a user attempts to set
deployRemoteAccess=true
but forgets to supply a password like this:template validation will helpfully fail:
Issue reference
The issue this PR will close #361
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
[ ] BASH scripts have been validated usingshellcheck
.vscode/extensions.json
.)