Request: Define Outputs

[whatisdot]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

Triggering a pipeline works as expected, but there's no way to consume and use the response in following steps. To do that, we need the action to define outputs for the job.

Describe the solution you'd like

Descriptions taken from the CircleCI API documentation:

outputs:
  id:
    description: The unique ID of the pipeline.
  state:
    description: The current state of the pipeline.
  number:
    description: The number of the pipeline.
  created_at:
    description: The date and time the pipeline was created.

Teachability, documentation, adoption, migration strategy

Descriptions taken from the CircleCI API documentation.

Outputs

Field	Data Type	Description
id	string (uuid)	The unique ID of the pipeline.
state	string (Enum: "created" "errored" "setup-pending" "setup" "pending")	The current state of the pipeline.
number	integer (int64)	The number of the pipeline.
created_at	string (date-time)	The date and time the pipeline was created.

What is the motivation / use case for changing the behavior?

Adds a backwards-compatible feature that enables teams to use the pipeline ID and date created in downstream workflow actions.

[vaxinate]

It would be really helpful to have at least the pipeline ID as outputs for use in other steps 🙏

[whatisdot]

@vaxinate I put up #47 with testing steps if you want to try it out