SqlDatabasePermission: Should Be Cluster Aware

Details of the scenario you tried and the problem that is occurring:
When the xSQLServerDatabasePermission resource is applied to all of the nodes in a Failover Cluster Instance (FCI), all of the nodes will connect to the instance and ensure the desired state is true even if the node is not currently hosting the instance.

The DSC configuration that is using the resource (as detailed as possible):
When the following configuration is applied to two or more nodes in a FCI.

xSQLServerDatabasePermission Grant_SqlDatabasePermissions_SQLUser_Db01
{
    Ensure               = 'Present'
    Name                 = 'CONTOSO\SQLUser'
    Database             = 'AdventureWorks'
    PermissionState      = 'Grant'
    Permissions          = 'Connect', 'Update'
    SQLServer            = 'SQLServer'
    SQLInstanceName      = 'DSC'
    PsDscRunAsCredential = $SysAdminAccount
}

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any

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

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

Locate the xSQLServerDatabasePermission resource and trace how it connects to a SQL Server Failover Cluster Instance when applied on multiple nodes. Use the two-node configuration in the report as the starting scenario. Done means the resource is cluster-aware and does not attempt to ensure permissions from a node that is not hosting the instance.