Record a GitHub Deployment after each deployment and deactivate on app delete

[zachcasper]

Summary

Have the run-rad-commands action record a GitHub Deployment on a successful deploy and mark it inactive when the application is deleted.

Part of the Repo Radius feature specification (PR #12078).

Details

GitHub Deployments give the frontend and the repository a native record of what is deployed where and at which commit. On a successful deploy, the action records a GitHub Deployment at the deployed commit for the target environment (see User Story 1.2). Promotion flows read the GitHub Deployment to determine the currently deployed commit (see User Story 3.1). When the application is deleted, the corresponding GitHub Deployment is marked inactive (see User Story 3.2).

Requirements

• FR13: run-rad-commands shall record a GitHub Deployment on a successful deploy and mark it inactive on delete.

Acceptance criteria

• A successful deploy records a GitHub Deployment at the deployed commit for the target environment.
• Deleting the application marks the corresponding GitHub Deployment inactive.
• The recorded GitHub Deployment reflects the environment and commit so promotion flows can read it.

[radius-triage]

👋 @zachcasper Thanks for filing this feature request.

A project maintainer will review this feature request and get back to you soon.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview