Skip to content

Changes waiting for the first Azure/GCP deploy after the 2026-10-20 pause #1413

Open

Description

@IAmJSD

Azure and GCP deploys have been paused since 2026-10-20 (deploy-azure.yml, deploy-gcp.yml and deploy-all.yml are disabled). The owner released the merge hold the same day: "merging is allowed; Azure/GCP apply stays paused" (see #1114). So Azure/GCP PRs merge normally, but some of them change infrastructure that only applies on the first Azure/GCP deploy after the pause. This issue lists them, so that deploy isn't a surprise.

When a PR below merges, it gets ticked here with its merge commit. Whoever re-enables the deploys should read this list first and run a plan against each environment before applying.

Azure/GCP infrastructure that applies on the first deploy (open PRs, not merged yet):

Changes to the disabled deploy workflows (no effect until they're re-enabled):

Code-only Azure/GCP PRs (CI guards, tests, Go and frontend code) need no deploy and aren't tracked here.

Opened by IAmJSD's agent at IAmJSD's request (acting owner while the maintainers are away).

Activity

  1. cristim commented on Nov 5, 2026

    @cristim
    Member

    Triaged: p3 tracker. It matters only when Azure and GCP deploys are re-enabled; whoever does that reads this list and plans each environment first. Severity medium, because an unread item could apply an unexpected change.

  2. cristim commented on Nov 10, 2026

    @cristim
    Member

    Claimed by claude-ui-fix-1 (coordinator assignment): refreshing this tracker. #1203 and #1312 are merged but unchecked, and Azure/GCP infrastructure changes have merged since the list was written. I will post the verified delta as a comment (I did not open this issue, so I leave its body to its author or the owner).

  3. cristim commented on Nov 10, 2026

    @cristim
    Member

    Refresh of this list against main (claude-ui-fix-1, from git log origin/main --since=2026-10-20 over the Azure/GCP terraform, arm and federation paths plus each commit's file list and message). The issue body is not mine to edit, so this is the delta; whoever re-enables the deploys should still run a plan per environment.

    Tick in the body: #1203 merged as 2374b4e9; #1312 merged as fe111246 (its AWS/CloudFormation parts were live on merge).

    Azure/GCP infrastructure merged since the list was written, applies on the first environment deploy:

    Manual ci-cd-permissions applies (bootstrap, not the deploy workflow):

    No deploy effect: #1306 (1ceaafd1, unused ARM parameter), #1439 (0be0374f, lock-file hashes; the env roots now init with -lockfile=readonly), #1587 (docs), #1507 (AWS-target CloudFormation).

    Read from commit contents, not from a plan: confirm each item with terraform plan per environment before applying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions