Feature request: auto create config file if not found about fig HOT 5 CLOSED

Hey @prgres few questions:

• What is your primary use case for this?
• What would the file contain when created?
• Which directory would the file be created in?

from fig.

• What is your primary use case for this?

I am thinking about a scenario when the user gets my binary file, runs it and if a config file is not detected, the app creates one and fills it with data the user provided during the initial start

• What would the file contain when created?

Maybe all required fields with no value set and the not mandatory one commented?

• Which directory would the file be created in?

Hm, the most convenient way I think is to split Dirs option to Dir (the default one) and additional that will be merged before scanning for file. Then if the config file won't be found, it would create one under the default path. This functionality would be gated behind the option to be backward compatible.

from fig.

Currently, I implementing catching the error file not found that fig throws but maybe there will be a space to port into fig itself

from fig.

It seems to me the behaviour you're looking for is for fig not to fail when a file is not found, and instead fallback to whatever is defined in the environment and/or annotations. Is there a reason you want to create the file? Are you expecting the user to modify it?

from fig.

Closing due to inactivity. Please open again if you'd like to continue the discussion.

from fig.