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.

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

[Feature] Add support for vm.name for virtualbox #365

Closed
gena01 opened this issue Aug 6, 2018 · 0 comments
Closed

[Feature] Add support for vm.name for virtualbox #365

gena01 opened this issue Aug 6, 2018 · 0 comments
Assignees

Comments

@gena01
Copy link

gena01 commented Aug 6, 2018

Please add support for "vm.name=" syntax. See documentation here: https://www.vagrantup.com/docs/virtualbox/configuration.html#virtual-machine-name

This came up after I upgraded from chefdk1.x to the latest stable 3.1.0 release which includes the new ktichen-vagrant. One of the things I noticed was that this commit: 1f58fce
was made to fix a path restriction.

The side-effect is that in VirtualBox GUI you can not tell which cookbook the VM is built-against. Adding something like:
vm.name= "kitchen-#{File.basename(config[:kitchen_root])}-#{instance.name}"
would help and restore the naming in VirtualBox GUI and hopefully address both issues.

@cheeseplus cheeseplus self-assigned this Aug 6, 2018
cheeseplus pushed a commit that referenced this issue Aug 7, 2018
Signed-off-by: Seth Thomas <sthomas@chef.io>
cheeseplus pushed a commit that referenced this issue Aug 7, 2018
Fix #365 - add name for virtualbox instances
stissot pushed a commit to Ecodev/kitchen-vagrant that referenced this issue Dec 11, 2018
Signed-off-by: Seth Thomas <sthomas@chef.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants