[Ingest pipelines] add support for registered_domain processor

[sabarasaba]

Fixes: #97465

Release note

The Ingest Node Pipelines UI added support to configure a registered domain processor. This processor extracts the registered domain, sub-domain and top-level domain from a fully qualified domain name.

Default Description

New Processor fields

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[sabarasaba]

@elasticmachine merge upstream

[alisonelizabeth]

Nice work @sabarasaba! 🎉 Great to see support added to the UI for another processor.

Overall, everything worked as expected. I left a few minor comments. I also found one issue related to the default value for the ignore_missing parameter. I'd like to see this addressed before approving. I went through and checked our other processors using this component (out of curiosity) and found a similar bug for the csv processor. I opened #99647 to address separately.

Also, would you mind adding a screenshot of what the default description looks like to your PR? I think it might help the docs team when they review the copy.

[alisonelizabeth]

@sabarasaba one more thing I forgot to mention 😄 - would you mind adding a release note to the PR description? You can take a look at #86163 as an example.

[alisonelizabeth]

Thanks for the quick turnaround on addressing my feedback!

I believe you'll also need to define a custom serializer, as the current behavior sets the field to undefined if it is false and strips it from the request. Perhaps we can also add a test for this behavior?

You can check out the form lib docs for more info on how the serializer/deserializer behaves.

[sabarasaba]

@alisonelizabeth good point! I totally missed that part in the internal implementation of the IgnoreMissingField component. I have now replaced this serializer with another one that removes it if set to true, since the api defaults the field to true we can get away with only sending it if disabled (I did it this way in order to follow the same patter that the geoIP processor uses).

[alisonelizabeth]

LGTM. Verified locally and everything works as expected now. I left a comment about the use of any, but won't block on it. Great work!

[lockewritesdocs]

Minor comments, but LGTM overall 🎉 Couldn't build/test locally because packages were missing, but updating the branch might resolve that issue.

[sabarasaba]

@elasticmachine merge upstream

[sabarasaba]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: d1db05f
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
ingestPipelines	492	493	+1

Async chunks

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

id	before	after	diff
ingestPipelines	680.7KB	682.0KB	+1.3KB

Unknown metric groups

References to deprecated APIs

id	before	after	diff
canvas	29	25	-4
crossClusterReplication	8	6	-2
fleet	22	20	-2
globalSearch	4	2	-2
indexManagement	12	7	-5
infra	261	149	-112
lens	67	45	-22
licensing	18	15	-3
maps	286	208	-78
ml	121	115	-6
monitoring	109	56	-53
stackAlerts	101	95	-6
total			-295

History

• 💛 Build #125996 was flaky 529e096
• 💚 Build #125345 succeeded 25912a8
• 💔 Build #125335 failed 36bb550
• 💚 Build #125275 succeeded 3e25668
• 💚 Build #125122 succeeded 0522a5c

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

cc @sabarasaba