mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 09:17:43 +03:00
5f75e9d1a0
Warm up local caches by building dev-env and current daml master This is allowed to fail, as we still want to have CI machines around, even when their caches are only warmed up halfway. Afterwards, we purge old agents that might still be around, that didn't unregister themselves This depends on #402 to be merged, as otherwise purge_old_agents.py can't be found obviously. |
||
|---|---|---|
| .. | ||
| modules/gcp_cdn_bucket | ||
| .gitignore | ||
| apply | ||
| bazel_cache.tf | ||
| main.tf | ||
| nix_cache.tf | ||
| README.md | ||
| vsts_agent_linux_startup.sh | ||
| vsts_agent_linux.tf | ||
| writer.tf | ||
DAML
This is the terraform code used by the DAML repository to deploy supporting infrastructure such as the Bazel and Nix caches.
Setup
To deploy the infrastructure changes, you will to get access to the
da-dev-gcp-daml-language Google project from IT. Then run
gcloud auth login to configure the local credentials.
Deployment
All the infrastructure is currently deployed using Terraform. For convenience we have a little wrapper script that you can run to apply the latest changes:
$ ./apply
Writer service-account key
To avoid holding the secret key into the store, creating the key has to be done through the UI.
This can be done here: https://console.cloud.google.com/iam-admin/serviceaccounts/details/104272946446260011088?project=da-dev-gcp-daml-language