From 4785d7ae0e625995cd71986b690d5a241457a9ac Mon Sep 17 00:00:00 2001 From: Lars Kellogg-Stedman Date: Fri, 2 Oct 2026 17:03:18 -0400 Subject: [PATCH] Disable terraform plan/apply workflows These workflows rely on a shared state bucket that is hosted at the MOC. That state bucket may be going away in the near future as we clean up AWS resources. If you continue to use this repository you should migrate the state to an object bucket controlled by ecosystems engineering. I'm happy to provide a state export. --- .github/workflows/apply.yaml | 8 -------- 1 file changed, 8 deletions(-) diff --git a/.github/workflows/apply.yaml b/.github/workflows/apply.yaml index e1b5be9..73448df 100644 --- a/.github/workflows/apply.yaml +++ b/.github/workflows/apply.yaml @@ -19,14 +19,6 @@ on: description: "One-time: comma-separated Terraform resource addresses to exclude from this apply (e.g. a resource that's known-broken and blocking every other pending change atomically, while a permanent fix is prepared). Leave empty for a normal apply." required: false default: "" - schedule: - - cron: "17 */4 * * *" - push: - paths: - - "**/*.tf" - - "**/*.csv" - branches: - - main concurrency: # This workflow has no pull_request trigger, so github.event.pull_request.number