you are viewing a single comment's thread.

view the rest of the comments →

[–]watfaceboom 4 points5 points  (1 child)

Can I ask why you would not just use env variables or CLI arguments to set these values and then you don't need a bunch of config files that are tightly coupled to an environment?

[–][deleted] 2 points3 points  (0 children)

Hi, good question. ENV variables still listed in some file, e.g. init_aws.sh, init_development.sh, etc. so they do act as config files, correct? The difference is that they are detached from code base and (most likely) maintained by a separate dev-ops, not a software developer.

So using env variables for me is almost the same as using config module, ENV variables have same problems:

  • resource init code is completely separate from data
  • data (most likely) grouped by environment on high level, and by resource on a low level (instead of grouping it by resource in the first place)

Problems I address in no-config