In aero, how would you handle a config which is both a function of a command line argument (modeA vs modeB) and the runtime environment (prod, dev, test, etc)?
@ben.sless one way could be to generate all the possible profiles like
#profile {:mode-a-dev .. #mode-b-prod .. }
and then just generate the right profile to pass in when you get the configmaybe a bit tedious but should work, otherwise you could implement your own profile reader that allows for the extra nesting