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

Fix feature variable name in template config file #114

Closed
wants to merge 1 commit into from

Conversation

lbn-chef-team
Copy link
Contributor

@lbn-chef-team lbn-chef-team commented Jan 8, 2018

replace "feature" variable name with "feature_list" in some case in _ConfigurationFile.ini.erb file. This syntax error impede the cookbook to run install of 2016 or 2017 versions of MSSQL Server with the following error: undefined method `include?' for nil:NilClass.

Description

Fix this error: FATAL: Chef::Mixin::Template::TemplateError: undefined method `include?' for nil:NilClass
Template Context:

on line #330
328:
329: <% if @Version == '2016' %>
330: <% if @feature.include?('ADVANCEDANALYTICS' || 'SQL_SHARED_MR') %>
331: IACCEPTROPENLICENSETERMS=<%= @accept_eula %>
332:

System Info:

chef_version=13.0.118
platform=windows
platform_version=6.3.9600
ruby=ruby 2.4.1p111 (2017-03-22 revision 58053) [x64-mingw32]

Issues Resolved

[List any existing issues this PR resolves]

Check List

replace "feature" variable name with "feature_list" in some case in _ConfigurationFile.ini.erb file. This syntax error impede the cookbook to run install of 2016 or 2017 versions of MSSQL Server with the following error:  undefined method `include?' for nil:NilClass.
@TheLunaticScripter
Copy link
Contributor

TheLunaticScripter commented Jan 8, 2018

@lbn-chef-team Thank you for submitting this PR but as a requirement of contributing to the repo we require your PR to be signed. If you could take care of that it would be greatly appreciated. Thank you.

@lbn-chef-team
Copy link
Contributor Author

yes! sorry for that, i'll take care henceforth.
you can delete this PR due to the existence of #117
that is the same fix.

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