Deploy to cloud.gov

[lbeaufort]

Summary of changes

• Made sure naming conventions for apps and services make sense/are consistent across apps (documented here: https://docs.google.com/spreadsheets/d/1P-tA0xVnlVDya4TLj5hkRxyenBHl7ceLbrIUI_HmNus/edit#gid=0)
• Made production settings file with debug=False (and possibly CORS_ALLOWED_ORIGINS)
• Removed DJANGO_SECRET_KEY from settings
• Set DJANGO_SECRET_KEY in cloud.gov dev/stage/prod envs. Put in follow-up tickets to rotate.
• Restored full database backup to dev/stage/prod
• Hooked up application and database with dj-database-url (uses built-in $DATABASE_URL - see https://docs.cloudfoundry.org/devguide/deploy-apps/environment-variable.html#DATABASE-URL
• Moved requirements.txt and requirements-test.txt to root directory
• Added wait_for_db in deploy command and made sure it works
• Made deploy task
• Added deploy task to CircleCI
• Added service keys for dev/stage/prod, CF username/password env vars to Circle for dev/stage/prod (see README)
• Added $DATABASE_URL env var to CircleCI
• Dockerfile changes
• Renamed FECFILE_DB_NAME to FECFILE_TEST_DB_NAME
• Made sure deploy tasks are in alignment in web app and api (https://github.com/fecgov/fecfile-web-app/pull/85/files)
• General code cleanup

Steps to test (QA)

Testing URLS
https://fecfile-web-api-dev.app.cloud.gov/api/v1/token/obtain
https://fecfile-web-api-stage.app.cloud.gov/api/v1/token/obtain
https://fecfile-web-api-prod.app.cloud.gov/api/v1/token/obtain

Steps to test/additional developer information (devs)

Deploy with invoke

• Log in to cloud.gov with cf login --sso
• invoke deploy --space dev

Deploy with CircleCI

• Make a copy of this branch
• Change deploy rules to deploy your branch
• Commit/push to github

Locally

• Set DATABASE_URL?
• Run with Docker

(Optional) Create RDS

• cf create-service aws-rds small-psql-redundant fecfile-api-rds
• Wait for db creation
• Bind to app in manifest, redeploy

(Optional) Restore database from backup

• Get database dump files from Google drive, see Matt for password
• See https://cloud.gov/docs/services/relational-database/ and https://github.com/fecgov/fec-cms/wiki/Backup-or-Restore-Wagtail-PostgreSQL-database-in-dev,-staging,-or-production but I used the service connect plugin
• cf connect-to-service -no-client fecfile-web-api fecfile-api-rds
• New tab
• psql --dbname (from ssh window) --host localhost --port (from ssh window) --username (from ssh window) < fec_clean_dev_db_backup-20211227.sql

Testing URLS
https://fecfile-web-api-dev.app.cloud.gov/api/v1/token/obtain
https://fecfile-web-api-stage.app.cloud.gov/api/v1/token/obtain
https://fecfile-web-api-prod.app.cloud.gov/api/v1/token/obtain

[albertcrowley]

I put inline comments in the PR. The summary is:

• I have a question about the Python version we should be using in general for our CI and dev containers.
• I'm seeing CORS errors in the web console when talking to the cloud.gov API so we need to either fix that up or spin it out to a new issue for later.

[mjtravers]

That's a lot of stuff. Good code clean up, too.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

81.2% Coverage
0.0% Duplication