CLI command
weles tasks submit
Submit one task document (schema weles.task.current, from --request or standard input) to the public task API (POST /api/v1/tasks) with the bearer of the item playing --role, reached through --consumer's route or --endpoint, and print what it answered; --idempotency-key repeats a request without doing it twice.
Purpose#
Submit one task document (schema weles.task.current, from --request or standard input) to the public task API (POST /api/v1/tasks) with the bearer of the item playing --role, reached through --consumer's route or --endpoint, and print what it answered; --idempotency-key repeats a request without doing it twice.
Invocation#
weles tasks submit --request <file|-> (--consumer <consumer> | --endpoint <url>) --role <role> [--idempotency-key <key>] [--json]Options#
| Option | Effect |
|---|---|
--request | tasks submit: the task document (schema weles.task.current) as POST /api/v1/tasks takes it. |
--consumer | tasks: the Stado consumer the caller is; the API is the route 'stado service directory connect weles-admission --consumer <consumer>' gives. |
--endpoint | tasks: the public task API's address instead of a consumer's route. |
--role | tasks: the vault role whose item holds the bearer (token) and, for cancel, the organization (organization_id) the API admits. |
--idempotency-key | weles --help names this option in the usage line and gives it no description. |
--json | Print the answer as one JSON document instead of key: value lines. release surface always prints its JSON document: it is the file a release carries. |
Help#
`weles tasks submit --help` prints these usage lines and never runs the command.