Skip to content

Draft feature docs: disconnect cloud accounts from the dashboard#392

Open
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/425102cd
Open

Draft feature docs: disconnect cloud accounts from the dashboard#392
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/425102cd

Conversation

@mintlify

@mintlify mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Summary

Porter now supports disconnecting GCP and Azure cloud accounts from the dashboard (AWS already supported), so the revoking-access flow is the same across all three providers: disconnect in Porter, then delete the customer-owned IAM resource in the cloud console.

Changes

  • Rewrote the Revoking Access section in cloud-accounts/connecting-a-cloud-account.mdx for AWS, GCP, and Azure as a two-step flow (disconnect in Porter → delete the IAM role / Workload Identity Pool / app registration).
  • Called out that Porter blocks disconnection while clusters, object storage, or environment groups still reference the account.
  • Updated the "Can I revoke Porter's access?" FAQ in cloud-accounts/overview.mdx to point at the new dashboard flow.

Context

Triggered by porter-dev/code#6577 ("feat: support deleting azure and gcp"), which extends the existing AWS disconnect endpoint to GCP and Azure and ships a unified delete UI plus a list_cloud_account_dependents endpoint used to block disconnects.

cc @d-g-town for review.

@mintlify mintlify Bot requested a review from d-g-town June 26, 2026 14:33
@mintlify

mintlify Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
porter 🟢 Ready View Preview Jun 26, 2026, 2:54 PM

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.

0 participants