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

SqlRS: Does this resource support Microsoft SQL Server 2017 Reporting Services? #864

Closed
johlju opened this issue Oct 13, 2017 · 5 comments · Fixed by #1261
Closed

SqlRS: Does this resource support Microsoft SQL Server 2017 Reporting Services? #864

johlju opened this issue Oct 13, 2017 · 5 comments · Fixed by #1261
Assignees
Labels
enhancement The issue is an enhancement request.

Comments

@johlju
Copy link
Member

johlju commented Oct 13, 2017

Details of the scenario you tried and the problem that is occurring:
In SQL Server 2017 Reporting Services are no longer a part of SQL Server, but a separate install Microsoft SQL Server 2017 Reporting Services.

Does this, and should this, resource support Microsoft SQL Server 2017 Reporting Services?

The DSC configuration that is using the resource (as detailed as possible):
n/a

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Microsoft SQL Server 2017 Reporting Services

What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

@johlju johlju added the discussion The issue is a discussion. label Oct 13, 2017
@johlju johlju changed the title xSQLServerRSConfig: Does this resource support Microsoft SQL Server 2017 Reporting Services? SqlRS: Does this resource support Microsoft SQL Server 2017 Reporting Services? Dec 24, 2017
@stale
Copy link

stale bot commented Jun 6, 2018

This issue has been automatically marked as needs more information because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is label with any of the work labels (e.g bug, enhancement, documentation, or tests) the issue will not auto-close.

@stale stale bot added the needs more information The issue needs more information from the author or the community. label Jun 6, 2018
@stale
Copy link

stale bot commented Jul 6, 2018

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

@stale stale bot added the stale The issue or pull request was marked as stale because there hasn't been activity from the community. label Jul 6, 2018
@johlju
Copy link
Member Author

johlju commented Jul 6, 2018

I suggest adding a new resource SqlRSSetup that downloads (either from URL, UNC or file) and installs RS, for the other resource to be able to configure it.

Labeling this as resource proposal, and help wanted so that anyone in the community can run with this.

@stale stale bot removed the stale The issue or pull request was marked as stale because there hasn't been activity from the community. label Jul 6, 2018
@johlju johlju added help wanted The issue is up for grabs for anyone in the community. resource proposal The issue is proposing a new resource in the resource module. and removed discussion The issue is a discussion. needs more information The issue needs more information from the author or the community. labels Jul 6, 2018
@bozho
Copy link
Contributor

bozho commented Dec 18, 2018

Only slightly related: modifying SqlRs resource to support configuring installed SSRS 2017 instance seems to involve only three changes:

  • related SQL Server version Registry key for SSRS is on a different path
  • the name of the Windows service is different
  • the name of the SSRS Windows account is different

I have a patch for this, I'm happy to submit a pull request under different issue.

Also, apologies for letting several of my suggestions and questions go stale, I'm hoping I'll have more time in 2019 to work on DSC stuff :)

@johlju
Copy link
Member Author

johlju commented Dec 19, 2018

@bozho Please send in a PR for the proposed change, and please reference this issue.

There is already another issue #865 for creating a new resource SqlRSSetup. Relabeling this issue to enhancement.

@johlju johlju added enhancement The issue is an enhancement request. and removed resource proposal The issue is proposing a new resource in the resource module. labels Dec 19, 2018
bozho added a commit to bozho/SqlServerDsc that referenced this issue Dec 31, 2018
bozho added a commit to bozho/SqlServerDsc that referenced this issue Dec 31, 2018
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jan 2, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jan 2, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jan 2, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Mar 5, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Mar 5, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Mar 5, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Mar 5, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Mar 5, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Mar 15, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Mar 15, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue Mar 15, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 6, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 7, 2019
@johlju johlju added in progress The issue is being actively worked on by someone. and removed help wanted The issue is up for grabs for anyone in the community. labels May 8, 2019
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 13, 2019
johlju pushed a commit that referenced this issue May 13, 2019
- Changes to SqlRS
  - Can now initialise SSRS 2017 instances (issue #864)
@kwirkykat kwirkykat removed the in progress The issue is being actively worked on by someone. label May 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants