Page MenuHomePhabricator

[feature-flags] Use default HTTP port for deployments
ClosedPublic

Authored by bartek on Sep 12 2023, 12:13 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 14, 8:16 AM
Unknown Object (File)
Wed, Nov 13, 7:00 PM
Unknown Object (File)
Mon, Nov 4, 3:39 AM
Unknown Object (File)
Mon, Oct 28, 6:44 PM
Unknown Object (File)
Sun, Oct 27, 4:26 PM
Unknown Object (File)
Sun, Oct 27, 4:26 PM
Unknown Object (File)
Sun, Oct 27, 4:26 PM
Unknown Object (File)
Sun, Oct 27, 4:26 PM
Subscribers

Details

Summary

Deploy feature-flags service with new default HTTP port

NOTE: Applying the terraform changes requires rebuilding the docker image first! See the test plan.

Depends on D9138

Test Plan

On Staging:

  1. Build new docker image for feature-flags (latest tag)
  2. Apply terraform

Repeat on prod right before landing, with 0.1.1 docker tag

In case of problems, revert this and terraform apply again - this will revert deployment back to the existing v0.1

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.Sep 12 2023, 12:22 AM
bartek edited the test plan for this revision. (Show Details)

Should we also update the docker-compose.yml to use the new port?

About the applying terraform issue: maybe I'm misunderstanding something but couldn't we just bump the service version?

Use separate tag for staging, bump prod version

Should we also update the docker-compose.yml to use the new port?

This revision is now accepted and ready to land.Sep 13 2023, 12:44 AM

Should we also update the docker-compose.yml to use the new port?

yes, I forgot to change it 🙄

Update port in docker-compose