Add GCP Workload Identity Federation onboarding#250
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Generated-By: mintlify-agent
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new keyless GCP onboarding flow that ships alongside the existing service-account JSON key method.
Customers can now connect a GCP project to Porter without generating or storing a static JSON key. The new flow:
porter-managerservice account in the customer's project.Changes
cloud-accounts/connecting-a-cloud-accountto present three options: Workload Identity Federation (recommended), automated JSON key script, and manual JSON key setup.Source PR
porter-dev/code#5434 — feat: adds a bootstrap endpoint to finalize gcp wif <> porter integration