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

provisioner/chef: add an option to specifically specify the target OS #2483

Merged
merged 1 commit into from
Jun 25, 2015
Merged

provisioner/chef: add an option to specifically specify the target OS #2483

merged 1 commit into from
Jun 25, 2015

Conversation

svanharmelen
Copy link
Contributor

Before this option (os_type) the provisioner would use the connection type to determine the targeted OS. When not supplying a value for os_type, it will fall back to the old behaviour, so this is fully BC.

Before this option (`os_type`) the provisioner would use the connection
type to determine the targeted OS. When not supplying a value for
`os_type`, it will fall back to the old behaviour, so this is full BC.
@svanharmelen
Copy link
Contributor Author

This fixes #2175

@phinze
Copy link
Contributor

phinze commented Jun 25, 2015

LGTM!

@svanharmelen
Copy link
Contributor Author

Thx! I'll merge it right away as I have another one lined up build on top of this one 😉

svanharmelen pushed a commit that referenced this pull request Jun 25, 2015
provisioner/chef: add an option to specifically specify the target OS
@svanharmelen svanharmelen merged commit 4c66df0 into hashicorp:master Jun 25, 2015
@svanharmelen svanharmelen deleted the f-provisioner-chef-ostype branch June 25, 2015 14:43
@ghost
Copy link

ghost commented May 2, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants