docs(gcp-wif): add Cloud Asset API enablement as required step - #236
Open
girish-cheedala wants to merge 8 commits into
Open
docs(gcp-wif): add Cloud Asset API enablement as required step#236girish-cheedala wants to merge 8 commits into
girish-cheedala wants to merge 8 commits into
Conversation
- Revise GCP integration overview for clarity on discovery approaches and authentication methods. - Introduce a detailed table of supported GCP services. - Expand on enumeration scope with project-level and organization-level discovery options. - Add warnings regarding permission requirements for organization-level enumeration. - Include new authentication methods with descriptions and links. - Add a new image for GCP integration screen.
The GCP org-level integration uses the Cloud Asset Inventory API for all discovery operations (Verify and Resources). The API must be enabled in the WIF pool/SA project (identified by the project number in the WIF provider path) for the integration to work. - Add Step 6: Enable Cloud Asset API with check and enable commands - Renumber Step 6→7 (Provider path) and Step 7→8 (Configure in PDCP) - Update troubleshooting: list Cloud Asset API enablement as the first cause of 'Google Cloud denied access', with the exact commands to check and fix using the project number from the WIF provider path
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
The GCP org-level integration uses the Cloud Asset Inventory API for all discovery operations (Verify and Resources). The API must be enabled in the WIF pool/SA project (identified by the project number in the WIF provider path) for the integration to work. - Add Step 6: Enable Cloud Asset API with check and enable commands - Renumber Step 6→7 (Provider path) and Step 7→8 (Configure in PDCP) - Update troubleshooting: list Cloud Asset API enablement as the first cause of 'Google Cloud denied access', with the exact commands to check and fix using the project number from the WIF provider path - Resolve merge conflict with main
Contributor
Author
this is now fixed |
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
2 participants
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
cloudasset.googleapis.com) must be enabled in the WIF pool/SA project for org-level integration to work — this was missing from the docsRoot Cause
Discovered while debugging a customer issue. The GCP org-level integration uses the Cloud Asset API for all operations (
Verify()→SearchAllResources,Resources()→ListAssets). When using WIF credentials, GCP uses the WIF pool project number (from theaudiencefield in the external_account credentials) as the consumer/quota project. If the Cloud Asset API is not enabled in that project, all calls fail with "Google Cloud denied access" — even though IAM permissions are correctly set.Test Plan