بنقرة واحدة
dot-ai-port-destroy
Remove all Port integrations, Kubernetes resources, and local files created by /port-setup
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Remove all Port integrations, Kubernetes resources, and local files created by /port-setup
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Set up Port integrations to sync Kubernetes resources and GitHub Actions to Port.io
Start working on a PRD implementation
Update PRD based on design decisions and strategic changes made during conversations
Kubernetes cluster operations via dot-ai CLI - natural language cluster queries, AI-powered deployment recommendations, issue troubleshooting and remediation, Day 2 operations (scale, update, rollback, delete), resources, namespaces, events, logs, organizational knowledge base (ingest, search, query), organizational patterns/policies/capabilities management, project scaffolding and repo audit, and session history and visualization. Run `dot-ai --help` for commands.
Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.
Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.
| name | dot-ai-port-destroy |
| description | Remove all Port integrations, Kubernetes resources, and local files created by /port-setup |
| user-invocable | true |
Remove all Port integrations, Kubernetes resources, and local files created by /port-setup.
Check the following and instruct the user to install/configure if missing:
PORT_CLIENT_IDPORT_CLIENT_SECRETBefore destroying, discover what exists and how it was deployed:
argocd namespace) or Flux (flux-system namespace)apps/port-*.yaml).github/workflows/port-*.yaml) and repository secretsIMPORTANT: When ArgoCD or Flux is detected, deletions must go through Git first.
This order ensures the exporter stops syncing before you delete resources in Port.
Critical: Delete the K8s exporter FIRST to stop new entities from being synced to Port.
Check deployment method and delete accordingly:
With ArgoCD/Flux (GitOps):
rm <manifest-dir>/port-k8s-exporter.yaml
git add -A && git commit -m "Remove port-k8s-exporter" && git push
kubectl get ns port-k8s-exporter should return not foundkubectl delete ns port-k8s-exporterWith Helm directly (non-GitOps):
helm uninstall port-k8s-exporter -n port-k8s-exporter
kubectl delete secret port-credentials -n port-k8s-exporter
kubectl delete externalsecret port-credentials -n port-k8s-exporter # if using ESO
kubectl delete namespace port-k8s-exporter
Delete all self-service actions created for CRDs. Do this BEFORE deleting blueprints since actions reference blueprints.
mcp__port-vscode-eu__list_actions to find actions with identifiers matching patterns:
create_*, update_*, delete_*mcp__port-vscode-eu__delete_actionDelete the blueprints created during setup from the Data Model page.
Steps:
mcp__port-vscode-eu__list_blueprints to discover which blueprints exist/port-setup (exclude system blueprints starting with _ and the defaults: cluster, namespace, workload)STOP and wait for user confirmation before proceeding.
Look for Port-related workflows and delete them:
rm .github/workflows/port-*.yaml
gh secret delete PORT_CLIENT_ID
gh secret delete PORT_CLIENT_SECRET
gh secret delete KUBE_CONFIG # if created
Commit and push the deletions:
git add -A && git commit -m "Remove Port self-service workflows" && git push
If user wants to remove GitHub integration:
After cleanup, verify:
kubectl get ns port-k8s-exporter returns not found