daml/infra
Gary Verhaegen c762d491ea target s3 bucket with docs refresh script (#1287)
There is no simple way to configure GCS to serve the desired security
headers, so instead the script will keep updating the existing s3
bucket.

Consequent changes:

- Add aws cli tool to dev-env
- Remove docs bucket from Terraform
2019-05-21 22:26:07 +00:00
..
modules/gcp_cdn_bucket target s3 bucket with docs refresh script (#1287) 2019-05-21 22:26:07 +00:00
.gitignore open-sourcing daml 2019-04-04 09:33:38 +01:00
apply infra: add a VSTS windows agents (#368) 2019-04-18 11:20:57 +00:00
bazel_cache.tf infra: add some docs / comments (#796) 2019-05-01 15:54:09 +00:00
main.tf infra: add some docs / comments (#796) 2019-05-01 15:54:09 +00:00
nix_cache.tf infra: add some docs / comments (#796) 2019-05-01 15:54:09 +00:00
README.md infra: add some docs / comments (#796) 2019-05-01 15:54:09 +00:00
vsts_agent_linux_startup.sh [ci/linux] restart fluentd after installing (#1290) 2019-05-21 21:37:51 +00:00
vsts_agent_linux.tf CI linux agent changes (#509) 2019-04-16 11:35:46 +02:00
vsts_agent_windows.tf Install the Windows SDK on CI nodes (#1272) 2019-05-21 13:42:49 +02:00
writer.tf open-sourcing daml 2019-04-04 09:33:38 +01:00

DAML

This is the terraform code used by the DAML repository to deploy supporting infrastructure such as the Bazel caches, Nix caches and Azure Pipeline (VSTS) Agents.

Setup

To deploy the infrastructure changes, you will to get access to the da-dev-gcp-daml-language Google project from DA 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