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
Linux USHQL835 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Description
When making any request to sandbox:update with a stop-scheduler or start-scheduler request, the request always fails, and at the same time, sets auto-scheduled to false (see log output, where a --stop-scheduler request is made, and eventually the PATCH request is made, and the body simply has autoScheduled: false.
It turns out this an issue with parameter order in cli.js
if (scheduleOk) {
require('./lib/sandbox').cli.update(spec, ttl, autoScheduled, false, startScheduler, stopScheduler);
}
But the function signature for update is:
/**
* Update a sandbox.
*
* @param {String} spec specification of the sandbox to update
* @param {Number} ttl number of hours, the sandbox TTL will be prolonged
* @param {Boolean} autoScheduled sets the sandbox as auto scheduled
* @param {String} startScheduler start schedule for the sandbox
* @param {String} stopScheduler stop schedule for the sandbox
* @param {Boolean} asJson optional flag to force output in json, false by default
*/
update : function(spec, ttl, autoScheduled, startScheduler, stopScheduler, asJson) {
so the hardcoded false parameter is throwing off the scheduler parameters, and thus a stopScheduler is always determined to be null based on the update function parameter validation.
sfcc-ci Version
2.12.0
NodeJS Version
v10.24.1
sfcc-ci Path
/home/xxxxxxx/.nvm/versions/node/v10.24.1/bin/sfcc-ci
Host OS Details
Linux USHQL835 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Description
When making any request to
sandbox:update
with a stop-scheduler or start-scheduler request, the request always fails, and at the same time, sets auto-scheduled to false (see log output, where a --stop-scheduler request is made, and eventually the PATCH request is made, and the body simply has autoScheduled: false.It turns out this an issue with parameter order in
cli.js
But the function signature for update is:
so the hardcoded
false
parameter is throwing off the scheduler parameters, and thus a stopScheduler is always determined to be null based on theupdate
function parameter validation.Relevant log output
The text was updated successfully, but these errors were encountered: