Hi,
after the 0.17 release I noticed an issue.
Whenever I run:
scalr create-run -auto-apply=true -source=cli -workspace-id=<my-workspace-id>
The result is:
IGNORE UNSUPPORTED FIELD source <nil>
{
...correct json response
}
In effect I can't use the -source parameter. From what I see, it always defaults to scalr-cli.
On the other hand ./scalr -help create-run still shows that this parameter is available:
-source=STRING The origin of the run.
[ api, cli, scalr-cli, configuration-version, service-catalog, ui, vcs, vcs-task, run-trigger, schedule, restart, restart-ci, assistant, dashboard-run, dashboard-workspace, workspaces-environment, workspaces-environment-bulk, workspaces-account, workspaces-account-bulk, reports-iac-versions, reports-stale-workspaces, auto-destroy, comment-github, vscode, drift-detection ]
When testing it with previous scalr-cli version (0.16.2) the same command (scalr create-run -auto-apply=true -source=cli -workspace-id=<my-workspace-id>) outputs only the json response (that is IGNORE UNSUPPORTED FIELD source <nil> is not present).
Is it a bug, or was it recently removed?
Hi,
after the 0.17 release I noticed an issue.
Whenever I run:
The result is:
In effect I can't use the
-sourceparameter. From what I see, it always defaults toscalr-cli.On the other hand
./scalr -help create-runstill shows that this parameter is available:When testing it with previous
scalr-cliversion (0.16.2) the same command (scalr create-run -auto-apply=true -source=cli -workspace-id=<my-workspace-id>) outputs only the json response (that isIGNORE UNSUPPORTED FIELD source <nil>is not present).Is it a bug, or was it recently removed?