This page explains how to create and management deployments for your Google Chat app. By maintaining different deployments, you can better manage each phase of your Chat app's lifecycle and safely release changes to production.
Create deployments for each phase of the app lifecycle
To manage your Chat app throughout its lifecycle, we recommend that you create and deploy a Chat app for each of the following environments:
- Development: The environment that you use to work on changes. If needed, you can use the head deployment or run this environment locally.
- Staging: The environment that you deploy to trusted testers for end-to-end testing. This environment should be as close to production as possible.
- Production: The environment that you deploy to end users by publishing your Chat app to the Google Workspace Marketplace.
For each Chat app that you deploy, you must create a Google Cloud project. When you configure the Chat API in each Cloud project, consider using a distinct app name, avatar URL, and description so that you can better distinguish between the Chat apps in Google Chat.
In the following example, the Chat app
Task app is built on HTTP and uses different endpoints to deploy to
development, staging, and production:
|Cloud project name
|Dev Task app
|Staging Task app
Manage deployments based on your Chat app architecture
The following table includes additional considerations when managing deployments for specific Chat app architectures:
|Google Apps Script
|You should use a different Pub/Sub topic for each deployment.
- Test interactive features for Google Chat apps
- Publish Google Chat apps
- Create and manage Apps Script deployments
- Choose a Chat app architecture