Skip to content

Feature Request: Shared service configuration within an application #2699

Open
@jlucas91

Description

I'm finding that the services within my application are sharing a lot of their configuration. Their sidecars (logging, datadog agent), addons (SQS permissions), image config, and secrets are all very, very similar.

Right now I have to copy/paste the entire service configuration between services. This is disincentivizing me from creating new services (ex. single purpose queue consumers that share the same source code), which is a bummer! I can forsee it being a big pain keeping them all in sync, particularly when adding/removing secrets. I'd love to be able to define a base config that the others inherit from/can override.

Do you have any plans to add something like that? Are y'all seeing similar concerns from other users and if so is there a way they're working around it? The best workaround I can think of is templating/generating the manifests myself, which I'd love to avoid.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    area/manifestIssues about infrastructure-as-code templates.size/LWe should be able to deliver roughly a large in 2-3 sprints.type/featureIssues that are new feature requests.type/requestIssues that are created by customers.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions