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.

Sign up for GitHub

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

Jump to bottom

SqlDatabase: Enforces collation even if the parameter is not specified in the configuration #1396

Closed
johlju opened this issue Jul 15, 2019 · 0 comments · Fixed by #1391
Closed

SqlDatabase: Enforces collation even if the parameter is not specified in the configuration #1396

johlju opened this issue Jul 15, 2019 · 0 comments · Fixed by #1391
Labels
bug The issue is a bug.

Comments

@johlju
Copy link
Member

johlju commented Jul 15, 2019

Details of the scenario you tried and the problem that is occurring

If the Collation parameter is not specified in a configuration, the resource will still enforce the property against the SQL Server instance collation.

This is related to issue #1395.

Verbose logs showing the problem

Suggested solution to the issue

The DSC configuration that is used to reproduce the issue (as detailed as possible)

# insert configuration here

SQL Server edition and version the target node is running

SQL Server PowerShell modules present on the target node

The operating system the target node is running

Version and build of PowerShell the target node is running

Version of the DSC module that was used ('dev' if using current dev branch)
@johlju johlju added bug The issue is a bug. in progress The issue is being actively worked on by someone. labels Jul 15, 2019
@pshamus pshamus mentioned this issue Jul 15, 2019
Merged
9 tasks
johlju added a commit to pshamus/SqlServerDsc that referenced this issue Jul 15, 2019
@johlju
Fixes issue dsccommunity#1395 and issue dsccommunity#1396
674506e
johlju pushed a commit that referenced this issue Jul 17, 2019
@pshamus @johlju
SqlDatabaseUser: New DSC resource (#1391)
bb95eb8 
- Changes to SqlServerDsc
  - New DSC resource SqlDatabaseUser (issue #846).
    - Adds ability to create database users with more fine-grained control,
      e.g. re-mapping of orphaned logins or a different login. Supports
      creating a user with or without login name, and database users mapped
      to a certificate or asymmetric key.
  - Minor style fixes in unit tests.
- Changes to SqlDatabase
  - Get-TargetResource now correctly return `$null` for the collation property
    when the database does not exist (issue #1395).
  - No longer enforces the collation property if the Collation parameter
    is not part of the configuration (issue #1396).
  - Updated resource description in README.md
  - Fix examples to use `PsDscRunAsCredential` (issue #760).
  - Added integration tests (issue #739).
  - Updated unit tests to the latest template (issue #1068).
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Jul 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug The issue is a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

SqlDatabaseUser: New DSC resource pshamus/SqlServerDsc
1 participant
@johlju