I should add that the records.cfg is the only current way to load a cfg
file with a different name. The runroot and the env vars only allow us to
point to a different directory with the predefined names.
still +1 for this, however, there might be a functional break for some
people because of this
+1
On Friday, November 1, 2019, 06:52:45 AM PDT, Leif Hedstrom
wrote:
Hi all,
I’d like to remove all (most?) of the settings that lets you override
configuration file names via records.config. We have other means to accomplish
this (environment variables / runroot), and, many times,
+1
On Fri, Nov 1, 2019 at 9:42 AM Sudheer Vinukonda
wrote:
> +1
>
>
> On Nov 1, 2019, at 6:52 AM, Leif Hedstrom wrote:
> >
> > Hi all,
> >
> > I’d like to remove all (most?) of the settings that lets you override
> configuration file names via records.config. We have other means to
> accomplis
+1
On Nov 1, 2019, at 6:52 AM, Leif Hedstrom wrote:
>
> Hi all,
>
> I’d like to remove all (most?) of the settings that lets you override
> configuration file names via records.config. We have other means to
> accomplish this (environment variables / runroot), and, many times, this
> “fea
Hi all,
I’d like to remove all (most?) of the settings that lets you override
configuration file names via records.config. We have other means to accomplish
this (environment variables / runroot), and, many times, this “feature” has
caused problems during upgrades. In addition, debug / warning
