The input.stage object is present in most spinnaker.execution.stages.before packages, and contains stage metadata.

Since most policies are written to be stage specific, the values in input.stage are less likely to be useful when creating policy scripts.

input.stage.endTimeThe time at which the stage finished executing. This is blank since the stage has not yet completed.
input.stage.idstringThe unique ID for the stage.
input.stage.lastModifiedWhen the stage was last modified.
input.stage.namestringThe name of the stage.
input.stage.outputs{object}DO NOT USE. This contains numerous manifests/artifacts created by the execution of the stage. Typically policies should be written against the inputs to the stage, not its outputs.
input.stage.refIdstringThis stages ID reference in the stage graph. Typically if you are writing a policy that depends on pipeline stage order, it is better to write that policy against either the opa.pipelines bpackage, or the spinnaker.execution.pipelines.before package.
input.stage.startTimenumberThe timestamp at which the stage started
input.stage.statusstringThe stages status, this is typically ‘running’ when this policy is evaluated.
input.stage.tasks[].endTimenumberThe time at which the task finished executing.
input.stage.tasks[].implementingClassstringThe name of the spinnaker class that implements this task.
input.stage.tasks[].namestringThe name of the task being executed. Each stage executes multiple tasks to accomplish its goals.
input.stage.tasks[].startTimenumberThe time at which the task started exeucting.
input.stage.tasks[].statusstringThe status of the task.
input.stage.typestringThe current state of activity of the stage.

Last modified March 3, 2023: (2d069084)