Skip to content

Adds ansible.compatiblity_mode statement to Vagrantfiles#206

Closed
kevinbowen777 wants to merge 1 commit intogeerlingguy:masterfrom
kevinbowen777:add_compatibility_mode_statement
Closed

Adds ansible.compatiblity_mode statement to Vagrantfiles#206
kevinbowen777 wants to merge 1 commit intogeerlingguy:masterfrom
kevinbowen777:add_compatibility_mode_statement

Conversation

@kevinbowen777
Copy link

Adds the ansible.compatibility_mode = "2.0" statement to Vagrantfiles where Ansible provisioning occurs.

@geerlingguy
Copy link
Owner

So, I agree with this PR in practice, but in my hopes and dreams, I want it to not be required at all to get rid of the annoying warning you get in Vagrant's output.

Therefore, I've opened the following upstream issue and would like to leave a little time to see if this can just be resolved upstream: hashicorp/vagrant#11419

@kevinbowen777
Copy link
Author

I concur. Thanks for opening up an issue upstream. I was mainly aiming for consistency within your book's repos. Appreciate the quick response.

@geerlingguy
Copy link
Owner

@kevinbowen777 - Laziness wins the day again! It looks like 2.2.8 includes the fix for the annoying compatibility mode warning (by changing it to 'INFO' level so it doesn't display in normal output).

geerlingguy added a commit that referenced this pull request Jul 20, 2020
@geerlingguy
Copy link
Owner

See commit above — I'm just removing it from the one place it exists. Thanks for this PR though!

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