-
Notifications
You must be signed in to change notification settings - Fork 49
Self-Signed Certificate Removed When Used with Modules that Restart AppVeyor #255
Comments
I thought by setting them to ’machine’ they would be permanent and would be loaded into the session again on reboot. 🤔 If that is not the case, then I’m okay with moving those line into the test-phase function instead. |
It doesn't seem to be the case - at least not with what I'm seeing. I'll submit a PR. |
I had a think about this and actually, what might be the best idea is to convert |
Do you mean |
Correction: I'll just update |
Sounds good! 👍 |
Cool! Just testing the changes with ActiveDirectorCSDsc. I should submit the changes in a little bit. |
The Self-signed certificate that is used for compiling the Example DSC files is created and the location assigned to
ENV:
variables inside theInvoke-AppveyorInstallTask
. However, some DSC Resources reboot the AppVeyor container afte theInvoke-AppveyorInstallTask
runs (e.g. so that some Windows Features can be installed fully). This clears theENV:
variables, so that they can no longer be accessed byInvoke-AppveyorTestScriptTask
(or other code).It is possible to execute
Invoke-AppveyorInstallTask
a second time, after the reboot in thetest_script:
section of the AppVeyor.yml, but this seems counter-intuitive. An alternative would be to move the:down into the
Invoke-AppveyorTestScriptTask
function instead.The text was updated successfully, but these errors were encountered: