cAppPool - Setting Identity Type to specific user but not username and password about dsc HOT 3 CLOSED

I'm not sure if that scenario should be supported. If you are telling DSC to configure an application pool to run as a specific user, shouldn't you be required to also give DSC the username and password? If the App Pool didn't exist and you applied a DSC configuration where the identity type was 'SpecificUser', but without setting a username or password, DSC would be producing a broken system.

Even before your proposed changes, this resource's code around the pool identity looks a bit iffy to me.

I think a cleaner solution might be to make the identity type parameter completely optional (removing its current default setting), and just ignore those settings if IdentityType is set to $null (only applying a default value if it has to create a new pool).

Making that change would require an update to existing configuration scripts, though, if they were previously assuming that an unspecified value for IdentityType would default to ApplicationPoolIdentity.

from dsc.

I was about to say the same, but Dave beat me to it.

from dsc.

I did want to add though, thank you for offering to contribute back. I do appreciate the offer.

from dsc.