From 4d7815240776b9636bde0d3d005e82184e04a8b4 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 29 Sep 2026 22:38:07 +0000 Subject: [PATCH] Apply the declared Cloudflare Access rules to the security-room policy The first deploy of #195 adopted the live policy as-is. Turning off the import lets Pulumi replace sdk-maintainers with security-team. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_01YBarRtzEtwT2HvfcEvRbW7 --- Pulumi.prod.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Pulumi.prod.yaml b/Pulumi.prod.yaml index 89243b5..cd56079 100644 --- a/Pulumi.prod.yaml +++ b/Pulumi.prod.yaml @@ -8,6 +8,6 @@ config: # cloudflare:roleManagementToken is set by the deploy workflow from the CLOUDFLARE_ROLE_MANAGEMENT_TOKEN secret. cloudflare:accountId: c39d6379ccfdb20a3627eeddffa80ec9 cloudflare:githubIdentityProviderId: 1e53bc11-a504-4572-92d1-4c8d56fc198b - # Adopt the existing dashboard-created policies on the first deploy. Set to "false" - # in a follow-up PR once the deploy that imported them has succeeded. - cloudflare:importExistingPolicies: "true" + # The dashboard-created policy was adopted by the first deploy of #195 and is now + # managed from config. Leave this "false" so deploys apply the declared rules. + cloudflare:importExistingPolicies: "false"