-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
# Backport This will backport the following commits from `main` to `8.x`: - [Handle Json in Set and Append Value field (#204336)](#204336) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sonia Sanz Vivas","email":"sonia.sanzvivas@elastic.co"},"sourceCommit":{"committedDate":"2025-01-03T06:34:57Z","message":"Handle Json in Set and Append Value field (#204336)\n\nCloses [#193186](https://github.com/elastic/kibana/issues/193186)\n\n## Sumary\n\nThis PR introduces changes in two processors: Set y Append. The aim of\nthis changes is to allow introducing the Value field in both processors\nin Json format. Now, Set accepts Text format or Json and Append a list\nof values or Json. The toggle between the format is done by the new\nLabel Append button.\n<img width=\"705\" alt=\"Screenshot 2024-12-16 at 07 30 11\"\nsrc=\"https://github.com/user-attachments/assets/0f6283ed-6117-48d8-bdd8-e0685ae1b42d\"\n/>\n\n\nAlso, since the Set processor already had a Label Append button for\ntoggling between the `Value` and the `Copy_from` field, this now has\nbeen replaced by a toggle button that enables a field for the\n`Copy_from` field (see the last comments in the related Issue for see\nthe most updated mocks).\n<img width=\"708\" alt=\"Screenshot 2024-12-16 at 07 30 49\"\nsrc=\"https://github.com/user-attachments/assets/4a632bda-4b4b-49b1-b3d4-d11579d7c27c\"\n/>\n\nNote: the Set copies still pending review so probably will be changed.\n\n### Demo\n\n\nhttps://github.com/user-attachments/assets/f9d1da6a-782d-4197-836b-fab46b4476b7","sha":"59b229280d2d48d45f5623d7d521a804b24848bc","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","v9.0.0","Feature:Ingest Node Pipelines","backport:prev-major"],"title":"Handle Json in Set and Append Value field","number":204336,"url":"https://github.com/elastic/kibana/pull/204336","mergeCommit":{"message":"Handle Json in Set and Append Value field (#204336)\n\nCloses [#193186](https://github.com/elastic/kibana/issues/193186)\n\n## Sumary\n\nThis PR introduces changes in two processors: Set y Append. The aim of\nthis changes is to allow introducing the Value field in both processors\nin Json format. Now, Set accepts Text format or Json and Append a list\nof values or Json. The toggle between the format is done by the new\nLabel Append button.\n<img width=\"705\" alt=\"Screenshot 2024-12-16 at 07 30 11\"\nsrc=\"https://github.com/user-attachments/assets/0f6283ed-6117-48d8-bdd8-e0685ae1b42d\"\n/>\n\n\nAlso, since the Set processor already had a Label Append button for\ntoggling between the `Value` and the `Copy_from` field, this now has\nbeen replaced by a toggle button that enables a field for the\n`Copy_from` field (see the last comments in the related Issue for see\nthe most updated mocks).\n<img width=\"708\" alt=\"Screenshot 2024-12-16 at 07 30 49\"\nsrc=\"https://github.com/user-attachments/assets/4a632bda-4b4b-49b1-b3d4-d11579d7c27c\"\n/>\n\nNote: the Set copies still pending review so probably will be changed.\n\n### Demo\n\n\nhttps://github.com/user-attachments/assets/f9d1da6a-782d-4197-836b-fab46b4476b7","sha":"59b229280d2d48d45f5623d7d521a804b24848bc"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204336","number":204336,"mergeCommit":{"message":"Handle Json in Set and Append Value field (#204336)\n\nCloses [#193186](https://github.com/elastic/kibana/issues/193186)\n\n## Sumary\n\nThis PR introduces changes in two processors: Set y Append. The aim of\nthis changes is to allow introducing the Value field in both processors\nin Json format. Now, Set accepts Text format or Json and Append a list\nof values or Json. The toggle between the format is done by the new\nLabel Append button.\n<img width=\"705\" alt=\"Screenshot 2024-12-16 at 07 30 11\"\nsrc=\"https://github.com/user-attachments/assets/0f6283ed-6117-48d8-bdd8-e0685ae1b42d\"\n/>\n\n\nAlso, since the Set processor already had a Label Append button for\ntoggling between the `Value` and the `Copy_from` field, this now has\nbeen replaced by a toggle button that enables a field for the\n`Copy_from` field (see the last comments in the related Issue for see\nthe most updated mocks).\n<img width=\"708\" alt=\"Screenshot 2024-12-16 at 07 30 49\"\nsrc=\"https://github.com/user-attachments/assets/4a632bda-4b4b-49b1-b3d4-d11579d7c27c\"\n/>\n\nNote: the Set copies still pending review so probably will be changed.\n\n### Demo\n\n\nhttps://github.com/user-attachments/assets/f9d1da6a-782d-4197-836b-fab46b4476b7","sha":"59b229280d2d48d45f5623d7d521a804b24848bc"}}]}] BACKPORT--> Co-authored-by: Sonia Sanz Vivas <sonia.sanzvivas@elastic.co>
- Loading branch information
1 parent
465d2aa
commit 4152249
Showing
15 changed files
with
453 additions
and
164 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.