[ATTENTION] New Process of Publishing Postgres Proxy Library

To all tv-sql-product users

Background

Artifactory had been deprecated following the migration to beiartf. Thus, Postgres proxy libraries publishing must also be migrated to beiartf.

As all of you know, currently the process of publishing Postgres proxy libraries are done from developers' laptops. We do not allow this kind of process anymore due to security concern because it means that engineers have direct write access to maven repository.

To solve this problem, Backend Infra had decided to create a new standard process to publish Postgres proxy libraries. The solution which we have designed leverage AWS CodeBuild and Terraform.

Deadline

August 1st, 2018.

You have 1 day left to implement the new process.

What you need to do

Setup CodeBuild project for each library

Please follow this guide to setup your CodeBuild project:
Postgres Proxy CodeBuild Publisher

If you encounter any issues during the setup, please contact us immediately.

Changes during the transition period

During the transition period, if you are still willing to publish proxy library from your local machine, there's a change in the command:

BEFORE:

./deploy_library.sh {TEAM}:{SUBDOMAIN}:{PROJECT} -r

AFTER: (USE THIS)

./deploy_library.sh {TEAM}:{SUBDOMAIN}:{PROJECT} -d

There will be a noticable delay, up to 30 minutes, for the newest published proxy binary to be available on beiartf S3. This old publishing method will be deprecated on August 1st 2018 so please run the setup as soon as possible.

Postgres Proxy Code Build Publisher - Note on Transition Period