[Ingest Pipelines] Highlight deprecated pipelines

[sabarasaba]

Partially addresses #170805

Summary

With elastic/elasticsearch#101148 we now can alert the users when an ingest pipeline will soon be deprecated and shouldnt be relied upon. This PR adds a badge and a callout to the ingest pipelines UI to alert the users about this.

How to test

• Start up kibana and es
• Navigate to Stack management -> Ingest pipelines
• Verify that:
  • Deprecated pipelines are hidden by default
  • Upon enabling filtering to see them they should pop up on the table with a badge
  • Verify that deprecated policies are highlighted and when editing, we also show a warning callout.

Screenshot

[sabarasaba]

/ci

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[yuliacech]

Thanks a lot for working on the deprecated pipelines, @sabarasaba!
Code changes LGTM 👍 I tested locally and the UI works as expected.
The filters are a little confusing for me though: the managed filter is not enabled by default but managed pipelines are shown and the deprecated ones are hidden. So it feels like the same filter buttons don't have the same function. I was trying to hide both managed and deprecated pipelines, but I don't think that is possible at the moment.
I think a more consistent UI for filters would be to mark the "managed" filter as enabled by default and if the user clicks to disable it, hide managed pipelines. That way both filters would work consistently, wdyt?

[sabarasaba]

I was trying to hide both managed and deprecated pipelines, but I don't think that is possible at the moment.

Not with filtering buttons perse, but can be done by negating the query -is:isManaged.

I think a more consistent UI for filters would be to mark the "managed" filter as enabled by default and if the user clicks to disable it, hide managed pipelines. That way both filters would work consistently, wdyt?

This problem arises because we want managed to be shown by default, but deprecated to be hidden by default and they both need to work with the same filtering pattern.

But I think this would make for an odd default behaviour too, since if the managed filter is enabled by default then we would want managed pipelines and non-managed to be shown and the same would need to happen for the deprecated which is strange. I think a way to have them behave consistently while keeping sane defaults would be to have managed hidden by default (although I might be missing something on why we have this enabled by default). So that toggling the filter will show us only those that comply with the filtering option (deprecated|managed). 🤔

[sabarasaba]

@elasticmachine merge upstream

[sabarasaba]

/ci

[yuliacech]

Thanks a lot for addressing the feedback, @sabarasaba!
I re-tested locally and pushed some changes to make the implementation somewhat easier by filtering the pipelines according to the filters options (managed and deprecated) and leaving the search to be handled by the table.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 7a393cb

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
ingestPipelines	362.0KB	364.7KB	+2.7KB

History

• 💚 Build #191327 succeeded 9146b7b
• 💚 Build #190655 succeeded f9bf00f
• 💚 Build #190389 succeeded e9d7f37
• 💔 Build #190382 failed 76ea1b7
• 💔 Build #190378 failed 6aa88c2
• 💚 Build #187357 succeeded 9656925

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @yuliacech