Deployment Workaround for 2018 TLS 1.2 Compatibility Issue

Background

On December 01, 2018 the EAS source code version control provider, Bitbucket, disabled support of TLSv1 and TLSv1.1 and began requiring secure connections through TLS 1.2.

The EAS stack does not currently support TLS 1.2 (as of December 2018). While this issue is being resolved there is a workaround for deploying EAS source code.

See also EAS Issue 251: Create deployment workaround for TLS 1.2 compatibility problem

Step-by-step workaround

1. Manually download required files to a computer that has FTP access to the EAS servers.

A. Download Repositories

There are three EAS repositories to download.

The names of the repository folders are important. It is recommended that the repositories be download from a web browser, accepting the default name for the downloaded file.

1. https://bitbucket.org/sfgovdt/eas/
2. https://bitbucket.org/sfgovdt/sfeas_config/
3. https://bitbucket.org/sfgovdt/thirdparty/

The downloaded files will look something like this:

            sfgovdt-eas-caaed66d58b3.tar.gz
            sfgovdt-sfeas_config-ff939b913451.tar.gz
            sfgovdt-thirdparty-8a1b00afcb15.tar

Uncompress both the 'gz' and 'tar' files (a two-step process in Windows Explorer).

This will result in three folders, such as these:

            sfgovdt-eas-caaed66d58b3
            sfgovdt-sfeas_config-ff939b913451
            sfgovdt-thirdparty-8a1b00afcb15

Again, the folder names are important so do not change them.

B. Download Workaround Deployment Scripts

Download the latest version of these five files from the /eas/web/bin/ source folder
https://bitbucket.org/sfgovdt/eas/src/default/web/bin/

1. deploy_eas_init.sh
2. deploy_eas_source.py
3. deploy_eas.sh
4. set_eas_mode.sh
5. set_eas_env.sh

2. FTP the 3 folders and 5 files to /var/tmp of relevant server(s).

3. Connect to relevant server.

    cd /var/tmp

4. Change permissions of files

    sudo chmod u+x *.sh

5. Move files to correct location

    sudo cp deploy_eas_init.sh /var/www/html
    sudo cp deploy_eas_source.py /var/www/html
    sudo cp deploy_eas.sh /var/www/html
    sudo cp set_eas_mode.sh /var/www/html
    sudo cp set_eas_env.sh /var/www/html

(Leave the 3 repository folders in /var/tmp/.)

6. Run the deployment script as sudo

    cd /var/www/html
    sudo ./deploy_eas_init.sh <EAS_COMMIT> <CONFIG_COMMIT> <BITBUCKET_USER>

    For example,

    sudo ./deploy_eas_init.sh caaed66 ff939b9 dan-king

7. Confirm with tests and remove files/folders from /var/tmp/.

Related articles