You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'delete-job' and 'delete-job-schedule' and 'delete-call' and 'delete-call-schedule' commands are all missing support for the optional '--force' or '-f' option causing execution error due to incompatible syntax and resulting in unexpected duplicated setup since the delete command with the optional option is not taking effect:
We are currently deciding if we are going to implement the prompt if the force is not set or just treat the force flag as a noop argument since the command's default behavior is to delete.
PR #2 Will be fixing this issue. Also added a --prompt flag that actually performs the prompting. This does not change the current behavior since an explicit action is required to get the confirmation to function. The --prompt flag will not be externally documented through the plugin at this time. Once the PR gets through the pipeline, this issue will be closed.
The 'delete-job' and 'delete-job-schedule' and 'delete-call' and 'delete-call-schedule' commands are all missing support for the optional '--force' or '-f' option causing execution error due to incompatible syntax and resulting in unexpected duplicated setup since the delete command with the optional option is not taking effect:
USAGE:
delete-job JOB_NAME [--force]
delete-job-schedule JOB_NAME SCHEDULE_GUID [--force]
delete-call CALL_NAME [--force]
delete-call-schedule CALL_NAME SCHEDULE_GUID [--force]
OPTIONS:
--force, -f Force deletion without confirmation
The text was updated successfully, but these errors were encountered: