Closed rylarson closed 8 years ago
It looks like RuboCop is failing in CI, but it was already failing. Do I need to add exclusions or fix these RuboCop errors before this can be merged?
Sorry for all of the commits, the tests were in a pretty broken state when I got to them.
The commit message has details, but we have to make sure that our mock takes a little while to "connect" because Vagrant has some really terrible multithreaded code here: https://github.com/mitchellh/vagrant/blob/master/lib/vagrant/action/builtin/wait_for_communicator.rb#L16
Is there anything else I need to do to get this merged?
I merged out from master so there are no conflicts again
Looks like my merging another pull request broke rubocop on this one again. Earlier I disabled some metrics cops so that pull requests would stop breaking from making a module or class one line longer, but I mistakenly made that change in .rubocop_todo.yml
instead of .rubocop.yml
. I'll make the fix in .rubocop.yml
, but then you may have another merge conflict...
After adding vsphere.notes = 'note string'
to my Vagrantfile
, I just got the same NoPermission
error as on #174.
Thanks!
@michael-brandt-cu
As far as the permissions issue goes, can you make sure that you have the Reconfigure privilege: VirtualMachine.Config.Rename
permission?
Ryan
== DETAILS
notes
notes
is set, the value ofnotes
is set as the annotation on theVirtualMahineConfigSpec
Notes:
in the Annotations field== TESTING
rake spec
all passesrake rubocop
doesn't have any more errors than it did before :)