Update extension docs #2072
Update extension docs #2072
Conversation
|
|
Lantero
force-pushed
the
update-extension-docs
branch
from
800eef9 to
da11cf7
Compare
| | **Community** | Community | ✅ Yes | ⚠️ Partial\* | | ||
|
|
||
| \* _Partial_ cloud support means that the extensions can be used in the CLI with the `--local-execution` mode, and on Private Load Zones with a custom image. They don't work on Grafana Cloud k6 Public Load Zones. | ||
| | Category | Maintainer | Audited | Cloud support | Guaranteed updates | |
There was a problem hiding this comment.
What do we mean by "Guaranteed updates" here @Lantero? 🤔
I'm wondering if this might be better explained outside of a column.
There was a problem hiding this comment.
Important security patches/backports mostly. Any thoughts on how we could incorporate this information? It is an important (the main) difference between official and community. With community, we vet a specific version and "forget" i.e. we don't take responsibility for keeping it up to date, you should use them at your own risk and rely on the maintainers for these type of patches.
Without this new column, the original table would look weird since it would be the same for both official and community, except for ownership. We could also challenge whether we need this table or not, now that both official and community are cloud supported.
Community extensions are now supported in the cloud, due to changes in these PR's:
In short, the registry got trimmed by removing all extensions that were not part of the new official/community lists, and both GCk6 backend and frontend are now using https://registry.k6.io/catalog.json as single source of truth, so all the builder endpoints support the full collection of extensions (community + official).
This should reconcile documentation with this change, and make our users happier.
That being said, we should likely prioritise https://github.com/grafana/k6-cloud/issues/3603 as a consequence.