You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -14,17 +14,17 @@ self-service update.
14
14
# Workflow
15
15
16
16
To deploy an updated data version to the Agora development database
17
-
1. Increment `data-version` in `data-manifest.json` on the `develop` branch.
17
+
1. Increment `data_version` in `data-manifest.json` on the `develop` branch.
18
18
2. Commit the change
19
19
3. The Github action CI system automatically updates the dev DB
20
20
21
21
22
22
To deploy an updated data version to the Agora staging database:
23
-
1. Merge the data-version update from the dev branch to the staging branch.
23
+
1. Merge the data_version update from the dev branch to the staging branch.
24
24
2. The Github action CI system automatically updates the dev DB
25
25
26
26
To deploy an updated data version to the Agora production database:
27
-
1. Merge the data-version update from the staging branch to the production branch.
27
+
1. Merge the data_version update from the staging branch to the production branch.
28
28
2. The Github action CI system automatically updates the dev DB
29
29
30
30
@@ -54,21 +54,21 @@ Context specific secrets for each environment that corresponds to a git branch (
54
54
55
55
## Self hosted runners
56
56
57
-
[agora2-infra] repository deploys a bastian host in AWS for each environment which have access to
57
+
[agora-infra-v3] repository deploys a bastian host in AWS for each environment which have access to
58
58
the databases. We manually configure a [Github self-hosted runner](https://docs.github.com/en/actions/hosting-your-own-runners)
59
59
for each bastian host, a label is applied to each runner to match the corresponding git branch name (develop/staging/prod).
60
60
61
61
Each runner corresponds to an environment which corresponds to a git branch. The update is
62
62
executed from these runners. When a push happens on a branch (i.e. develop), the update
63
-
is executed on the `agora-bastian-develop`runner which in turn updates the development database.
63
+
is executed on the self-hosted runner with the `develop`label, which in turn updates the development database.
64
64
65
65
66
66
![alt text][self_hosted_runners]
67
67
68
68
69
69
### Setup self hosted runners
70
70
71
-
Github self hosted runners are deployed with a [Sceptre template config file])(https://github.com/Sage-Bionetworks/agora2-infra/blob/main/config/agoradev/develop/agora-bastian.yaml).
71
+
Github self hosted runners are deployed with [Cloudformation](https://github.com/Sage-Bionetworks-IT/agora-infra-v3/blob/dev/src/bastion_stack.py).
72
72
73
73
Self Hosted Runner setup:
74
74
* Deploy the template to the Agora AWS account.
@@ -121,5 +121,5 @@ Enter name of work folder: [press Enter for _work]
0 commit comments