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

Jump to bottom

Provide a way to optionally deploy Bastion host and jumpboxes in the Hub network #189

Closed
glennmusa opened this issue Apr 29, 2021 · 0 comments · Fixed by #217
Closed

Provide a way to optionally deploy Bastion host and jumpboxes in the Hub network #189

glennmusa opened this issue Apr 29, 2021 · 0 comments · Fixed by #217
Assignees
@glennmusa
Labels
core New feature or request

Comments

@glennmusa
Copy link
Contributor

Benefit/Result/Outcome
If I don't want to use bastion, I shouldn't have to.

Description
Provide a mechanism from deployment to optionally deploy Bastion host and its jumpboxes, defaulting to the behavior of deploying Bastion and its jumpboxes

Acceptance Criteria

  • The terraform configuration takes some boolean that decides whether or not to deploy Bastion resources and jumpbox resources
  • The deployment scripts takes some boolean that decides whether or not to deploy Bastion resources and jumpbox resources
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@glennmusa glennmusa

Labels
core New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add --no-bastion to allow users to opt-out of Bastion host and Jumpbox creation Azure/missionlz
2 participants
@glennmusa @brooke-hamilton