Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Path

Method

Description

/api/v3/pipeline

Status
colourGreen
titlePOST

Execute adhoc
pipeline YAML or JSON given in the body. The pipeline is not stored.

  • The request body will become the body of the pipeline.

  • Request params will be set in vars scope of the pipeline.

  • Request and response can be accessed via ${request} and ${response} object in the pipeline.

See: https://pipeforce.github.io/api#/Pipeline%20API

Info

For security reasons, executing adhoc pipelines is by default restricted to admin, support and developer users in DEV stage only.

For production stage you should always consider to use persisted pipelines instead.

/api/v3/pipeline:{path}

Status
colourYellow
titlePUT

Store
the pipeline YAML given in the body in the property store at {path}. Overwrite any existing one.

See: https://pipeforce.github.io/api#/Pipeline%20API

/api/v3/pipeline:{path}

Status
colourGreen
titlePOST

Load and execute
the persisted pipeline at {path} from the property store:

  • The request body will become the body of the pipeline.

  • Request params will be set in vars scope of the pipeline.

  • Request and response can be accessed via ${request} and ${response} object in the pipeline.

See: https://pipeforce.github.io/api#/Pipeline%20API

/api/v3/pipeline:{path}

Status
colourBlue
titleGET

Return
the pipeline source persisted at {path} from the property store.

See: https://pipeforce.github.io/api#/Pipeline%20API

/api/v3/pipeline:{path}

Status
colourRed
titleDELETE

Delete
the persisted pipeline at {path} from the property store.

See: https://pipeforce.github.io/api#/Pipeline%20API

/api/v3/property:{path}

Status
colourYellow
titlePUT

Status
colourBlue
titleGET

Status
colourRed
titleDELETE

Create, read, update and delete persisted JSON documents, attachments and other data types in the persistence DB, called the Property Store.

See: https://pipeforce.github.io/api#/Property%20API

/api/v3/command:{name}

Status
colourGreen
titlePOST

Status
colourBlue
titleGET

Execute
a single command given by name {name}.

  • The request body in

    Status
    colourGreen
    titlePOST
    requests will become the body of the command.

  • Request params of

    Status
    colourGreen
    titlePOST
    or
    Status
    colourBlue
    titleGET
    requests will become the params to the command.

  • In case parameters must be send in body instead of request parameters, use

    Status
    colourGreen
    titlePOST
    , set the request parameter ?params=body and place the command parameters as JSON in the body.

See here for a full list of available commands:
https://pipeforce.github.io/api

...

Info

Note: It is possible to restrict the permission by users, roles and groups who is allowed to call commands. See Users, Groups, Roles and Permissions for more details.

...