Skip to content

configuration_files.md

Latest commit

 

History

History
30 lines (16 loc) · 2.22 KB

configuration_files.md

File metadata and controls

30 lines (16 loc) · 2.22 KB
Raw

Configuration Files

This solution is designed so that the average deployer can interact solely with a core set of configuration files, and not need to interact with the underlying Terraform and Python assets.

Configuration File Details

Configuration activities are split between two different categories:

  1. Desired infrastructure and application deployment state (via terraform.tfvars).

  2. Seeding of sensitive application secrets in AWS Parameter Store (via ssm_sensitive_values_* files).

  3. terraform.tfvars
    Used to set flags and values that control how your infrastructure and the Seqera Platform Enterprise instance is built and configured.

    This file must be configured and stored in the project folder root.

  4. ssm_sensitive_values_tower.json
    Used to define secrets like credentials and passwords which the Seqera Platform needs to fulfill its duties.

    This file exists to make SSM data population more convenient and should not be stored in source-control.

  5. ssm_sensitive_values_seqerakit.json (Optional; deprecated as of Release 1.8)
    Used to define secrets like tokens and credentials which the Seqerakit tool needs to fulfill its duties. The file/SSM entry must still be created, but contents may be placeholder values.

    This file exists to make SSM data population more convenient and should not be stored in source-control.

  6. ssm_sensitive_values_groundswell.json (Optional)
    Used to define credentials for the Groundswell optimization service.

    This file exists to make SSM data population more convenient and should not be stored in source-control.

  7. ssm_sensitive_values_wave_lite.json (Optional)
    Used to define credentials for the Groundswell optimization service.

    This file exists to make SSM data population more convenient and should not be stored in source-control.