Closed snekiam closed 3 years ago
Use the INSTANCE_NAME from secrets to deploy to gcp. Updated the cron to update SSL certs to output to stdout, which is logged by docker
This doesn't change the way the api runs locally, it'll have to be tested on deploy.
formatting help: - [x] means "checked' and - [ ] means "unchecked"
- [x]
- [ ]
[ ] I documented my code according to the Google Python Style Guide
[ ] I ran ./build_docs.sh and the docs look fine
./build_docs.sh
[ ] I ran ./type_check.sh and got no errors
./type_check.sh
[ ] I ran ./format.sh because it automatically cleans my code for me 😄
./format.sh
[ ] I ran ./lint.sh to check for what "format" missed
./lint.sh
[ ] I added my tests to the /tests directory
/tests
[ ] I ran ./run_tests.sh and all the tests pass
./run_tests.sh
Kudos, SonarCloud Quality Gate passed!
0 Bugs 0 Vulnerabilities (and 0 Security Hotspots to review) 0 Code Smells
No Coverage information No Duplication information
What's New?
Use the INSTANCE_NAME from secrets to deploy to gcp. Updated the cron to update SSL certs to output to stdout, which is logged by docker
Fixes (works toward) #188
Type of change (pick-one)
How Has This Been Tested?
This doesn't change the way the api runs locally, it'll have to be tested on deploy.
Checklist (check-all-before-merge)
formatting help:
- [x]
means "checked' and- [ ]
means "unchecked"[ ] I documented my code according to the Google Python Style Guide
[ ] I ran
./build_docs.sh
and the docs look fine[ ] I ran
./type_check.sh
and got no errors[ ] I ran
./format.sh
because it automatically cleans my code for me 😄[ ] I ran
./lint.sh
to check for what "format" missed[ ] I added my tests to the
/tests
directory[ ] I ran
./run_tests.sh
and all the tests pass