Skip to content

"arguments" instead of "cli_arguments" when starting a job #3

@MBerdasco

Description

@MBerdasco

I didn't test the PS module but I checked the sources looking for help in order to see how the REST API works and I found out a possible issue:

if($CLIArguments)
{
$Body.Add("cli_arguments", $CLIArguments)
}

"cli_arguments" does not work for me (at least in Semaphore v2.9.56). Changed to "arguments" works perfectly. In fact, this is how the Semaphore UI send the payload when starting a job

arguments: "[\"--extra-vars\", \"serverList=server1.mydomain.com\"]" environment: "{}" project_id: 1 template_id: 15

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions