Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Ops] Fix deployment/project purging logic (elastic#172082)
## Summary We've noticed that on certain PRs, the deployments are cleaned up right after they're creating, with the indication that it was stale. (elastic#170579 - cleaned up in https://buildkite.com/elastic/kibana-purge-cloud-deployments/builds/15440#018c1605-144b-4db5-b29a-e3af3c9b1c70) Turns out, the logic that acquires the last commit's timestamp is relying on the `gh pr` api, and commits are limited there to 100. It's easier to look at the pr's `updatedAt` value. - change purge logic to be based on the PRs updatedAt label instead of the max-100th commit's timestamp See: https://elastic.slack.com/archives/C5UDAFZQU/p1701093461763989
- Loading branch information