You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds two related improvements to the pull request lifecycle:
- Post a comment on the pull/merge request once Burrito applies the
merged changes, reporting success or failure per affected layer
(internal/controllers/terraformpullrequest/comment/apply.go). The
TerraformPullRequest resource is kept alive after merge (annotated
with the merge date instead of being deleted) so its controller can
track layer applies and post that comment once they complete.
- Report plan and apply status via the GitHub Commit Statuses API and
GitLab External Commit Statuses (internal/controllers/terraformpullrequest/status,
APIProvider.SetStatus in the github/gitlab/mock providers). The
status is set to pending when a phase starts and updated to
success/failure based on the actual outcome:
- plan: pending when temp layers are created, success/failure once
the comment is posted, based on whether every layer produced a
plan.
- apply: pending while waiting for the merged layers to apply,
success/failure once they all have, based on LastApplyDate vs a
failed TerraformRun created after the merge.
Status updates are best-effort and never fail the reconciliation loop.
0 commit comments