uber-node / zero-config

A zero configuration configuration loader
MIT License
116 stars 10 forks source link

No way to specify common datacenter secrets #23

Open freeqaz opened 9 years ago

freeqaz commented 9 years ago

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 commented 9 years ago

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 commented 9 years ago

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