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

Support Windows VM's #29

Closed
wants to merge 1 commit into from
Closed

Support Windows VM's #29

wants to merge 1 commit into from

Conversation

ghoneycutt
Copy link
Owner

No description provided.

"box_download_checksum": "123456781038992207555513504e37258c29e2e9",
"box_download_checksum_type": "sha1",
"update_packages": "false",
"shutdown": "false"
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

update_packages and shutdown have to be string "false" instead of boolean false to get this to work.

Added the following to lib/rzo/app/templates/Vagrantfile.erb to aid in debugging and found that these two options were always showing as true, even if set to false here. This is odd as other options from defaults such as box work as expected.

shutdown = x<%= nc['shutdown'] %>x
update_packages = x<%= nc['update_packages'] %>x

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The false becoming true issue appears to be a "feature" or some quirk with deep_merge gem. danielsdeleo/deep_merge#23. I think the summary is that deep_merge handles values of different classes in a way that isn't entirely intuitive and true is a different class from false.

I've not yet found a way to force a false option to override the true default.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it work if we convert booleans to strings and then back to booleans after the merge?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so but haven't tested that approach yet. The last comment on the issue I linked seems to indicate that's a valid workaround. I'll test that out and see how viable an option that is.

@ghoneycutt ghoneycutt closed this Oct 13, 2018
@ghoneycutt ghoneycutt deleted the windows branch October 13, 2018 14:08
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

Successfully merging this pull request may close these issues.

2 participants