dsccommunity / dsccommunity/SqlServerDsc
WaitForSqlRs: New resource proposal
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 385
- Forks
- 224
- PR merge metrics
- No merged PRs in 30d
Description
Resource proposal
Suggest adding a WaitForSqlRs resource that would try to hit the SSRS until it gets http status code 200. There was a need for a timer of 30 seconds in the integration test after running SqlRs and before running an Invoke-WebRequest to be able for it to return http status code 200 (otherwise it returned 503).
Proposed properties
| Property | Type qualifier | Data type | Description | Default value | Allowed values |
|---|---|---|---|---|---|
| InstanceName | Key | String | Name of the SQL Server Reporting Services instance to wait for. | None | None |
| ReportServerUrl | Required | String | Specifies the URL of the Report Server site. | None | None |
| ReportsUrl | Required | String | Specifies the URL of the Report Manager or Report Web App site. | None | None |
| WaitTime | Write | Int16 | Specifies the time to wait (in seconds) initially before trying to access URLs. | 30 | None |
| Timeout | Required | Int16 | Specifies the timeout to wait (in seconds) for the SQL Server Reporting Services instance before throwing an error. If WaitTime is specified, the timeout starts counting down after that initial wait time. |
30 | None |
Special considerations or limitations
- Should make sure the instance is installed before trying to wait for the URLs.
- Should wait until the URLs return http status code 200. It should preferably output other http status codes in a verbose message, and finally in the thrown message.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by locating the module's existing SQL Server Reporting Services resources and their tests, then compare their conventions with the proposed properties and waiting behavior. Done means a WaitForSqlRs resource checks installation, waits for the configured interval and timeout, and reports non-200 responses as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, sql
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100