Skip to content

(MODULES-6168) Detect SQL 2017 #251

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

Conversation

RandomNoun7
Copy link
Contributor

This change updates the features.rb file to ensure that it is checking for the registry keys for SQL 2017.

This change updates the features.rb file to ensure that it is checking for the registry keys for SQL 2017.
Copy link
Contributor

@michaeltlombardi michaeltlombardi left a comment

Choose a reason for hiding this comment

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

This is off to a good start, but I think we'll need to make sure we add handling to testing for 2017 before we pull in (otherwise our only validation is manual).

@RandomNoun7
Copy link
Contributor Author

Manual verification of changes to be completed.

@RandomNoun7
Copy link
Contributor Author

I manually verified these changes by running puppet manifests that install SQL 2017 instances both alone and alongside down version instances.

The module will also manage 2017 instances and existing features (no new features added for 2017), without incorrectly managing the other instances' features.

@jpogran jpogran merged commit 66bea53 into puppetlabs:master Dec 6, 2017
@RandomNoun7 RandomNoun7 deleted the tickets/master/MODULES-6168-detect-sql-2017 branch February 28, 2018 16:15
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.

3 participants