Skip to content

Add identity-gated edge migration planning skill - #285

Draft
kennyj42 wants to merge 1 commit into
cloudflare:mainfrom
kennyj42:kjohnson/identity-gated-edge-migration
Draft

kennyj42 wants to merge 1 commit into
cloudflare:mainfrom
kennyj42:kjohnson/identity-gated-edge-migration

Conversation

@kennyj42

Copy link
Copy Markdown

Summary

  • Add identity-gated-edge-migration for inventorying self-hosted HTTP applications and planning their migration behind Access.
  • Include a DNS discovery checklist, configuration decision references, and a local migration-plan template.
  • Add the skill to the README catalog and route relevant requests from cloudflare and cloudflare-one.

Scope

Based on Brian's identity-gated edge migration-planning draft. This contribution keeps its provider-aware discovery, Protect/Public/Unknown classification, configuration interview, and staged rollout workflow.

Following CONTRIBUTING.md, product details come from current Cloudflare documentation rather than bundled API calls or Terraform modules. The draft's provider-specific discovery scripts, source-fetching configuration, deployment shell script, and static Terraform templates are not included. The skill directs the agent to inspect existing resources and current schemas before generating implementation artifacts on request.

Discovery and planning are read-only against external systems. Inventory refreshes preserve owner decisions, credentials stay out of the plan, and external changes require approval. Existing origin choices and inventory-only requests remain in scope without forcing a full migration.

Documentation

Companion reference architecture, design guide, and Tunnel pilot: cloudflare/cloudflare-docs#35225.

This skill uses published, product-specific Markdown documentation today. It does not depend on the unmerged companion PR or require access to the private draft repository.

Validation

  • Ran the skill-creator quick_validate.py validator successfully.
  • Parsed YAML metadata and verified name/directory consistency for the new skill and both updated routing skills.
  • Checked all four new skill files for valid UTF-8, LF line endings, and resolving local references.
  • Retrieved all 18 linked Cloudflare Markdown documentation pages successfully.
  • Reviewed the migration workflow against the current self-hosted Access, origin-protection, JWT-validation, and Dedicated CDN Egress IP/CNI documentation.
  • Reviewed routing for inventory-only requests, existing Access client authentication, and VPN/SASE migrations.
  • Ran git diff --check.

No Cloudflare infrastructure was changed. No deployment scripts or new executable code are included.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant