Skip to content

All Mod's data service environments should have consistent configurations by default in each environments #106

@marchant

Description

@marchant

For example, for a database data service, we configure

"develop": {
"clientPool": {"@":"gcpPostgreSQLClientPool"},
"environment": "gcp",
"database": "my-app",
"owner": "postgres",
"schema": "my-app_v1",
"secretName": "my-app-database-credentials"
}

and we end up doing the same for all environments. Only the secret is treated as actual data, the name leads to a fetch for a secret with that name that ends up returning a different secret stored from each environment's secret value, which is different: different URL for the server, different client ssh key,

Local develop ends up being different because we still don't have a local secret manger, but we should. We might want to keep the flexibility to have different values, but have the ability to have a unique configuration applicable to all environments.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions