issues icon indicating copy to clipboard operation
issues copied to clipboard

Renaming script names should trigger an update of related entries in Schedule.ps1

Open DataTraveler1 opened this issue 2 years ago • 1 comments

Steps to Reproduce

Renaming script names directly in .Universal\Scripts.ps1 does not trigger an update of related entries in Schedule.ps1

Suggestions

  1. Allow the Schedules.ps1 New-PSUSchedule modules Name parameter to match a registered scripts name, relative path (in repository or scripts) or full path name

  2. Update New-PSUSchedule dynamic parameters with more resiliency. For example: If there is a failure pulling "$URL/api/v1/script/$($ScriptName) ", maybe try a few other options before gently exiting.

Expected behavior

Renaming script names directly in .Universal\Scripts.ps1 should an update of related entries in Schedule.ps1

Actual behavior

Renaming script names directly in .Universal\Scripts.ps1 does not trigger an update of related entries in Schedule.ps1

Environment data

PSU 3.7.10

Visuals

Thanks to the person who reported this internally 👍

DataTraveler1 avatar Feb 09 '23 21:02 DataTraveler1

I'd also suggest updating script names in triggers.ps1 should be bundled in with this too

insomniacc avatar Feb 22 '24 14:02 insomniacc