[MODULES-8438] SQLServer fact doesn't detect 2019 - Puppet Jira Server

XML

Word

Printable

Details

Type: New Feature
Status: Resolved
Priority: Normal
Resolution: Fixed
Affects Version/s: None
Fix Version/s: None
Component/s: sqlserver
Labels:
- customer-escalation

Acceptance Criteria:

Hide

Running the module should correctly detect that there
is no SQL 2017 instance installed on the host.

Running the module should correctly install SQL 2017 on the host.

Running the module should only install an instance once.

Confirm other installation conforms to previous behavior.

No additional support for 2019 features.
Code change.
Documented manual verification (add to this ticket).

Show
Running the module should correctly detect that there is no SQL 2017 instance installed on the host. Running the module should correctly install SQL 2017 on the host. Running the module should only install an instance once. Confirm other installation conforms to previous behavior. No additional support for 2019 features. Code change. Documented manual verification (add to this ticket).
Epic Link:
Windows Customer Escalations
Team:
Windows
Story Points:
1
Sprint:
Windows 2019-01-16

QA Risk Assessment:
Needs Assessment

Description

I'm working with a user of the Puppetlabs/SQLServer module. They're beginning to investigate SQLServer 2019 and find that the module doesn't detect it and attempts to re-install it on each Puppet run.

The appropriate fact(s) need to be updated to detect if SQLServer 2019 is installed on the system. (Managing it is another issue, but for another time).

This will allow them to intelligently manage state of their SQLServer instances.

Attachments

Issue Links

relates to

MODULES-6168 SQLServer fact doesn't detect 2017

Resolved

Activity

People

Assignee:: William Hurt

Reporter:: Paul Anderson

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2019/01/07 7:23 AM

Updated:: 2019/01/16 9:57 AM

Resolved:: 2019/01/16 9:57 AM