SqlDatabaseUser: New resource

[bozho]

xSQLServerDatabaseRole currently handles DB user creation and role assignment (for already existing roles)

The name is a bit confusing, since the name implies the resource actually handles DB roles creation/removal.

I suggest we rename xSQLServerDatabaseRole to XSQLServerDatabaseUser.

The new resource xSQLServerDatabaseRole would then handle DB roles.

[johlju]

I agree to rename this resource, and change so that this resource only handles creation and dropping of database user.

This must be merged at the same time (or close to the same time) as the issue #847 is merged.

[johlju]

Practically, to be able to create a PR for this issue and issue #847, I think it would be best to not rename this resource but instead, if it helps, copy the code from the xSQLServerDatabaseRole to the new resource xSQLServerDatabaseUser and change the code there. This will make it possible to change to xSQLServerDatabaseRole without merge conflicts.

[johlju]

This is the proposed schema. Please comment if you see anything that needs to be changed.

[ClassVersion("1.0.0.0"), FriendlyName("SqlDatabaseUser")]
class MSFT_SqlDatabaseUser : OMI_BaseResource
{
    [Key, Description("Specifies the name of the database user to be added or removed.")] String Name;
    [Key, Description("Specifies the host name of the SQL Server on which the instance exist.")] String ServerName;
    [Key, Description("Specifies the SQL instance in which the database exist.")] String InstanceName;
    [Key, Description("Specifies the name of the database in which to configure the user.")] String DatabaseName;
    [Write, Description("Specifies the name of the SQL login to associate with the database user. This must be specified if parameter UserType is set to 'Login'.")] String LoginName;
    [Write, Description("Specifies the name of the asymmetric key to associate with the database user. This must be specified if parameter UserType is set to 'AsymmetricKey'.")] String AsymmetricKeyName;
    [Write, Description("Specifies the name of the certificate to associate with the database user. This must be specified if parameter UserType is set to 'Certificate'.")] String CertificateName;
    [Write, Description("Specifies the user type of the database user. Valid values are 'Login', 'NoLogin', 'Certificate', or 'AsymmetricKey'. Defaults to 'Login'."), ValueMap{"Login", "NoLogin", "Certificate", "AsymmetricKey"}, Values{"Login", "NoLogin", "Certificate", "AsymmetricKey"}] String UserType;
    [Write, Description("Specifies if the user should be present or absent. If 'Present' then the user will be added to the database and, if needed, the login mapping will be updated. If 'Absent' then the user will be removed from the database. Defaults to 'Present'."), ValueMap{"Present", "Absent"}, Values{"Present", "Absent"}] String Ensure;
    [Read, Description("Returns the authentication type of the SQL login connected to the database user. This will return either 'Windows', 'Instance' or 'None'. The value 'Windows' means the SQL login is using Windows Authentication, 'Instance' means that the SQL login is using SQL authentication, and 'None' means that the database user have no SQL login connected to it.")] String AuthenticationType;
    [Read, Description("Returns the login type of the SQL login connected to the database user. If no SQL login is connected to the database user this returns $null.")] String LoginType;
};