New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ingest pipelines] Add copy_from to set processor #104070
[Ingest pipelines] Add copy_from to set processor #104070
Conversation
4393c5d
to
ed7527f
Compare
@elasticmachine merge upstream |
@elasticmachine merge upstream |
merge conflict between base and head |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @sabarasaba!
Not sure if this one was ready for review yet (still in draft), but since I was tagged thought I'd give it a quick look as I'll be OOO next week 😄.
I left a few comments in the code. Overall, everything worked as expected.
I'm wondering if this one merits some more UX consideration. For example, what if there was first a selection - do you want to set a string value, or copy from an existing field? Then, there would just be one text input displayed based on the selection. I guess this would require an extra step for the user, so not sure if this is the best approach or not. However, I can see it being beneficial to better associate these two fields together so it's more clear that it's a one-or-another type deal. Would you mind reaching out to @dborodyansky to get his thoughts?
Also, I think this could benefit from a copy review. I think it would be helpful if we could better distinguish why a user might want to use value
over copy_from
, or vice versa.
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...est_pipelines/public/application/components/pipeline_editor/__jest__/processors/set.test.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
@alisonelizabeth Sorry you got pinged early, didnt thought gh will do when the PR was still in draft mode! Thanks for checking it out, will reach out to Dmitry and will ask the docs team to have a look later :) |
@elasticmachine merge upstream |
Pinging @elastic/kibana-stack-management (Team:Stack Management) |
After a small discussion with @dborodyansky, we agreed on following a similar pattern as we used in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @sabarasaba. I left some non-blocking suggestions that you can ignore if wanted.
Thanks for working on this.
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @sabarasaba! UX changes look good 👍 .
I left a couple nits in the code. I'd like to see at least the validation messages addressed before merging.
I also noticed the spacing is different with the toggle field. However, I also see the same issue with the network_direction
processor.
...est_pipelines/public/application/components/pipeline_editor/__jest__/processors/set.test.tsx
Outdated
Show resolved
Hide resolved
...est_pipelines/public/application/components/pipeline_editor/__jest__/processors/set.test.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
...s/public/application/components/pipeline_editor/components/processor_form/processors/set.tsx
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
merge conflict between base and head |
94bbf31
to
77e205b
Compare
Thanks again for re-checking @alisonelizabeth! Nice spot on the labels with toggle links not being exactly the same as the other fields. I've addressed this with d2b795e for both processors: |
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @sabarasaba |
* fix up validation conditions for fields * add tests and fix prettier errors * Small refactor and fix tests * Fix copy surrounding error handling * Clean up unnecessary boilerplate from tests * Fix i18n error * Keep optional select next to bound input * Pass disabled prop as boolean * fix test matchers * No need to whitelist fields anymore * Small CR changes * Convert optional inputs to toggle state * Fix testcase copy * address CR suggestions * address CR changes * Fix i18n * Fix labelAppend link alignment # Conflicts: # x-pack/plugins/translations/translations/ja-JP.json # x-pack/plugins/translations/translations/zh-CN.json
* fix up validation conditions for fields * add tests and fix prettier errors * Small refactor and fix tests * Fix copy surrounding error handling * Clean up unnecessary boilerplate from tests * Fix i18n error * Keep optional select next to bound input * Pass disabled prop as boolean * fix test matchers * No need to whitelist fields anymore * Small CR changes * Convert optional inputs to toggle state * Fix testcase copy * address CR suggestions * address CR changes * Fix i18n * Fix labelAppend link alignment # Conflicts: # x-pack/plugins/translations/translations/ja-JP.json # x-pack/plugins/translations/translations/zh-CN.json
* fix up validation conditions for fields * add tests and fix prettier errors * Small refactor and fix tests * Fix copy surrounding error handling * Clean up unnecessary boilerplate from tests * Fix i18n error * Keep optional select next to bound input * Pass disabled prop as boolean * fix test matchers * No need to whitelist fields anymore * Small CR changes * Convert optional inputs to toggle state * Fix testcase copy * address CR suggestions * address CR changes * Fix i18n * Fix labelAppend link alignment
Fixes: #101246
As a side note, either
value
orcopy_from
can be defined at any given time, not both.Release Note
The Ingest Node Pipelines UI added support to configure a copy_from field on the set processor.
Default description
New processor fields