Skip to content
This repository was archived by the owner on Dec 5, 2022. It is now read-only.

Use provisioner type attribute - #134

Merged
fgrehm merged 1 commit into
fgrehm:masterfrom
Yserz:vagrant_1-7-1_fix
Jan 15, 2015
Merged

Use provisioner type attribute#134
fgrehm merged 1 commit into
fgrehm:masterfrom
Yserz:vagrant_1-7-1_fix

Conversation

@Yserz

@Yserz Yserz commented Dec 22, 2014

Copy link
Copy Markdown
Contributor

Vagrant changed the provisioner name attribute to type in version 1.7.1.

fixes #133

Vagrant changed the provisioner name attribute to type in version 1.7.1.
@jkulak

jkulak commented Jan 12, 2015

Copy link
Copy Markdown

Would be great to see that merged!

@fgrehm
fgrehm merged commit 15b0039 into fgrehm:master Jan 15, 2015
@fgrehm

fgrehm commented Jan 15, 2015

Copy link
Copy Markdown
Owner

Thanks and sorry it took so long! The 1.2.0 version of the plugin will come out with this in a few ;-)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@fgrehm @Yserz that might be a bit too optimistic and works only if the provisioner name is not set. However, note that you can have named provisioners in which case the p.name might be anything:
https://docs.vagrantup.com/v2/provisioning/basic_usage.html

Here's how I solved it in one of my vagrant plugins:
tknerr/vagrant-toplevel-cookbooks@ae188ee

Or @sethvargo here:
https://github.com/berkshelf/vagrant-berkshelf/blob/cd5ee78f28ee9f6bec1b72fcdbcb042b0155aa04/lib/vagrant-berkshelf/helpers.rb#L69-L86

/cc @cassianoleal

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cachier does not resolve provisioners with Vagrant 1.7.1

4 participants