-
Notifications
You must be signed in to change notification settings - Fork 189
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
c.vm.box configuration incorrectly set for bento/hardenedbsd-11 in generated Vagrantfile #349
Labels
Comments
kitchen-vagrant will need to be updated to "know" about any new distros and then this will go away. |
Seth Thomas:
kitchen-vagrant will need to be updated to "know" about any new distros and then this will go away.
is the line I quoted above the correct (and only) place to add the new platforms?
If so I can submit a patch
|
Two places need the change: the code itself that needs updating the unit test (which you've found)
Both need to be updated for this to work but it should be an easy PR. |
cheeseplus
pushed a commit
that referenced
this issue
Apr 23, 2018
Signed-off-by: Seth Thomas <[email protected]>
cheeseplus
pushed a commit
that referenced
this issue
Apr 24, 2018
Fixing #349 - allow bento/hardenedbsd
stissot
pushed a commit
to Ecodev/kitchen-vagrant
that referenced
this issue
Dec 11, 2018
Signed-off-by: Seth Thomas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
kitchen-vagrant creates the following box line in the Vagrant file when using "- name: hardenedbsd-11":
but it should be:
The same problem probably occurs once we add OpenBSD to bento.
kitchen-vagrant/spec/kitchen/driver/vagrant_spec.rb
Line 164 in bbb36bc
REF:
nusenu/ansible-relayor/issues/155
The text was updated successfully, but these errors were encountered: