CD & Release Orchestration

In a logged deployment there is a link to the associated job but the job's UI doesn't have a link to the deployment

Currently additional configuration needs to be added to account for the deploy marker job's status. Success and failure can be handled within the same job but canceled requires an additional job. These patterns are difficult to orbify because canceled requires adding the canceled job into a workflow

Facilitate programmatic interaction with historical deploy data via API

Links to the deployed resources, associated jira ticket, and other customized links being added to each deployment would help unify data around deployment in one place.