Skip to content

Keep encrypted Cloudflare recovery with its owner #33

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Summary

Keep the retained pre-migration DNS recovery snapshot with its declarative Cloudflare owner, recoverable through the existing independent infrastructure recovery key.

Motivation

Recovery material should remain with its configuration owner and be usable from another trusted machine without introducing another repository or private key dependency.

Proposed Solution

Re-encrypt the existing authenticated snapshot to the infrastructure recovery recipient and retain only ciphertext in this repository. Keep operational service credentials in their existing secret store. Validate the retained package and document the distinction between reviewed desired configuration, a current provider inventory, and future infrastructure state recovery.

Acceptance Criteria

  • The existing snapshot is recoverable from repository ciphertext and the independently held infrastructure key, without the temporary snapshot identity.
  • Repository checks reject plaintext, damaged or mismatched packages, unexpected files and incorrect recovery bindings.
  • A real decrypt-and-compare proves the retained payload is unchanged; a fresh repository checkout passes the same recovery check after protected merge.
  • Documentation preserves import-first, no-destructive-plan and first-apply review requirements. This change performs no provider writes and does not claim complete infrastructure state recovery.

Alternatives Considered

The provider API can reconstruct a current inventory, but cannot recover deleted configuration or one-time credential values. A separate recovery repository and an additional wrapped private key are unnecessary for this retained snapshot. The cluster-hosted secret store cannot be the sole bootstrap recovery dependency.

Part of #21. Full import, active state backend and first apply remain under devantler-tech/monorepo#3274.

Activity

  1. self-assigned this
    on Oct 29, 2026
  2. moved this to 🫴 Ready in 🌊 Project Boardon Oct 29, 2026
  3. coderabbitai commented on Oct 29, 2026

    @coderabbitai
    🔗 Related PRs

    #34 - feat(recovery): retain encrypted DNS recovery with its owner [closed]
    #32 - feat: prepare encrypted read-only DNS snapshots [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  4. moved this from 🫴 Ready to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Oct 29, 2026
  5. added a commit that references this issue on Oct 29, 2026
  6. devantler commented on Oct 29, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Completed by #34, protected-merged as f3a89853a1d38f970550a625f064f7ca1d498b13. Main CI passed. A newly cloned main has the reviewed tree, passes the retained-package checks, and authentically decrypts the source-bound snapshot using the independently held infrastructure identity. Earlier decrypt-and-compare proved unchanged content and refusal by the temporary snapshot identity. No plaintext recovery file was written.

    This closes custody of the retained historical DNS snapshot. Provider adoption, current inventory, active infrastructure state and full recovery remain open under #21 and devantler-tech/monorepo#3274. No provider write or credential rotation occurred.

  7. moved this from 🏃🏻‍♂️ In Progress to ✅ Done in 🌊 Project Boardon Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Fields

Priority

None yet

Start date

None yet

Target date

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions