You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a group that is created with IsAssignableToRole, it would be helpful to also be able to assign it to one or more AAD roles and subsequently to maintain such role-assignments. Therefore, an additional property AssignedToRole is proposed
Also, it would be nice to be able to build and maintain security-groups that are intended as role-groups, ie members of a role-group are recursively members of one or more security-groups. Therefore, an additional property MemberOf is proposed
Proposed properties
MemberOf
AssignedToRole
Special considerations or limitations
I have already written the necessary addition to the DSC-resource (based off of an earlier version and retro-fitted to the current dev-version of the DSC-resource) and tested it against a test-tenant.
However, since I'm not really at home with Pester, I'm contemplating how unit-tests could - and/or should - be written to verify that the new functionality works as intended. It gets complicated quickly as there's a need for mocking additional groups and one or more directory roles, so it tends to become more similar to a kind of integration-test. Please advise..
The text was updated successfully, but these errors were encountered:
I think I have the unit-tests sorted by using -ParameterFilter in the Get-MgGroup mocks. Tests include whether a group is a member of another group and whether a group is assigned to the correct AAD-role. I'll run the test-harness and report back
Description
For a group that is created with IsAssignableToRole, it would be helpful to also be able to assign it to one or more AAD roles and subsequently to maintain such role-assignments. Therefore, an additional property AssignedToRole is proposed
Also, it would be nice to be able to build and maintain security-groups that are intended as role-groups, ie members of a role-group are recursively members of one or more security-groups. Therefore, an additional property MemberOf is proposed
Proposed properties
MemberOf
AssignedToRole
Special considerations or limitations
I have already written the necessary addition to the DSC-resource (based off of an earlier version and retro-fitted to the current dev-version of the DSC-resource) and tested it against a test-tenant.
However, since I'm not really at home with Pester, I'm contemplating how unit-tests could - and/or should - be written to verify that the new functionality works as intended. It gets complicated quickly as there's a need for mocking additional groups and one or more directory roles, so it tends to become more similar to a kind of integration-test. Please advise..
The text was updated successfully, but these errors were encountered: