environments/sigilstack.yaml.j2 at main · sigilstack/environments · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
terraform:
  worker_options:
    aws_region: us-east-1
    # configure via aws credentials file
    aws_profile: terraform
    backend: s3
    backend_bucket: sigilstack-state
    provider_cache: ./.cache

  definitions:
    # bootstrap will handle managing the state bucket and related resources
    # bootstrap:

    # dns will handle the management of all DNS zones and one-off DNS records
    coredns:
      {% if var.local == "true" %}
      path: ../worker-definitions/
      {% else %}
      path: git@github.com:sigilstack/worker-definitions.git
      {% endif %}
      remote_path_options:
        branch: main
        sub_path: coredns
      terraform_vars:
        cloudflare_account_name: "sigilstack"

  providers:
      aws:
        requirements:
          version: 5.99.1
        config_blocks:
          default_tags:
            tags:
              terraform: "true"
              deployment: "sigilstack"
              environment: "prodish"

      # Used to read DNS records as a data source, this provider is rough, it sometimes likes
      # to return empty results, or truncate results, so we use it with care, no, not really, we
      # just use it carelessly. What could go wrong?
      dns:
        requirements:
          version: 3.4.3

      cloudflare:
        requirements:
          version: 5.5.0
          source: "cloudflare/cloudflare"

      'null':
        requirements:
          version: 3.2.4