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

SqlRSSecureConnectionLevel: Localization should change to align with HQRM modules #623

Closed
johlju opened this issue Jun 6, 2017 · 0 comments · Fixed by #991
Closed

SqlRSSecureConnectionLevel: Localization should change to align with HQRM modules #623

johlju opened this issue Jun 6, 2017 · 0 comments · Fixed by #991
Assignees
Labels
enhancement The issue is an enhancement request.

Comments

@johlju
Copy link
Member

johlju commented Jun 6, 2017

Details of the scenario you tried and the problem that is occurring:
Resource should use the same method of localization as HQRM modules (PSDscResource). More information in PR #205.

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:
n/a

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 enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. labels Jun 6, 2017
@johlju johlju changed the title xSQLServerRSSecureConnectionLevel: Localization should change to align with HQRM modules SqlRSSecureConnectionLevel: Localization should change to align with HQRM modules Dec 24, 2017
@johlju johlju removed the help wanted The issue is up for grabs for anyone in the community. label Jan 4, 2018
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.

1 participant