Hook for automatically generated .buckconfig?

In Buckaroo we are overwritting .buckconfig.local with automatically generated values for [repositories]. This is less than ideal, because if the user has important configuration there it is lost.

It would be possible for us to parse and merge the existing .buckconfig.local (discussion), but this would be a brittle solution.

Instead, perhaps Buck could provide a hook for this? For example, we could introduce a new .buckconfig designed for generated values. For example (in order or precedence):

• .buckconfig
• .buckconfig.generated
• .buckconfig.local

Would this fit with the overall design direction of Buck?

[styurin]

.buckconfig supports including other files, see “Configuration files can include other files” here: https://buckbuild.com/files-and-dirs/buckconfig.html.

You can create .buckconfig.generated file and include it from .buckconfig:

<?file:.buckconfig.generated>

The question mark instructs buck not to fail when that file doesn’t exist.

[nikhedonia]

well, you can create a buck wrapper script when initializing buckaroo repo, which would call buck and pass appropriate overrides

Unfortunately then we would need to call the script using a relative path… One nice feature of Buck is that you can invoke any buck command from any sub directory and it just works.