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

Upgrade to Vagrant 2 for `salt_call_args` #729

Merged
merged 1 commit into from Oct 13, 2017

Conversation

@aneeshusa
Copy link
Member

aneeshusa commented Oct 4, 2017

Vagrant 2.0.0 adds support for a new salt_call_args option.
We use this option to specify some additional arguments for Vagrant.

Previously, we used a hack to pass these options via the minion_id
parameter, but that hack stopped working as of Vagrant 1.8.3


This change is Reviewable

Vagrant 2.0.0 adds support for a new `salt_call_args` option.
We use this option to specify some additional arguments for Vagrant.

Previously, we used a hack to pass these options via the `minion_id`
parameter, but that hack stopped working as of Vagrant 1.8.3
@larsbergstrom
Copy link
Contributor

larsbergstrom commented Oct 12, 2017

@bors-servo
Copy link
Contributor

bors-servo commented Oct 12, 2017

📌 Commit 6f199e9 has been approved by larsbergstrom

@bors-servo
Copy link
Contributor

bors-servo commented Oct 12, 2017

Testing commit 6f199e9 with merge bb37763...

bors-servo added a commit that referenced this pull request Oct 12, 2017
Upgrade to Vagrant 2 for `salt_call_args`

Vagrant 2.0.0 adds support for a new `salt_call_args` option.
We use this option to specify some additional arguments for Vagrant.

Previously, we used a hack to pass these options via the `minion_id`
parameter, but that hack stopped working as of Vagrant 1.8.3

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/729)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Oct 12, 2017

💔 Test failed - status-travis

@aneeshusa
Copy link
Member Author

aneeshusa commented Oct 13, 2017

@bors-servo retry

  • repo.saltstack.com flakiness
@bors-servo
Copy link
Contributor

bors-servo commented Oct 13, 2017

Testing commit 6f199e9 with merge e290e64...

bors-servo added a commit that referenced this pull request Oct 13, 2017
Upgrade to Vagrant 2 for `salt_call_args`

Vagrant 2.0.0 adds support for a new `salt_call_args` option.
We use this option to specify some additional arguments for Vagrant.

Previously, we used a hack to pass these options via the `minion_id`
parameter, but that hack stopped working as of Vagrant 1.8.3

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/729)
<!-- Reviewable:end -->
@bors-servo
Copy link
Contributor

bors-servo commented Oct 13, 2017

💔 Test failed - status-travis

@bors-servo
Copy link
Contributor

bors-servo commented Oct 13, 2017

☀️ Test successful - status-travis
Approved by: larsbergstrom
Pushing e290e64 to master...

@bors-servo bors-servo merged commit 6f199e9 into servo:master Oct 13, 2017
1 of 2 checks passed
1 of 2 checks passed
continuous-integration/travis-ci/pr The Travis CI build failed
Details
homu Test successful
Details
@aneeshusa
Copy link
Member Author

aneeshusa commented Oct 18, 2017

This doesn't need to be deployed in any way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.