Closed rismoney closed 7 months ago
This is a class based resource, not sure if that matters...
This is a class based resource, not sure if that matters...
Thanks for raising this @rismony. I'll try look at this when I can, Could you supply a sample manifest to replicate this?
class sql::logons {
dsc_sqlpermission { 'SQLConfigureServerPermission-sec_sqlserver_dev_adm':
dsc_instancename => 'MSSQLSERVER',
dsc_name => 'myco\\sec_sqlserver_dev_adm',
dsc_permission => [
{
'permission' => ['ViewServerState', 'ViewAnyDefinition'],
'state' => 'Grant',
}
],
}
}
this was previously recorded here - https://github.com/dsccommunity/SqlServerDsc/issues/1951
Anything that can be done to expedite this, let me know. I found a bug in the puppet sql module as well, that is causing a blocker in managing this either through that module or via dsc.
Closing as this is an issue in https://github.com/dsccommunity/SqlServerDsc/issues/1951 and not in the builder.
I don't think the issue is in the dsc module. I think it has to do with the use of class based resource. I stopped using DSC with puppet because it is wildly inefficient in its' catalogs bloating
Here is a stack trace of the sqlpermission resource that is not working. Puppet 8.x Windows 2022, SQL 2022.