SqlDatabaseRole: Should Be Cluster Aware

Details of the scenario you tried and the problem that is occurring:
When the xSQLServerDatabaseRole 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.

xSQLServerDatabaseRole Add_Database_Role
{
    Ensure               = 'Present'
    SQLServer            = 'SQLServer'
    SQLInstanceName      = 'DSC'
    Name                 = 'CONTOSO\SQLAdmin'
    Role                 = 'MyRole', 'MySecondRole'
    Database             = 'AdventureWorks'
    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

Start by locating the xSQLServerDatabaseRole resource and reviewing how it connects to SQL Server instances. Reproduce the supplied configuration across two or more nodes in a Failover Cluster Instance (FCI), including a node that is not hosting the instance. Done means the resource handles the FCI without every node independently enforcing the database role state.