Andreas Stenius

> > I'm wondering if there's a "missing" component in Pants here which lives between static configuration (pants.toml) and the BUILD files. For example; in Bazel you've got WORKSPACE which...

> We can propose that all backends are "generated"/"templated". Yes, we can attempt to always check for `generate(..)` when loading a backend, but perhaps only if we have kwargs. This...

> But there's certainly a lack of smarts that separates them from regular backends. I'm worrying that by equating them we'll (a) make teaching Pants harder, (b) have a mismatch...

oh, and thanks for reviewing and raising questions, it's precisely what we need to settle this :) 🙏🏽

Another shift, to stay closer to packages in `backend_packages` could be to instead have: ```toml [GLOBAL] backend_packages.add = [ "pants.backend.python", # the below are configured/templated backends and must still be...

> backend order matters for things like `fmt` and `fix`. [#17729 (comment)](https://github.com/pantsbuild/pants/issues/17729#issuecomment-1843840932) , something I constantly need to be reminded of. Ah, thank you for keeping that top of mind....

Hi @kuza55, Sorry for the confusion. This is not clearly called out in the [docs](https://www.pantsbuild.org/docs/tagging-docker-images#setting-a-repository-name), but you provide the default repository using `[docker].default_repository`. Any repository configured on the registry takes...

That's a fair point about the target value being more specific. I wonder if changing this to be more intuitive would cause any issues for existing uses..? Agreed that an...

the new `[docker].use_buildx` option from #20154 makes the above a lot easier to tackle, I think. (thanks @riisi!)

> @kaos Is there any way to future-pick this feature for an earlier release? @danny-todd-oxb It'll be in the 2.19.0 release which has entered stabilization. I don't think it'll come...