Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Armazene dependências dos seus aplicativos do App Engine no Artifact Registry.
Declare dependências no Artifact Registry nos seus aplicativos Node.js e
Python.
Implante seu aplicativo no App Engine usando o Cloud Build.
Permissões necessárias
Ambiente flexível do App Engine
Se o ambiente flexível do App Engine e o Artifact Registry estiverem no mesmo projeto, a
conta de serviço padrão do App Engine terá permissões para
extrair contêineres dos repositórios.
Se você também usa o Cloud Build para contêinerizar seus aplicativos e armazená-los
no Artifact Registry, conceda o papel de Gravador do Artifact Registry
à conta de serviço do Cloud Build.
Ambiente padrão do App Engine:
O ambiente padrão do App Engine usa a conta de serviço do Cloud Build para
criar e implantar seus aplicativos, incluindo a integração de
dependências armazenadas no Artifact Registry.
Se o App Engine e o Artifact Registry estiverem no mesmo
Google Cloud projeto, a conta de serviço terá as permissões
necessárias para fazer o download de repositórios.
Se o App Engine e o Artifact Registry estiverem em projetos diferentes,
conceda acesso ao repositório à conta de serviço.
Para fornecer acesso somente leitura para o download de dependências, conceda o
papel de leitor do Artifact Registry à conta de serviço do
Cloud Build.
Se você também usa o Cloud Build para fazer upload de artefatos para repositórios,
conceda a função de escritor do Artifact Registry à conta de serviço do Cloud Build.
Configurar o acesso a dependências
Para aplicativos de ambiente padrão, consulte a documentação do ambiente padrão do App Engine para
instruções de configuração do npm e do Python.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-18 UTC."],[[["\u003cp\u003eArtifact Registry allows you to store dependencies for your App Engine applications.\u003c/p\u003e\n"],["\u003cp\u003eYou can declare dependencies within Artifact Registry for both Node.js and Python applications, and then leverage Cloud Build to deploy your application to App Engine.\u003c/p\u003e\n"],["\u003cp\u003eFor App Engine flexible environment, the default service account has permissions to pull containers from Artifact Registry when they're in the same project, and if using Cloud Build to containerize apps, you need to grant the Cloud Build service account the Artifact Registry Writer role.\u003c/p\u003e\n"],["\u003cp\u003eIn the App Engine standard environment, the Cloud Build service account handles building and deploying applications, including dependencies from Artifact Registry, and if they're in different projects, you'll need to grant the service account repository access, with options for read-only or writer roles.\u003c/p\u003e\n"],["\u003cp\u003eTo configure dependency access, you can refer to the App Engine standard environment documentation for npm and Python, and to include dependencies in Cloud Build runs, you can integrate with Cloud Build.\u003c/p\u003e\n"]]],[],null,["# Deploying to App Engine\n\nStore dependencies for your App Engine applications in Artifact Registry.\n\n- Declare dependencies in Artifact Registry in your Node.js and Python applications.\n- Deploy your application to App Engine leveraging Cloud Build.\n\n| **Note:** App Engine and Cloud Build create [Pub/Sub](/pubsub/docs) topics and subscriptions in your project for use in Google's internal analysis and maintenance of your container images. These Pub/Sub push subscriptions have `rpc://` URL targets.\n\nRequired permissions\n--------------------\n\nApp Engine flexible environment\n: If App Engine flexible environment and Artifact Registry are in the same project, the\n App Engine [default service account](/appengine/docs/standard/python/service-account) has permissions to\n pull containers from repositories.\n: If you also use Cloud Build to containerize your applications and store\n them in Artifact Registry, [grant](/artifact-registry/docs/access-control#grant) the Artifact Registry Writer role\n to the Cloud Build service account.\n\nApp Engine standard environment:\n: App Engine standard environment uses the [Cloud Build service account](/build/docs/cloud-build-service-account) to\n build and deploy your applications, including integration of\n dependencies stored in Artifact Registry.\n\n - If App Engine and Artifact Registry are in the same Google Cloud project, the service account has the necessary permissions to download from repositories.\n - If App Engine and Artifact Registry are in different projects, you must grant repository access to the service account.\n - To provide read-only access for downloading dependencies, [grant](/artifact-registry/docs/access-control#grant) the Artifact Registry Reader role to the Cloud Build service account.\n - If you also use Cloud Build to upload artifacts to repositories, [grant](/artifact-registry/docs/access-control#grant) the Artifact Registry Writer role to the Cloud Build service account.\n\nConfigure access to dependencies\n--------------------------------\n\nFor standard environment applications, see the App Engine standard environment documentation for\n[npm](/appengine/docs/standard/nodejs/specifying-dependencies#private_dependencies_with_artifact_registry) and [Python](/appengine/docs/standard/python3/specifying-dependencies#private_dependencies_with_artifact_registry) configuration instructions.\n\nTo include dependencies in builds you run with Cloud Build, see\n[Integrating with Cloud Build](/artifact-registry/docs/configure-cloud-build)."]]
