app/cloudfoundry_config.py

"""
Extracts cloudfoundry config from its json and populates the environment variables that we would expect to be populated
on local/aws boxes
"""

import json
import os


def extract_cloudfoundry_config():
    vcap_services = json.loads(os.environ['VCAP_SERVICES'])
    set_config_env_vars(vcap_services)


def set_config_env_vars(vcap_services):
    # Postgres config
    os.environ['SQLALCHEMY_DATABASE_URI'] = vcap_services['postgres'][0]['credentials']['uri'].replace('postgres',
                                                                                                       'postgresql')

    vcap_application = json.loads(os.environ['VCAP_APPLICATION'])
    os.environ['NOTIFY_ENVIRONMENT'] = vcap_application['space_name']
    os.environ['NOTIFY_LOG_PATH'] = '/home/vcap/logs/app.log'
Run API on Paas 2016-12-08 12:12:45 +00:00			`"""`
			`Extracts cloudfoundry config from its json and populates the environment variables that we would expect to be populated`
			`on local/aws boxes`
			`"""`

			`import json`
Run auto-correct on app/ and tests/ 2021-03-10 13:55:06 +00:00			`import os`
Run API on Paas 2016-12-08 12:12:45 +00:00

			`def extract_cloudfoundry_config():`
			`vcap_services = json.loads(os.environ['VCAP_SERVICES'])`
			`set_config_env_vars(vcap_services)`


			`def set_config_env_vars(vcap_services):`
			`# Postgres config`
SQLAlchemy 1.4 requires SQLALCHEMY_DATABASE_URI to use `postgresql` rather than `postgres` for the connection uri to the database. When deploying to paas the database postgres environment variables are set using VCAP_SERVICES provided by PaaS. When we start up the app and set the properties we need to replace the postgres string with postgresql for the app to start up properly. This wasn't caught locally or with the unit tests because we were setting this property with postgresql. 2021-04-29 13:49:37 +01:00			`os.environ['SQLALCHEMY_DATABASE_URI'] = vcap_services['postgres'][0]['credentials']['uri'].replace('postgres',`
			`'postgresql')`
Run API on Paas 2016-12-08 12:12:45 +00:00
			`vcap_application = json.loads(os.environ['VCAP_APPLICATION'])`
			`os.environ['NOTIFY_ENVIRONMENT'] = vcap_application['space_name']`
don't capture logs directly from stdout previously in run_app_paas.sh, we captured stdout from the app and piped that into the log file. However, this came up with a bunch of problems, mainly: * exceptions with stack traces often weren't formatted properly, and kibana could not parse them * celery logs were duplicated - we'd collect both the json logs and the human readable stdout logs. instead, with the updated utils library, we can use that to log json straight to the appropriate directory directly. 2017-07-31 13:28:34 +01:00			`os.environ['NOTIFY_LOG_PATH'] = '/home/vcap/logs/app.log'`