-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Add-DhcpServerSecurityGroup #23
Comments
I've recently stumbled upon this problem while working with DSC. @kwirkykat I'm happy to do the work. Do you think this should be in it's own resource with a single "Ensure" variable, or could this go into xDhcpServerAuthorization (I already have the code written in there but I can split it out). |
I agree, this is a necessary addition to make the resource really "no touch" |
@LiamFisher92 Is there any instance outside xDhcpServerAuthorization where it would be useful to be able to create the DHCP Administrators and the DHCP Users groups? |
@kwirkykat I can't think of a reason you would need the security groups without authorizing the DHCP server. Would splitting them out not lead to potential fully set-up unauthorized DHCP servers floating around? I'd be happy to shift them around if somebody else can think of one? I'm conscious of the fact I might lose the code I've already done so I'll submit a PR for now. |
@LiamFisher92 Ok. If there is no reason to split it out, then the security group creation should stay in xDhcpServerAuthorization |
@kwirkykat I'm not really a DHCP expert (I'm a games development graduate in disguise) so I can't really give you a definitive answer. Do you know anyone who could? |
@LiamFisher92 I'll ask around |
I think this should be a separate resource - having the DHCP server authorized ( I suggest a new resource |
Support for Add-DhcpServerSecurityGroup would be nice to have, so as to create the DHCP Administrators and the DHCP Users groups. This is easily worked around with a script resource, but it would be nice to be included in this Resource Module.
The text was updated successfully, but these errors were encountered: