-
Notifications
You must be signed in to change notification settings - Fork 60
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Core] Added logs for JQ misconfigured mappings (#1265)
created a test to simulate wrong mapping and validated for single and multiple data rows # Description What -following a bug ticket https://getport.atlassian.net/browse/PORT-12112, I have created a test to simulate wrong mapping and validated for single and multiple data rows Why - when the customer misconfigures a mapping we do not display the misconfigured fields and thus the customer can't understand the reason for the non working pipe How - I've added a misconfiguration dict to map all of the misconfigured mappings the logs shown prior to this change ``` 2024-12-24 13:00:54.025 | DEBUG | port_ocean.utils.queue_utils:_start_processor_worker:21 - Processing async task 2024-12-24 13:00:54.036 | DEBUG | port_ocean.core.handlers.entity_processor.jq_entity_processor:_parse_items:232 - Finished parsing raw results into entities with 0 errors. errors: [] ``` after the change: ``` 2024-12-24 13:00:54.024 | INFO | port_ocean.core.handlers.entity_processor.jq_entity_processor:_parse_items:221 - Parsing 2 raw results into entities 2024-12-24 13:00:54.025 | DEBUG | port_ocean.utils.queue_utils:_start_processor_worker:21 - Processing async task 2024-12-24 13:00:54.036 | DEBUG | port_ocean.core.handlers.entity_processor.jq_entity_processor:_parse_items:232 - Finished parsing raw results into entities with 0 errors. errors: [] 2024-12-24 13:00:54.036 | INFO | The mapping resulted with invalid values for identifier, blueprint, properties. Mapping result: {'identifier': '.ark', 'foo': '.bazbar', 'desc': '.foobar', 'name': '.bar.baz'} ```
- Loading branch information
Showing
6 changed files
with
102 additions
and
12 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