-
-
Notifications
You must be signed in to change notification settings - Fork 221
feat: Upstream bastion
component
#340
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.
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
Conversation
a59b7dd
to
c94a363
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requested minor changes.
699d02a
to
71ec8a7
Compare
74911a9
to
58770c9
Compare
c7a152a
to
5d6d016
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please bump cloudposse/ec2-bastion-server/aws
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be a good idea to keep var.ssm_enabled
as part of this component instead of abstracting it to the module entirely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are still issues with this component, namely the fact that it doesn't support the bastion not associating a public IP if var.associate_public_ip_address=false
. But I will address this in a separate PR.
what
bastion
componentwhy
references
notes
To pass pre-commit hook