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
+34-2Lines changed: 34 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,36 @@ Go to GitHub and create a new app. Beware you can create apps your organization
62
62
63
63
### Setup terraform module
64
64
65
-
1. Create a terraform workspace and initiate the module, see the examples for more details.
65
+
First you need to download the lambda's releases. THe lambda code is available as a GitHub release asset. Downloading can be done with the provided terraform module for example. Create in an empty workspace a terraform module:
66
+
67
+
```terraform
68
+
module "lambdas" {
69
+
source = "../../../modules/download-lambda"
70
+
lambdas = [
71
+
{
72
+
name = "webhook"
73
+
tag = "v0.0.0-beta"
74
+
},
75
+
{
76
+
name = "runners"
77
+
tag = "v0.0.0-beta"
78
+
},
79
+
{
80
+
name = "runner-binaries-syncer"
81
+
tag = "v0.0.0-beta"
82
+
}
83
+
]
84
+
}
85
+
86
+
output "files" {
87
+
value = module.lambdas.files
88
+
}
89
+
```
90
+
91
+
Next run `terraform init && terraform apply` as result the lambdas will be download to the same directory.
92
+
93
+
94
+
Next create a second terraform workspace and initiate the module, see the examples for more details.
3.Check the terraform output for the API gateway url, which you need in the next step.
128
+
Check the terraform output for the API gateway url, which you need in the next step. The lambda for syncing the GitHub distribution will be executed by a trigger via Cloud Watch. To ensure the binary is cached, trigger the `runner-binaries-syncer` manually. The payload does not matter.
0 commit comments