environment.py

from collections.abc import (
    Mapping,
)
import json
import os
import tomllib


def _pin(*path: str) -> str:
    """
    Return the version from the exact version specifier at the given path of
    keys in `pyproject.toml`. That file is the sole source of these versions
    because uv reads it directly, and because TOML offers no way of referring
    to a value defined elsewhere.
    """
    file_path = os.path.join(os.path.dirname(__file__), 'pyproject.toml')
    with open(file_path, 'rb') as f:
        node = tomllib.load(f)
    for key in path:
        node = node[key]
    assert isinstance(node, str), node
    prefix = '=='
    assert node.startswith(prefix), node
    version = node.removeprefix(prefix)
    return version


def env() -> Mapping[str, str | None]:
    """
    Returns a dictionary that maps environment variable names to values. The
    values are either None or strings. String values can contain references to
    other environment variables in the form `{FOO}` where FOO is the name of an
    environment variable. See

    https://docs.python.org/3.12/library/string.html#format-string-syntax

    for the concrete syntax. These references will be resolved *after* the
    overall environment has been compiled by merging all relevant
    `environment.py` and `environment.local.py` files.

    Entries with a `None` value will be excluded from the environment. They
    can be used to document a variable without a default value in which case
    other, more specific `environment.py` or `environment.local.py` files must
    provide the value.
    """
    xdg_data_home = os.environ.get('XDG_DATA_HOME',
                                   os.path.expanduser('~/.local/share'))
    return {
        # Only variables whose names start in `AZUL_` will be published to a
        # deployed Lambda. Note that by implication, `azul_` variables will not
        # be published, even though they are considered part of Azul. For secret
        # values that should not be printed or logged, use a variable name
        # containing any of the strings `secret`, `password` or `token`, either
        # upper or lower case. Think twice before publishing a variable
        # containing a secret.

        # Configure the catalogs to be managed by this Azul deployment. A
        # catalog is a group of indices populated from a particular source.
        #
        # The AZUL_CATALOGS variable must be a string containing a JSON object
        # of the following shape:
        #
        # {
        #   'name': {
        #       'atlas': 'bar',
        #       'internal': True,
        #       'mirror_limit': -1,
        #       'plugins': {
        #           plugin_type: {'name'=plugin_package},
        #           plugin_type: {'name'=plugin_package},
        #           ...
        #       }
        #       'sources': {
        #           source: {}
        #           ...
        #       }
        #   },
        #   ...
        # }
        #
        # The `atlas` and `name` properties follow the same, fairly restrictive
        # syntax defined by azul.Config.Catalog.validate_name. `plugin_type` is
        # the name of a child package of `azul.plugins` and `plugin_package` is
        # the name of a child package of that package. The `plugin_type` denotes
        # the purpose (like accessing a repository or transforming metadata) and
        # `plugin_package` denotes the concrete implementation of how to fulfill
        # that purpose.
        #
        # Files larger than `mirror_limit` will not be mirrored for that
        # catalog. This property may be absent or null, in which case all files
        # will be mirrored for that catalog, or negative, in which case no files
        # will be mirrored for that catalog.
        #
        # The first catalog listed is the default catalog.
        #
        # A source represents a TDR snapshot or canned staging area to index.
        # Each source is a string matching the following EBNF grammar:
        #
        # source = TDR source | canned source | DSS source;
        #
        # TDR source = 'tdr:', Google Cloud project name,
        #              ':', TDR dataset or snapshot name
        #
        # canned source = 'https://github.com',
        #                 '/', owner,
        #                 '/', repo,
        #                 '/tree/', ref,
        #                 ['/', path]
        #
        # DSS source = 'dss.data.humancellatlas.org/v1',
        #
        # `ref` can be a branch, tag, or commit SHA. If `ref` contains special
        # characters like `/`, '?` or `#` they must be URL-encoded.
        #
        # Examples:
        #
        # tdr:broad-jade-dev-data:hca_mvp:/1
        # https://github.com/HumanCellAtlas/schema-test-data/tree/de355ca/tests:2
        #
        # This variable tends to be large. If you get `Argument list too long`
        # after sourcing the environment, a last-resort option is to compress
        # the variable. The application automatically detects a compressed value
        # and decompresses it on the fly. If the uncompressed definition of this
        # variable is
        #
        # 'AZUL_CATALOGS': json.dumps({
        #   ...
        # }),
        #
        # the compressed version of that definition would be
        #
        # 'AZUL_CATALOGS': base64.b64encode(bz2.compress(json.dumps({
        #   ...
        # }).encode())).decode('ascii'),
        #
        'AZUL_CATALOGS': None,

        # The name of a catalog to perform reindex or other operational tasks on.
        # By default, these tasks are performed on all catalogs.
        #
        'azul_current_catalog': None,

        # A space-separated list of shell globs to match the sources in the
        # current catalog against, or "*" for all sources in the catalog. "*" is
        # the default, but it is not defined here so that the variable can
        # be interactively overridden when running jobs on GitLab.
        #
        # Only matching sources will be targeted when performing reindex or
        # other operational tasks. If no sources match, an error will be raised.
        #
        'azul_current_sources': None,

        # The Account ID number for AWS
        #
        'AZUL_AWS_ACCOUNT_ID': None,

        # The region of the Azul deployment. This variable is primarily used by
        # the AWS CLI, by TerraForm, botocore and boto3 but Azul references it
        # too. This variable is typically set in deployment-specific
        # environments.
        #
        'AWS_DEFAULT_REGION': None,

        # The name of the billing account that pays for this deployment.
        #
        'AZUL_BILLING': None,

        # The email address of a user that owns the cloud resources in the
        # current deployment. This will become the value of the Owner tag on all
        # resources.
        #
        'AZUL_OWNER': None,

        # An email address to subscribe to the SNS topic for monitoring
        # notifications in the current deployment. Warn all members of the group
        # to ignore any "Subscription Confirmation" emails and not to click the
        # "Confirm subscription" link contained within, since doing so would
        # confirm the subscription in a way that allows anyone with an
        # unsubscribe link to unsubscribe the entire group from the topic.
        # Instead, confirmation of the subscription should be done when prompted
        # to do so during the `make deploy` process.
        #
        'AZUL_MONITORING_EMAIL': None,

        # Controls the verbosity of application logs. Use 0 for no debug logging
        # 1 for debug logging by application code and info logging by other code
        # and 2 for debug logging by all code. This also controls app.debug, a
        # Chalice setting that causes an app to return a traceback in the body
        # of error responses: Setting AZUL_DEBUG to 0 disables the traceback
        # (app.debug = False), 1 or higher enable it (app.debug = True). See
        # https://github.com/aws/chalice#tutorial-error-messages for more.
        #
        'AZUL_DEBUG': '0',

        # Whether to create and populate an index for replica documents.
        'AZUL_ENABLE_REPLICAS': '1',

        # Maximum number of conflicts to allow before giving when writing
        # replica documents.
        'AZUL_REPLICA_CONFLICT_LIMIT': '10',

        # The name of the current deployment. This variable controls the name of
        # all cloud resources and is the main vehicle for isolating cloud
        # resources between deployments.
        #
        'AZUL_DEPLOYMENT_STAGE': None,

        # The Docker registry containing all 3rd party images used by this
        # project, including images used locally, in FROM clauses, for CI/CD or
        # GitLab. Must be empty or end in a slash. All references to images from
        # other parties must point at the registry defined here, ideally by
        # prefixing the image reference with a reference to this variable. The
        # registry and the images therein are managed by the `shared` TF
        # component, which copies images from the upstream registry into the
        # Azul registry.
        #
        # The image `<registry>/<username>/<repository>:<tag>`, is stored as
        # `${azul_docker_registry>}<registry>/<username>/<repository>:<tag>` in
        # the Azul registry. To disable the use of the Azul registry, set this
        # variable to the empty string.
        #
        'azul_docker_registry': '{AZUL_AWS_ACCOUNT_ID}.dkr.ecr.'
                                '{AWS_DEFAULT_REGION}.amazonaws.com/',

        # The platforms to build Lambda container images for, as a list of
        # Docker platform specifications separated by space. The first platform
        # in the list also determines the architecture of the deployed Lambda
        # function. Images will be built for the other platforms listed, but
        # those images will not be used by the deployment. A multi-platform
        # image list consisting of the specified platform-specific images will
        # also be pushed.
        #
        # On machines that support cross-platform image builds, this variable
        # can be overridden locally to build images for additional platforms. On
        # machines that don't support building the default platform, a different
        # one can be specified, e.g., 'linux/arm64'.
        #
        'azul_lambda_image_platforms': 'linux/amd64',

        # The version of Docker used throughout the system.
        #
        # This variable is not intended to be overridden per deployment or
        # locally.
        #
        # This variable is duplicated in a file called `environment.boot`
        # because it is referenced in the early stages of the GitLab build. The
        # next paragraph explains how to keep that file in sync.
        #
        # After modifying this variable, run `make docker_images.json` and
        # `make environment.boot`, in that order. Commit the resulting
        # changes. Ensure that the `shared` and `gitlab` components are
        # redeployed, and that the executor image is built and pushed (see
        # terraform/gitlab/runner/Dockerfile for how).
        #
        'azul_docker_version': '29.7.2',

        # The version of Python used throughout the system. Do not modify this
        # variable directly. It is derived from `requires-python` in
        # `pyproject.toml`, where the procedure for updating it is documented.
        #
        'azul_python_version': _pin('project', 'requires-python'),

        # The version of Terraform used throughout the system.
        #
        # This variable is not intended to be overridden per deployment or
        # locally.
        #
        # This variable is duplicated in a file called `environment.boot`
        # because it is referenced in the early stages of the GitLab build. The
        # next paragraph explains how to keep that file in sync.
        #
        # After modifying this variable, run `make environment.boot` and
        # `make -C terraform update_schema`, and commit the resulting changes.
        #
        'azul_terraform_version': '1.15.9',

        # The version of the AWS CLI v2 used throughout the system.
        #
        # This variable is not intended to be overridden per deployment or
        # locally.
        #
        # This variable is duplicated in a file called `environment.boot`
        # because it is referenced in the early stages of the GitLab build. The
        # next paragraph explains how to keep that file in sync.
        #
        # After modifying this variable, run `make environment.boot` and commit
        # the resulting changes.
        #
        'azul_awscli_version': '2.36.38',

        # The version of the GitHub CLI used in the `github_schedule` GitLab CI
        # job to create GitHub issues from the templates.
        #
        # This variable is not intended to be overridden per deployment or
        # locally.
        #
        # This variable is duplicated in a file called `environment.boot`
        # because it is referenced in the early stages of the GitLab build. The
        # next paragraph explains how to keep that file in sync.
        #
        # After modifying this variable, run `make environment.boot` and
        # `make gh_checksums`, and commit the resulting changes.
        #
        'azul_ghcli_version': '2.99.0',

        # The version of uv used to create the virtual environment and to
        # install dependencies into it. Do not modify this variable directly. It
        # is derived from `required-version` in `pyproject.toml`, where the
        # procedure for updating it is documented.
        #
        'azul_uv_version': _pin('tool', 'uv', 'required-version'),

        # A dictionary mapping the short name of each Docker image used in Azul
        # to its fully qualified name. Note that a change to any of the image
        # references below requires running `make docker_images.json` and
        # redeploying the `shared` TF component.

        'azul_docker_images': json.dumps({
            # See `azul_docker_version` above about what actions are required
            # after modifying this entry.
            'docker': {
                'ref': 'docker.io/library/docker:{azul_docker_version}',
                'url': 'https://hub.docker.com/_/docker'
            },
            # See `azul_python_version` above about what actions are required
            # after modifying this entry.
            'python': {
                'ref': 'docker.io/library/python:{azul_python_version}-slim-trixie',
                'url': 'https://hub.docker.com/_/python',
            },
            'pycharm': {
                'ref': 'docker.io/ucscgi/azul-pycharm:2025.2.6.1-87',
                'url': 'https://hub.docker.com/repository/docker/ucscgi/azul-pycharm',
                'is_custom': True
            },
            'opensearch': {
                'ref': 'docker.io/opensearchproject/opensearch:2.19.6',
                'url': 'https://hub.docker.com/r/opensearchproject/opensearch',
                'is_custom': False
            },
            'bigquery_emulator': {
                'ref': 'docker.io/ucscgi/azul-bigquery-emulator:0.4.4-70',
                'url': 'https://hub.docker.com/repository/docker/ucscgi/azul-bigquery-emulator',
                'is_custom': True
            },
            # Updating any of the four images below additionally requires
            # redeploying the `gitlab` TF component.
            'clamav': {
                'ref': 'docker.io/clamav/clamav:1.5.2-35',
                'url': 'https://hub.docker.com/r/clamav/clamav'
            },
            'gitlab': {
                'ref': 'docker.io/gitlab/gitlab-ce:19.3.1-ce.0',
                'url': 'https://hub.docker.com/r/gitlab/gitlab-ce'
            },
            'gitlab_runner': {
                'ref': 'docker.io/gitlab/gitlab-runner:ubuntu-v19.3.1',
                'url': 'https://hub.docker.com/r/gitlab/gitlab-runner'
            },
            'dind': {
                'ref': 'docker.io/library/docker:{azul_docker_version}-dind',
                'url': 'https://hub.docker.com/_/docker'
            },
            # The images below are not used within the security boundary:
            '_signing_proxy': {
                'ref': 'docker.io/cllunsford/aws-signing-proxy:0.2.2',
                'url': 'https://hub.docker.com/r/cllunsford/aws-signing-proxy'
            },
            '_cerebro': {
                'ref': 'docker.io/lmenezes/cerebro:0.9.4',
                'url': 'https://hub.docker.com/r/lmenezes/cerebro'
            },
            '_opensearch_dashboards': {
                'ref': 'docker.io/opensearchproject/opensearch-dashboards:2.19.3',
                'url': 'https://hub.docker.com/r/opensearchproject/opensearch-dashboards'
            }
        }),

        # Whether to enable direct access to objects in the DSS main bucket. If
        # 0, bundles and files are retrieved from the DSS using the GET
        # /bundles/{uuid} and GET /files/{UUID} endpoints. If 1, S3 GetObject
        # requests are made directly to the underlying bucket. This requires
        # intimate knowledge of DSS implementation details but was ten times
        # faster. Recent optimizations to the DSS (mainly, the delayed eviction
        # of metadata files from the checkout bucket made the performance gains
        # less dramatic but the first hit to a metadata file is still going to
        # be slow because the objects needs to be checked out. Aside from the
        # latency improvements on a single request, direct access also bypasses
        # DSS lambda concurrency limits, thereby increasing in the throughput of
        # the Azul indexer, which is especially noticeable during reindexing and
        # scale testing.
        #
        # More importantly, direct access needs to be enabled for deletions to
        # work properly as the Azul indexer needs to know the metadata of the
        # deleted bundle in order to place the correct tombstone contributions
        # into its index. Direct access is also required for the Azul service's
        # DSS files proxy and DOS/DRS endpoints. Disabling DSS direct access
        # will break these endpoints.
        #
        'AZUL_DSS_DIRECT_ACCESS': '0',

        # An optional ARN of a role to assume when directly accessing a DSS
        # bucket. This can be useful when the DSS buckets are not owned by the
        # same AWS account owning the current Azul deployment. If there is
        # another Azul deployment in the account owning the DSS bucket, the role
        # assumed by the other Azul indexer would be an obvious candidate for
        # the current deployment's indexer to assume for direct access.
        # Presumably that other indexer has sufficient privileges to directly
        # access the DSS buckets.
        #
        # The character '*' will be replaced with the name of the lambda wishing
        # to gain access. This parameterization can be used to have the indexer
        # lambda in the native deployment assume the role of the indexer lambda
        # in the foreign deployment, while the native service lambda assumes the
        # role of the foreign service lambda.
        #
        # If specified, this ARN must be of the following form:
        #
        # arn:aws:iam::ACCOUNT_ID:role/azul-*-DEPLOYMENT
        #
        # The only free variables are ACCOUNT_ID and DEPLOYMENT which are the
        # AWS account ID and the deployment stage of the Azul deployment that's
        # providing the role to be assumed.
        #
        'AZUL_DSS_DIRECT_ACCESS_ROLE': None,

        # The name of the hosted zone in Route 53 in which to create user
        # friendly domain names for various API gateways. This hosted zone will
        # have to be created manually prior to running `make deploy`. The value
        # is typically not deployment specific. A subdomain will automatically
        # be created for each deployment.
        'AZUL_DOMAIN_NAME': None,

        # An optional list of roles in other AWS accounts that can assume the
        # IAM role normally assumed by lambda functions in the active Azul
        # deployment.
        #
        # The syntax is `<account>[,<role>...][:<account>[,<role>...]...]` where
        # `<account>` is the numeric AWS account ID and `<role>` is a role name
        # with optional * or ? wildcards for the StringLike operator in IAM
        # conditions. Whitespace around separators and at the beginning or end
        # of the value are ignored.
        #
        # This parameter has profound security implications: the external role
        # can do anything an Azul lambda can do. The external account and any
        # principal with IAM access in that account, not just the specified
        # roles, must be fully trusted.
        #
        # This configuration is typically used to enable an external Azul
        # deployment to directly access the same DSS buckets the active
        # deployment has direct access to.
        #
        'AZUL_EXTERNAL_LAMBDA_ROLE_ASSUMPTORS': None,

        # The domain name of the HCA DRS endpoint. The service lambda serves
        # requests under both its canonical domain name as well as the domain
        # name given here. It is assumed that the parent domain of the given
        # domain is a hosted zone in Route 53 that we can create additional
        # certificate validation records in. If unset or set to empty string,
        # the service lambda will only serve requests under its canonical domain
        # name and no validation records will be created in hosted zones other
        # than the zone defined by AZUL_DOMAIN_NAME.
        #
        'AZUL_DRS_DOMAIN_NAME': '',

        # A template for the name of the Route 53 record set in the hosted zone
        # specified by AZUL_DOMAIN_NAME. The character '*' in the template will
        # be substituted with the name of the Lambda function, e.g. `indexer` or
        # `service`. May contain periods.
        #
        'AZUL_SUBDOMAIN_TEMPLATE': '*',

        # Boolean value, 0 to create public APIs, 1 to create private APIs that
        # can only be accessed from within the VPC or through the VPN tunnel
        # into the VPC.
        #
        'AZUL_PRIVATE_API': '0',

        # A prefix to be prepended to the names of AWS Lambda functions and
        # associated resources. Must not contain periods.
        #
        'AZUL_RESOURCE_PREFIX': 'azul',

        # The host and port of the OpenSearch instance to use. This takes
        # precedence over AZUL_OPENSEARCH_DOMAIN.
        #
        'AZUL_OPENSEARCH_ENDPOINT': None,

        # The name of the AWS-hosted OpenSearch instance (not a domain name)
        # to use. The given ES domain's endpoint will be looked up dynamically.
        #
        'AZUL_OPENSEARCH_DOMAIN': 'azul-index-{AZUL_DEPLOYMENT_STAGE}',

        # Boolean value, 1 to share `dev` ES domain, 0 to create your own
        #
        'AZUL_SHARE_OPENSEARCH_DOMAIN': '0',

        # The number of nodes in the AWS-hosted OpenSearch cluster
        #
        'AZUL_OPENSEARCH_INSTANCE_COUNT': None,

        # The EC2 instance type to use for a cluster node.
        #
        # Indexing performance benefits from the increased memory offered by the
        # `r` family, especially now that the number of shards is tied to the
        # indexer Lambda concurrency.
        #
        'AZUL_OPENSEARCH_INSTANCE_TYPE': None,

        # The size of the EBS volume backing each cluster node. Set to 0 when
        # using an instance type with SSD volumes.
        #
        'AZUL_OPENSEARCH_VOLUME_SIZE': '0',

        # OpenSearch operation timeout in seconds. Matches AWS' own timeout
        # on the ELB sitting in front of ES:
        #
        # https://forums.aws.amazon.com/thread.jspa?threadID=233378
        #
        'AZUL_OPENSEARCH_TIMEOUT': '60',

        # The number of workers pulling files from the DSS repository. There is
        # one such set of repository workers per index worker.
        #
        'AZUL_DSS_WORKERS': '8',

        # The number of workers pulling metadata from the TDR repository. There
        # is one such set of repository workers per index worker. Using one
        # worker as opposed to 8 (or 4) improved the indexing time noticeably
        # because it reduced retries due to exceeding BigQuery's limit on the #
        # of concurrent queries. Using two workers wasn't significantly faster.
        #
        'AZUL_TDR_WORKERS': '1',

        # The number of times a deployment has been destroyed and rebuilt. Some
        # services used by Azul do not support the case of a resource being
        # recreated under the same name as a previous incarnation. The name of
        # such resources will include this value, therefore making the names
        # distinct. If a deployment is being rebuilt, increment this value in
        # the deployment's `environment.py` file.
        #
        'AZUL_DEPLOYMENT_INCARNATION': '0',

        # The name of the Google Cloud project to host the Azul deployment.
        # There are two methods of authenticating with Google Cloud: setting the
        # GOOGLE_APPLICATION_CREDENTIALS environment variable to point to the
        # key file of a Google service account, or setting the application
        # default credentials using the `gcloud` CLI interactive login.
        #
        'GOOGLE_PROJECT': None,

        # The path of the directory where the Google Cloud Python libraries and
        # the Google Cloud CLI (gcloud) put their state. If this variable is not
        # set, the state is placed in ~/.config/gcloud by default. Since we want
        # to segregate this state per working copy and deployment, we set this
        # variable to the path of a deployment-specific directory in the working
        # copy. Note that this variable does not affect the Google Cloud
        # libraries for Go, or the Google Cloud provider for Terraform which
        # uses these Go libraries. Luckily, the Go libraries don't write any
        # state, they only read credentials from the location configured via
        # GOOGLE_APPLICATION_CREDENTIALS below.
        #
        'CLOUDSDK_CONFIG': '{project_root}/deployments/.active/.gcloud',

        # The path of a JSON file with credentials for an authorized user or a
        # service account. The Google Cloud libraries for Python and Go will
        # load the so-called ADC (Application-default credentials) from this
        # file and use them for any Google Cloud API requests. According to
        # Google documentation, if this variable is not set,
        # ~/.config/gcloud/application_default_credentials.json is used.
        # However, the Google Cloud SDK and Python libraries will only default
        # to that if CLOUDSDK_CONFIG is not set. If it is,
        # $CLOUDSDK_CONFIG/application_default_credentials.json is used. Since
        # the Go libraries are unaffected by CLOUDSDK_CONFIG, the officially
        # documented default applies. We'll work around the inconsistent
        # defaults by setting both variables explicitly.
        #
        # If the azul_google_user variable is set, the _login helper defined
        # in `environment` will populate this file with credentials (a
        # long-lived refresh token) for that user. It does so by logging that
        # user into Google Cloud, which requires a web browser. As a
        # convenience, and to avoid confusion, it will, at the same time,
        # provision credentials for the Google Cloud CLI, in a different file,
        # but also in the directory configured via CLOUDSDK_CONFIG above.
        #
        # To have a service account (as opposed to a user account) manage Google
        # Cloud resources, leave azul_google_user unset and change this variable
        # to point to a file with the private key of that service account. Note
        # that the service account would have to be different from the one whose
        # name is set in AZUL_GOOGLE_SERVICE_ACCOUNT. In fact, the service
        # account from this variable is used to manage those other service
        # accounts, so generally, it needs elevated permissions to the project.
        # We used to call this type of account "personal service account" but we
        # don't use that type anymore. GitLab is nowadays the only place where
        # this variable is set to service account credentials.
        #
        'GOOGLE_APPLICATION_CREDENTIALS': '{CLOUDSDK_CONFIG}/application_default_credentials.json',

        # The name of a Google user account with authorization to manage the
        # Google Cloud resources in the project referred to by GOOGLE_PROJECT.
        # If this variable is not set, GOOGLE_APPLICATION_CREDENTIALS must be
        # changed to the path of a file containing service account credentials.
        #
        'azul_google_user': None,

        # The name of the Google Cloud service account to represent the
        # deployment. This service account will be created automatically during
        # deployment and will then be used to access (meta)data in Google-based
        # repositories, like the Terra Data Repository (TDR). If unset, a
        # canonical resource name will be used. That default allows one such
        # account per Azul deployment and Google Cloud project.
        #
        'AZUL_GOOGLE_SERVICE_ACCOUNT': 'azul-ucsc-{AZUL_DEPLOYMENT_INCARNATION}-{AZUL_DEPLOYMENT_STAGE}',

        # The name of the Google Cloud service account to be created and used
        # for accessing public (not access-controlled) (meta)data in Google-
        # based repositories anonymously i.e., without authentication. Used for
        # determining the limits of public access to TDR.
        #
        'AZUL_GOOGLE_SERVICE_ACCOUNT_PUBLIC': 'azul-ucsc-{AZUL_DEPLOYMENT_INCARNATION}-public-{AZUL_DEPLOYMENT_STAGE}',

        # The name of the Google Cloud service account to be created and used
        # to simulate access from users who are logged in but not registered
        # with SAM.
        #
        'AZUL_GOOGLE_SERVICE_ACCOUNT_UNREGISTERED':
            'azul-ucsc-{AZUL_DEPLOYMENT_INCARNATION}-unreg-{AZUL_DEPLOYMENT_STAGE}',

        # The number of concurrently running lambda executions for the
        # contribution and aggregation stages of indexing, respectively.
        # Concurrency for the retry lambdas of each stage can be configured
        # separately via a '/' separator, e.g. '{normal concurrency}/{retry
        # concurrency}'. Chalice creates one Lambda function for handling HTTP
        # requests from API Gateway and one additional Lambda function per event
        # handler. The concurrency limit applies to each such function
        # independently. See
        #
        # https://docs.aws.amazon.com/lambda/latest/dg/concurrent-executions.html
        #
        # for details. These settings may also be used to drive other scaling
        # choices. For example, the non-retry contribution concurrency
        # determines the number of shards in OpenSearch.
        #
        'AZUL_CONTRIBUTION_CONCURRENCY': '64',
        'AZUL_AGGREGATION_CONCURRENCY': '64',

        # The number of concurrently running lambda executions for file
        # mirroring. See the previous paragraph for technical details. There is
        # no retry concurrency. No effect if ``AZUL_ENABLE_MIRRORING`` is zero.
        #
        'AZUL_MIRRORING_CONCURRENCY': '8',

        # Collect and monitor important health metrics of the deployment (1 yes, 0 no).
        # Typically only enabled on main deployments.
        #
        'AZUL_ENABLE_MONITORING': '0',

        # Whether to include relations in manifests of the verbatim PFB format
        # (1 yes, 0 no).
        #
        'AZUL_ENABLE_VERBATIM_RELATIONS': '1',

        # Mirror data files from the indexed repository in an S3 bucket
        # (1 yes, 0 no).
        #
        'AZUL_ENABLE_MIRRORING': '0',

        # The name of an external bucket to use for mirroring. This requires
        # deploying the GitLab component to update the boundary policy.
        #
        # If None, a provisioned bucket will be used.
        #
        'AZUL_MIRROR_BUCKET': None,

        # The name of an external bucket to use for mirroring managed access
        # files. If None, a provisioned bucket will be used.
        #
        'AZUL_MANAGED_ACCESS_MIRROR_BUCKET': None,

        # A short string (no punctuation allowed) that identifies a Terraform
        # component i.e., a distinct set of Terraform resources to be deployed
        # together but separately from resources in other components. They are
        # typically defined in a subdirectory of the `terraform` directory and have
        # their own directory under `deployments`. The main component is identified
        # by the empty string and its resources are defined in the `terraform`
        # directory.
        #
        'azul_terraform_component': '',

        # Set this to '1' in order to skip deleting certain types of unused
        # resources during `terraform apply`. The unused resources can be
        # deleted later by running `terraform apply` again with this variable
        # reset to its default. The resource types affected by this flag are:
        #
        # - Unused Docker images in ECR
        #
        # This variable should be not be overridden in other `environment.py*`
        # files. It should be left at its default, except temporarily, when
        # running `terraform apply`.
        #
        'azul_terraform_keep_unused': '0',

        # The slug of the Github repository hosting this fork of Azul
        #
        'azul_github_project': 'DataBiosphere/azul',

        # A GitHub REST API access token with permission to post status checks
        # to the repository defined in `azul_github_project`, and to create
        # issues in the Azul repositories (used by the `github_schedule` GitLab
        # CI job).
        #
        'azul_github_access_token': '',

        # A GitLab private access token with scopes `read_api`, `read_registry`
        # and `write_registry`. This variable is typically only set on developer
        # machines. In GitLab CI/CD pipelines, this variable should NOT be set
        # because a different type of token is automatically provided via the
        # CI_JOB_TOKEN variable.
        #
        'azul_gitlab_access_token': None,

        # The filesystem UUID of the EBS volume attached to the GitLab EC2
        # instance. This variable is only used in the `.gitlab` component. For
        # additional info, see section 8.5 of the README (Storage) and the
        # comments in `terraform/gitlab/gitlab.tf.json.template.py`.
        #
        'azul_gitlab_data_volume_id': None,

        # The name of the user owning the token in `azul_gitlab_access_token`.
        #
        'azul_gitlab_user': None,

        'PYTHONPATH': '{project_root}/src:{project_root}/test',
        'MYPYPATH': '{project_root}/src:{project_root}/stubs:{project_root}/test',

        # The path of a directory containing a wheel for each runtime
        # dependency. Settng this variable causes our fork of Chalice to skip
        # the downloading and building of wheels and instead install the wheels
        # from that directory. The wheels must be compatible with the AWS
        # Lambda platform.
        #
        # No longer actively used. The run-time dependencies of a Lambda
        # function are installed with uv, from the lock file, while its image is
        # built. Our fork of Chalice still reads this variable, but only while
        # building a deployment package from a `requirements.txt`, and there is
        # no such file for either Lambda function.
        #
        'azul_chalice_bin': None,

        # The path of the directory where the public key infrastructure files
        # are managed on developer, operator and administrator machines. The
        # directory contains secrets so it Must reside outside of the project
        # root so as to prevent accidentally committing those secrets to source
        # control.
        #
        'azul_easyrsa_pki': xdg_data_home + '/azul/easyrsa',

        # Set the Terraform state directory. Since we reuse deployment names across
        # different AWS accounts, we need a discriminator for the state directory and
        # the best I could come up with is the profile name.
        #
        'TF_DATA_DIR': '{project_root}/deployments/.active/.terraform.{AWS_PROFILE}',

        # Make Terraform's deprecation warnings more compact
        #
        **{
            'TF_CLI_ARGS_' + command: '-compact-warnings'
            for command in ['validate', 'plan', 'apply']
        },

        # BigQuery dataset location of the TDR snapshots the deployment is
        # configured to index. All configured snapshots must reside in the same
        # location.
        #
        # https://cloud.google.com/bigquery/docs/locations
        #
        'AZUL_TDR_SOURCE_LOCATION': None,

        # The full set of BigQuery dataset locations of the TDR snapshots
        # indexed across all deployments. The value of
        # ``AZUL_TDR_SOURCE_LOCATION`` must always be an element of this set.
        #
        'AZUL_TDR_ALLOWED_SOURCE_LOCATIONS': json.dumps([
            'US',
            'us-central1'
        ]),

        # BigQuery offers two modes for queries: interactive queries, which are
        # started immediately and limited to 100 concurrent queries, and batch
        # queries, which are not started until resources are available and do
        # not count towards the concurrency limit. Set this variable to 1 to
        # enable batch mode.
        #
        # https://cloud.google.com/bigquery/docs/running-queries
        #
        'AZUL_BIGQUERY_BATCH_MODE': '0',

        # The URL of the Terra Data Repository instance to index metadata from.
        #
        'AZUL_TDR_SERVICE_URL': None,

        # The URL of an instance of Broad Institute's SAM.
        # This needs to point to the SAM instance that's used by the TDR
        # instance configured in `AZUL_TDR_SERVICE_URL`.
        #
        'AZUL_SAM_SERVICE_URL': None,

        # The URL of Terra's DUOS service from which to index descriptions of
        # AnVIL datasets. If left unset, this step is skipped during indexing.
        #
        'AZUL_DUOS_SERVICE_URL': None,

        # The URL of an instance of Broad Institute's orchestration service for
        # Terra.
        #
        'AZUL_TERRA_SERVICE_URL': None,

        # The GCP project ID of the Terra workspace to charge for file downloads
        # from TDR while mirroring. If left unset, egress charges are incurred
        # to the owner of the GCS bucket the files are stored in. Otherwise, the
        # egress will be charged to the GCP billing account associated with the
        # workspace. See section 3.2.3 of the README.
        #
        'AZUL_TDR_REQUESTER_PAYS_PROJECT': None,

        # OAuth2 Client ID to be used for authenticating users. See section
        # 3.2 of the README
        #
        'AZUL_GOOGLE_OAUTH2_CLIENT_ID': None,

        # Maps a branch name to a list of names of deployments the branch may be
        # deployed to. When building a given branch, a GitLab instance uses this
        # variable to automatically determine the target deployment by using the
        # first item of the value for that branch. An empty key signifies any
        # other branch not mentioned explicitly, or a detached HEAD. Note that
        # this variable is likely being overridden on a GitLab instance so that
        # feature branches are deployed to the sandbox deployment.
        #
        # Only shared deployments are mentioned here. A shared deployment is one
        # that is not personal. A personal deployment is owned and maintained by
        # a single person. Shared deployments can be either main or sandbox
        # deployments. A sandbox deployment is used to test feature branches. A
        # main deployment is a shared deployment that is not a sandbox. Main
        # deployments can be either stable or lower. A stable (aka production)
        # deployment is one that must be kept operational at all times because
        # it is exposed to the public *and* serves external users for production
        # purposes. A lower (aka unstable) deployment is a main deployment that
        # is not stable.
        #
        # ╔════════════╗ ╔═════════════════════════════════════════════════════╗
        # ║  Personal  ║ ║                       Shared                        ║
        # ║            ║ ║ ╔═════════════╗ ╔═════════════════════════════════╗ ║
        # ║            ║ ║ ║   Sandbox   ║ ║              Main               ║ ║
        # ║            ║ ║ ║             ║ ║ ╔═════════════╗ ╔═════════════╗ ║ ║
        # ║            ║ ║ ║             ║ ║ ║    Lower    ║ ║   Stable    ║ ║ ║
        # ║ ┌────────┐ ║ ║ ║ ┌─────────┐ ║ ║ ║ ┌─────────┐ ║ ║ ┌─────────┐ ║ ║ ║
        # ║ │ hannes │ ║ ║ ║ │ sandbox │ ║ ║ ║ │   dev   │ ║ ║ │  prod   │ ║ ║ ║
        # ║ └────────┘ ║ ║ ║ └─────────┘ ║ ║ ║ └─────────┘ ║ ║ └─────────┘ ║ ║ ║
        # ║            ║ ║ ║ ┌─────────┐ ║ ║ ║ ┌─────────┐ ║ ║             ║ ║ ║
        # ║            ║ ║ ║ │anvilbox │ ║ ║ ║ │anvildev │ ║ ║             ║ ║ ║
        # ║            ║ ║ ║ └─────────┘ ║ ║ ║ └─────────┘ ║ ║             ║ ║ ║
        # ║            ║ ║ ║ ┌─────────┐ ║ ║ ║             ║ ║ ┌─────────┐ ║ ║ ║
        # ║            ║ ║ ║ │hammerbox│ ║ ║ ║             ║ ║ │anvilprod│ ║ ║ ║
        # ║            ║ ║ ║ └─────────┘ ║ ║ ║             ║ ║ └─────────┘ ║ ║ ║
        # ║            ║ ║ ║             ║ ║ ╚═════════════╝ ╚═════════════╝ ║ ║
        # ║            ║ ║ ╚═════════════╝ ╚═════════════════════════════════╝ ║
        # ╚════════════╝ ╚═════════════════════════════════════════════════════╝
        #
        'azul_shared_deployments': json.dumps({
            'develop': ['dev', 'sandbox', 'anvildev', 'anvilbox'],
            'prod': ['prod'],
            'anvilprod': ['anvilprod', 'hammerbox']
        }),

        # A dictionary with one entry per browser or portal site that is to be
        # managed by the `browser` TF component of the current Azul deployment.
        #
        # {
        #     'browser': { // The TF resource name of per-site resources in the
        #                  // `browser` component and unqualified name of the
        #                  // S3 bucket hosting the site
        #
        #         'domain': '{AZUL_DOMAIN_NAME}',  // The domain name of the
        #                                          // site
        #
        #         'zone': '{AZUL_DOMAIN_NAME}', // The name of the Route53
        #                                       // hosted zone containing the
        #                                       // A record for the domain name
        #                                       // of the site. The zone must
        #                                       // already exist before the
        #
        #         'project': 'ucsc/data-browser', // The path of the GitLab
        #                                         // project hosting the source
        #                                         // code for the site. The
        #                                         // project must exist on the
        #                                         // GitLab instance managing
        #                                         // the current Azul
        #                                         // deployment.
        #
        #         'branch': 'main', // The name of the branch (in that project)
        #                           // from which the site's content tarball was
        #                           // built
        #
        #         'tarball_name': 'anvil' // Typically corresponds to an Azul
        #                                 // atlas as defined in AZUL_CATALOGS
        #                                 // and a child directory of
        #                                 // .gitlab/sites/$AZUL_DEPLOYMENT_STAGE
        #                                 // in the source of the project
        #                                 // referenced by the top-level key in
        #                                 // this structure.
        #
        #         'tarball_path': 'explore',  // The path to the site's content
        #                                     // in the tarball
        #
        #         'real_path': 'explore/anvil-cmg'  // The path of that same
        #                                           // content in the bucket
        #     }
        # }
        #
        # The real_path and tarball_path properties define a path mapping from
        # files in the tarball to objects in the S3 bucket. In the above
        # example, the tarball entry `explore/foo.html` will be stored in the S3
        # bucket under the key `explore/anvil-cmg/foo.html`. The tarball entry
        # `fubaz/bar.html` will be store in the S3 bucket under the same key
        # (`fubaz/bar.html`). It is uncommon to have such tarball entries. Site
        # tarballs should always contain a single root directory.
        #
        'azul_browser_sites': json.dumps({}),

        # A list of names of AWS IAM roles that should be given permission to
        # manage incidents with AWS support as defined in CIS rule 1.20:
        #
        # https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-cis-controls.html#securityhub-cis-controls-1.20
        #
        'azul_aws_support_roles': json.dumps([]),

        # A dict containing the contact details of the AWS account alternate
        # contact for security communications. The keys must include those
        # required by the aws_account_alternate_contact Terraform resource,
        # however should exclude the key alternate_contact_type.
        #
        # https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/account_alternate_contact
        #
        'azul_security_contact': None,

        # To enable Slack integration with AWS Chatbot, set this variable to
        # a JSON object containing the IDs of the Slack workspace and Slack
        # channel for Chatbot to post notifications to. For example:
        #
        # 'azul_slack_integration': json.dumps({
        #     'workspace_id': 'your-workspace-id',
        #     'channel_id': 'your-channel-id'
        # })
        #
        'azul_slack_integration': None,

        # The CIDR of the Azul VPC. The VPC is shared by all deployments. Keep
        # that in mind when deciding on the width of the netmask. Also note that
        # the CIDR is split into four subnets. In other words, a /8 CIDR is
        # probably not a suitable choice. In the platform-hca-dev account, for
        # example, there are currently sixty network interfaces and most of them
        # are in two of the four subnets. Dividing a /8 CIDR into four subnets
        # would only allow for 64 IP addresses in each of the subnets, which is
        # dangerously close to that current number of network interfaces.
        #
        'azul_vpc_cidr': None,

        # The CIDR of the subnet used for the IP addresses on each end of a VPN
        # tunnel. AWS uses NAT between the tunnel IPs and the two IPs of an ENI
        # in the Azul VPC. This subnet can't overlap the VPC CIDR and the subnet
        # mask must be less than 22 bits.
        #
        'azul_vpn_subnet': None,

        # This variable contains a space-separated list of keywords, also known
        # as *flags*, that control certain aspects of the integration test (IT).
        #
        # The presence of the `no_index` flag prevents the IT from indexing and
        # causes it to reuse the indices created by a previous run. The
        # `no_delete` flag prevents the IT from performing any deletions,
        # allowing subsequent runs to reuse the indices.
        #
        # For faster modify-deploy-test cycles, set this to 'no_delete' and run
        # the IT. Then set it to 'no_index no_delete'. Subsequent IT runs will
        # reuse the index from a prior run, and be significantly faster, albeit
        # not covering any changes to the indexer, since indexing will be
        # skipped.
        #
        # To supress IT coverage of the mirroring functionality in Azul, include
        # the 'no_mirror' flag.
        #
        # To pin the random seed used by the IT, include the 'seed=12345' flag,
        # replacing 12345 with the integer seed you'd like to use. The IT logs
        # the seed, so running the IT again with the seed pinned should produce
        # the same test results.
        #
        # The 'unattended' flag ensures that running the IT requires no user
        # intervention. If the unattended flag is set, service account
        # credentials will be used for the tests that would otherwise have used
        # an access token for the current user. The downside of unattended mode
        # is therefore that no APAT functionality will be covered by the IT.
        #
        'azul_it_flags': None,

        # Wether to enable bot control in AWS WAF. Setting this to 1 will enable
        # two rules aimed at blocking requests from suspected and verified bots.
        # As of January 2024, this will incur monthly cost of $10 per ACL plus
        # $1 per one million requests above ten million requests. The blocking
        # only applies to URLs disallowed via robots.txt.
        #
        'azul_waf_bot_control': '0',

        # The maximum allowed percentage of blocked requests (number of blocked
        # requests, divided by the number of all requests, times 100) for a
        # configured period before a metric alarm is tripped.
        #
        'azul_waf_blocked_alarm_threshold': '50',

        # Whether to enable bundle notifications for incremental index changes
        #
        # FIXME: Enable bundle notifications again #7183
        #        https://github.com/DataBiosphere/azul/issues/7183
        #
        'AZUL_ENABLE_BUNDLE_NOTIFICATIONS': '0',

        # URL of Terra's external credentials manager (ECM) service used by the
        # Azul deployment.
        #
        'azul_ecm_service_url': None
    }