-
Notifications
You must be signed in to change notification settings - Fork 87
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
Update component image versions to latest #108
Conversation
variable "use_ssh_agent" { | ||
type = bool | ||
description = "Use ssh agent to connect to provisioner machine" | ||
default = false | ||
} | ||
|
||
variable "ssh_private_key" { | ||
type = string | ||
description = "ssh private key file to use" | ||
default = "~/.ssh/id_rsa" | ||
} |
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.
Previously if a user had a password protected ssh key, provisioning would fail.
This allows users to either override the private key file used, or choose to use an ssh agent to handle authentication.
config.vm.provider :libvirt do |libvirt| | ||
libvirt.qemu_use_session = false | ||
end | ||
|
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.
Previously, if a user tries to stand up the vagrant environment in libvirt it would fail because the default for using user sessions does not allow the creation of a bridge device, which is needed by our networking configuration.
Update component image versions to latest
Description
Updates tink, boots, and hegel images to the latest published images (as of Oct 1, 2021)
Why is this needed
Prepare sandbox for an updated release
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
No impact to existing users as far as I was able to tell through my manual testing described above.