Skip to content
This repository has been archived by the owner on Sep 25, 2020. It is now read-only.

No way to specify common datacenter secrets #23

Open
freeqaz opened this issue Jun 8, 2015 · 2 comments
Open

No way to specify common datacenter secrets #23

freeqaz opened this issue Jun 8, 2015 · 2 comments

Comments

@freeqaz
Copy link

freeqaz commented Jun 8, 2015

When I'm testing on dev, I want to test that a datacenter's config is working. Currently, I can only specify my config on a per-datacenter basis. That leads to my config having a lot of duplication and redundancy.

common.json
development.json
development.datacenter.json
production.json
production.datacenter.json

It'd be nice to add support for common.datacenter.json in order to reduce the need of duplicating configuration.

@Raynos
Copy link
Contributor

Raynos commented Jun 8, 2015

Rather then implementing this I would rather inverse the inheritance.

i.e. production.json becomes common.json and development.json inherits from production;

We'll add a local.json to replace common.json and it will inherit from production.json

@Raynos
Copy link
Contributor

Raynos commented Jun 8, 2015

this means that every environment will inherits production.datacenter.json because it effectively becomes common.datacenter.json

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants