Add group field to mysql packages - #20547
Conversation
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
|
✅ All changelog entries have the correct PR link. |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
|
|
Package mysql - 1.30.2 containing this change is available at https://epr.elastic.co/package/mysql/1.30.2/ |
|
Package mysql_enterprise - 1.17.2 containing this change is available at https://epr.elastic.co/package/mysql_enterprise/1.17.2/ |
|
Package mysql_input_otel - 0.2.3 containing this change is available at https://epr.elastic.co/package/mysql_input_otel/0.2.3/ |
|
Package mysql_otel - 0.6.1 containing this change is available at https://epr.elastic.co/package/mysql_otel/0.6.1/ |
Proposed commit message
Add
group: mysqlto the manifest of all mysql-related packages:mysql,mysql_enterprise,mysql_input_otel,mysql_otel.WHAT: Adds a
groupfield to each package'smanifest.yml, immediately after thetypefield, with the valuemysql. Each package receives a patch version bump and a corresponding changelog entry.WHY: The Kibana UI uses the
groupfield to display related packages as a unified technology tile, allowing users to discover and install the full mysql observability stack from a single entry point.Checklist
changelog.ymlfile.Author's Checklist
group: mysqlappears in all 4 package manifests.How to test this PR locally
Start a local registry (v1.40.0) pointing at this branch using
elastic-packagev0.126.0 and query each package:Requires
elastic-packagev0.126.0, which starts the registry at v1.40.0.Each response should contain
"group": "mysql". Example:{ "name": "mysql", "version": "1.30.2", "type": "integration", "group": "mysql" }Related issues
Screenshots