-
assigned issue to
Add help for importing Munki workflows from another machine
v1.8 build 18059
When importing a workflow with Munki I noticed that I was importing from a different machine, so the workflow had the wrong URL for Munki Repo. Also when saving to volume it did not warn that the certificate path was not valid because it was for the location on the other machine and did not exist on the current machine.
For Munki Repo URL, it could be helpful to provide an option to either hard-code the value or to set the URL dynamically when saving to volume to be the current machine.
For certificate it could be good to add a warning when the certificate file is not found at the specified path.
Comments (3)
-
-
This all depends if the munki is pointing to this machine or to another munki repo. I could do a warning. Holding for customer feedback.
-
- changed status to on hold
- Log in to comment