Skip to content

Commit

Permalink
fix: replace secrets with every Cloud Build deployment
Browse files Browse the repository at this point in the history
  • Loading branch information
ngurenyaga committed Jul 14, 2021
1 parent 46c5ec0 commit 0691e36
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 5 deletions.
6 changes: 2 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,5 @@ your browser and go to ``http://127.0.0.1:8025``
Deployment
----------

This application can be deployed via:

* Heroku: <http://cookiecutter-django.readthedocs.io/en/latest/deployment-on-heroku.html>
* Docker Compose: <http://cookiecutter-django.readthedocs.io/en/latest/deployment-with-docker.html>
This application is deployed via Google Cloud Build ( <https://cloud.google.com/build> ) to Google Cloud Run ( <https://cloud.google.com/run> ).
There's a `cloudbuild.yaml` file in the home folder. Secrets (e.g production settings) are managed with Google Secret Manager ( <https://cloud.google.com/secret-manager> ).
2 changes: 1 addition & 1 deletion cloudbuild.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ steps:
'--max-instances', '4',
'--memory', '256M',
'--cpu', '1',
'--update-secrets', '/tmp/secrets/.env=mle_django_settings:latest'
'--set-secrets', '/tmp/secrets/.env=mle_django_settings:latest'
]

images:
Expand Down

0 comments on commit 0691e36

Please sign in to comment.