Conversation
|
@ph @mostlyjason @mtojek @andresrc The above means we should update all the packages with the related categories. Please reach out to @mostlyjason for the correct mapping. @mostlyjason Can you validate the the category list is correct? |
|
@mostlyjason Please create an issue in the integrations repository with updated categories for packages. We can pick it up from there. |
40b253b to
1580df3
Compare
1580df3 to
d5c0158
Compare
|
Thanks I left a comment on a separate thread discussing a new category field. I proposed that we move forward with this PR and come back later to update the categories if needed. Lets give a day or two to see if there are any objections. |
f1ad258 to
eeee8d4
Compare
In the process of defining our integrations page, additional categories were defined: https://www.elastic.co/integrations This PR adds these categories to the registry. It must be followed up to update all existing packages and then remove the old category definitions.
eeee8d4 to
5eeb73d
Compare
|
@mostlyjason Merged this PR so we can move forward with the changes in the packages but happy to follow up if you find more issues in the category names. |
The logs and metrics categories do not exist anymore. In elastic/package-registry#534 the supported categories were updated. The categories are removed for now to allow the registry to remove the legacy support for these categories. The new releases of these packages must contain the new categories.
The logs and metrics categories do not exist anymore. In elastic/package-registry#534 the supported categories were updated. The categories are removed for now to allow the registry to remove the legacy support for these categories. The new releases of these packages must contain the new categories.
In the process of defining our integrations page, additional categories were defined: https://www.elastic.co/integrations This PR adds these categories to the registry.
It must be followed up to update all existing packages and then remove the old category definitions.