Tags: google-marketing-solutions/crmint
Tags
New architecture CRMint 3.0 CRMint 2.0 is deploying on App Engine standard, which comes with its limitations. CRMint 3.0 will deploy on Cloud Run and is a completely new stack, to give more flexibility & security to our users, including: - Docker containers - Docker Compose to run CRMint locally and customize it - Cloud Build to build images from Dockerfiles - Cloud Run for the services (frontend, controller and jobs) - Load Balancer to route requests to the right service - Locally-signed SSL Certificate for development - Trusted SSL Certificate managed by Google Cloud for production - Identity-Aware Proxy to secure the access to the CRMint app - Possibility to use a custom domain to integrate CRMint into your tools stack (e.g. `https://crmint.example.com`) - Terraform to setup and manage the infrastructure Roadmap to complete this new architecture: - [x] ~Dockerfiles~ - [x] ~Update `docker-compose.yaml`~ - [x] ~Cloud Build integration to build Docker images~ - [x] ~Migrate infrastructure setup to Terraform~ - [x] ~Migrate the pubsub setup to Terraform~ - [x] ~Activate needed APIs using Terraform~ - [x] ~Setup VPC using Terraform~ - [x] ~Setup Cloud Scheduler using Terraform~ - [x] ~Setup Cloud Build private pool using Terraform~ - [x] ~Run database initialization in Cloud Build~ - [x] ~Clean unused setup/deploy code from the CLI~ - [x] ~Clean up stage file logic now that we are using `-var-file` with Terraform~ - [x] ~Move "reset-pipelines" to Cloud Build~ - [x] ~Support multiple deployments with Terraform workspaces~ - [x] ~Access the UI without a custom domain~ - [x] ~Add a `crmint bundle update [v*|latest]` command to deploy new images to Cloud Run~ - [x] ~Add a `crmint bundle allow-users [email1,email2]` command to update IAP and give access to new users~ - [x] ~Migrate the Insight token to an env~ - [x] ~Migrate the app title to an env~ - [x] ~Migrate the email notification to a log-based alert~ - [x] ~Embed the check for minimal IAM roles to deploy CRMint into the automated checklist~ - [x] ~Update the README, public documentation and guides~ - [x] ~Document the IAP "Make external" config if they want to open access to user with emails outside their Google Workspace organization (in which the GCP project belongs)~ - [ ] Update the GitHub wiki once it has been merged into master PiperOrigin-RevId: 492248943
PreviousNext