1879170 - stand up a LandoAPI container for Lando-Treestatus

Status: RESOLVED FIXED

(Cloud Services :: Operations: LandoAPI, task)

Description

[Connor Sheehan [:sheehan]]

After some deliberation on the best way to deploy Lando-Treestatus, it was decided that we should stand up a separate container for the Treestatus API, with a distinct domain, which allows us to avoid needing to namespace API requests under /treestatus/. This makes the migration day tasks a simple change to DNS, and should avoid cross contamination between Lando and Treestatus when either is under high load.

I've completed the work to move the Treestatus API endpoints into their own container. To deploy this to production we will need to deploy the latest Treestatus branch updates to the development branch on each of LandoAPI and LandoUI, and make the following changes to the CloudOps infra configs:

• Create a second LandoAPI container with the same configuration as the regular LandoAPI container, except with the TREESTATUS_APP environment variable set to 1 on startup. This will load the Treestatus API endpoints instead of the standard LandoAPI endpoints.
• Add a new domain for the Lando-Treestatus specific endpoint and point it at the new container.
• Add a TREESTATUS_URL environment variable to the LandoUI container that points to the new domain.

I'd like to deploy these changes to the dev environment first, and then deploy to production once we have confirmation that everything is working as expected.

Comment 1

[Dustin Lactin [:dlactin]]

A new deployment was created with the requested parameters. Pending review.

Comment 2

[Connor Sheehan [:sheehan]]

Attachment: GitHub Pull Request

Comment 3

[Dustin Lactin [:dlactin]]

PR has been merged, landoapi-dev was deploying from this branch but has been reset back to the master branch now.

Comment 4

[Dustin Lactin [:dlactin]]

Treestatus changes for prod have been merged and deployed.