> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cloud-onboarding-template-releases/cloud-onboarding-templates-gcp-rn.md). # GCP ## 2026-10-20 ### Terraform #### AUTOMATION * Added permissions for automation to manage resources across Compute Engine, Cloud KMS (including encrypt/decrypt), Cloud Storage (including IAM), Cloud Functions, Google Kubernetes Engine, Cloud Logging, and Resource Manager. * Added permission to invoke Cloud Functions, and replaced the network peering update permission with more specific add/remove peering permissions. #### GENERAL * Added asset discovery for Gemini Agent Platform resources, including managed agents, MCP servers, reasoning engines, agent identities and credentials, agent gateways, gateway policies, agent registries, and agent skills. * Added discovery of auth providers for Gemini Agent Platform agent credentials, reasoning engine agent-identity bindings, and Agent Gateway authorization extensions. * Added permission to list IAM policy bindings. * Fixed an issue that could force the onboarding role to be re-created during an upgrade. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/cloud-onboarding-template-releases/cloud-onboarding-templates-gcp-rn.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.