Is there an index of quality plugins anywhere?

Not to my knowledge. To date, most of the mature plugins get merged into the main Pants codebase, so it’s easier to keep them up to date as the plugin API changes (it is not yet completely stable, although getting there).

definitely something I'm seeing that I'd end up having to invest in as things stand

I have a hunch you might be interested in this, for whenever it lands: https://github.com/pantsbuild/pants/pull/16412 Idea is to make adding code quality plugins just a config file,

could be interesting. Sometimes DSLs (even if it's a config driven thing) can be more limiting than expected though. It's hard to say.

To add to what Benjy said, yep there's no official directory. I looked into making one but the consensus was the while there's stabilization work to be finished on the plugin API, we are reluctant to point people at 3rd parties plugins that are likely to break on them due to our changes. API stabilization is the priority. That said, to the extent one is comfortable discussing what you need to achieve, usually someone here can offer you a running start at what you want.

makes a lot of sense. 🙂 I'm sure I'm going to have a ton of random questions and give more than a small amount of feedback and ideas. I hope it's not too annoying <_<

Definitely not annoying, we welcome it!

We have 3 plugins we would be happy to contribute to a community repository of plugins once the API is stable. I'm not sure the plugins are broad enough to merged into the main codebase.

I'd love an index! Concourse has a page on third-party plugins like that: https://resource-types.concourse-ci.org/. I think that'd also make it easier to find somewhere to contribute/collaborate. For example, I'm working on k8s/kustomize and now also a umoci wrapper. Maybe someone else is? Who knows 🙂

This spreadsheet of known Pants plugins is a year out of date. And is just informational for now since they're not vetted, unlike contribs to core. But let's start by bringing that up to date, and figure out what we can do to make it easier for folks to find unvetted examples they might find useful! If you have, or know of, a public plugin, please do add it to that spreadsheet or update its info there. https://docs.google.com/spreadsheets/d/1F3k4T8OkQpZ1pGA6YK-kh5AkbP3ma-C-QDljFi33ZTk/edit#gid=0

I have a variety of plugins in my PoC branch for the StackStorm repo. Some are st2-specific, and some are more generic. The stevedore_extensions and do_invoke plugins are more generic. Others can be more inspirational for other repos, like uses_services https://github.com/st2sandbox/st2/tree/pants/pants-plugins

Would you add all of the public ones to the spreadshoot and add a note about which you think are/aren't useful outside of StackStorm context? Even if someone doesn't re-use it, just seeing a working example can be helpful for understanding how to roll one's own.

@busy-vase-39202 I took the liberty of structuring the spreadsheet a bit to add some headings for maintenance status as mine is only WIP 🙂

Terrific!