Details of the scenario you tried and the problem that is occurring
Basically i tested to create new exclusion range which works ok
Running the same configuration also works fine as expected - idempotency is ok
Problem is when I change the parameter of the exclusion range, i get fatal error of the module
Seems that module is not able to deal with this scenario
Then i thought OK lets delete all ranges from the range and re-run the code with new parameters
Here i bumped into another issue.
This module requires Start and End IP which makes sense.
Problem is that i dont have a way to get information about existing ranges from any DSC module. That means i have create extra code to grab the exclusions and feed it to the module with parameter absent
Would be great to NOT have Start and End IP mandatory when ABSENT is selected. That way the module simply delete all Exclusion ranges
Verbose logs showing the problem
Suggested solution to the issue
I know its bit tricky issue with changing the exclusion, maybe you have some idea how to enhance it ?
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version and build of PowerShell the target node is running
Details of the scenario you tried and the problem that is occurring
Basically i tested to create new exclusion range which works ok Running the same configuration also works fine as expected - idempotency is ok
Problem is when I change the parameter of the exclusion range, i get fatal error of the module Seems that module is not able to deal with this scenario
Then i thought OK lets delete all ranges from the range and re-run the code with new parameters Here i bumped into another issue. This module requires Start and End IP which makes sense. Problem is that i dont have a way to get information about existing ranges from any DSC module. That means i have create extra code to grab the exclusions and feed it to the module with parameter absent
Would be great to NOT have Start and End IP mandatory when ABSENT is selected. That way the module simply delete all Exclusion ranges
Verbose logs showing the problem
Suggested solution to the issue
I know its bit tricky issue with changing the exclusion, maybe you have some idea how to enhance it ?
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used