|
3 | 3 | | description | status |
|
4 | 4 | |------------ | ----------- |
|
5 | 5 | | latest commit | 
|
6 |
| -| latest pull request |  |
7 | 6 | | development release | 
|
8 | 7 | | production release | 
|
9 | 8 |
|
@@ -54,30 +53,28 @@ to rebuild.
|
54 | 53 |
|
55 | 54 | If you do need to deploy manually (as is currently required for production), you can install
|
56 | 55 | [act](https://github.com/nektos/act) on a local machine, and run:
|
57 |
| -`act --secret-file config/secrets.dev -j dev-build-and-deploy` or |
58 |
| -`act --secret-file config/secrets.prod -j prod-build-and-deploy`. |
| 56 | +`act --secret-file config/secrets -j dev-build-and-deploy` or |
| 57 | +`act --secret-file config/secrets -j prod-build-and-deploy`. |
59 | 58 |
|
60 | 59 | You'll also need to set your secrets file to contain the following environmental variables:
|
61 | 60 |
|
62 | 61 | ```
|
| 62 | +# these are needed to invoke `act --secret-file config/secrets -j dev-build-and-deploy` |
63 | 63 | DEVELOPMENT_AWS_ACCESS_KEY_ID=...
|
64 | 64 | DEVELOPMENT_AWS_SECRET_ACCESS_KEY=...
|
65 | 65 | DEVELOPMENT_AWS_CDN_BUCKET_NAME=...
|
66 | 66 | DEVELOPMENT_AUTH0_CLIENT_ID=...
|
67 | 67 | DEVELOPMENT_AUTH0_CLIENT_SECRET=...
|
68 |
| -``` |
69 |
| - |
70 |
| -Or: |
71 | 68 |
|
72 |
| -``` |
| 69 | +# these are needed to invoke `act --secret-file config/secrets -j prod-build-and-deploy` |
73 | 70 | PRODUCTION_AWS_ACCESS_KEY_ID=...
|
74 | 71 | PRODUCTION_AWS_SECRET_ACCESS_KEY=...
|
75 | 72 | PRODUCTION_AWS_CDN_BUCKET_NAME=...
|
76 | 73 | PRODUCTION_AUTH0_CLIENT_ID=...
|
77 | 74 | PRODUCTION_AUTH0_CLIENT_SECRET=...
|
78 | 75 | ```
|
79 | 76 |
|
80 |
| -Contact a member of the Mozilla-IAM team for a copy of these credentials, or push to the repo and request them |
| 77 | +Contact a member of the Mozilla-IAM team for a copy of these credentials, or push to the repo and create a release |
81 | 78 | to deploy.
|
82 | 79 |
|
83 | 80 | ## Coding standards
|
@@ -133,3 +130,20 @@ Auto-login Settings screen. Allows user to enable or disable auto-login.
|
133 | 130 | ### account_verification=true
|
134 | 131 |
|
135 | 132 | This is a specific parameter that is set when the log in screen is used for _account verification_.
|
| 133 | + |
| 134 | +## Backend setup |
| 135 | + |
| 136 | +First, run the CloudFormation template in AWS. Currently, this is done in the `infosec-dev` and `infosec-prod` AWS accounts. |
| 137 | +This will generate the `environment_AWS_ACCESS_KEY_ID` and `environment_AWS_SECRET_ACCESS_KEY` values needed to run `act` or |
| 138 | +invoke the GitHub Action. |
| 139 | + |
| 140 | +Secondly, create an Application in Auth0 with the correct scopes to the Auth0 Management API: |
| 141 | + |
| 142 | +application name: `github.com/mozilla-iam/auth0-custom-lock` |
| 143 | +application type: Machine to Machine |
| 144 | +description: `Owner: Mozilla-IAM (Your Name)` |
| 145 | +apis: Auth0 Management API |
| 146 | +scopes: `read:clients`, `update:clients`, `read:client_keys`, `update:client_keys`, `update:tenant_settings` |
| 147 | + |
| 148 | +This will generate the `environment_AUTH0_CLIENT_ID` and `environment_AUTH0_CLIENT_SECRET` needed to run `a0deploy` inside |
| 149 | +the GitHub action. |
0 commit comments