Is there a way to split

pants.toml

sections and have them in a separate file? Reason is that the addition of new resolves requires editing this file, and currently we've got the admin of the repo as the code owner of

pants.toml

so any change to the resolves requires an admin's approval which is not very necessary We're working with dozens of resolves in our monorepo, BTW

The global

pants_config_files

option determines which config files Pants uses, but the catch is that you can’t set it in a config file, for obvious reasons.

Oh, got it! Thank you 🙂

Quick thought, is it at all possible to enable different subsystems in different parts of a repo, maybe using a

pants.toml

file in a subdirectory?

@acoustic-librarian-29560 Not today, but exactly that is going to be a major feature of the new Python backend, and eventually all of Pants I hope.

Does it have to be implemented in the backends specifically? My gut feeling as a plugin author is that this would ideally be a backend agnostic feature. Could you have a concept of subprojects where the backends only know about targets and union rules from the project they're running in or a subproject?

The backends would have to be aware of it, they are not currently written that way