Use SSH bastion for Leafcloud image builds #296
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sd109
force-pushed
the
ci/leafcloud-ssh-bastion
branch
6 times, most recently
from
7910fd9 to
e059176
Compare
sd109
force-pushed
the
ci/leafcloud-ssh-bastion
branch
from
e059176 to
3dcb004
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently still WIP but can't mark as draft as I need to test the CI (which doesn't run on draft PRs).
Packer bastion config is working but Ansible provisioner is not correctly using the bastion yet. Need to do some more debugging to figure out why.