[cisco_duo] Fix bad value in ip and date fields

[vinit-chauhan]

Type of change

• Enhancement

What does this PR do?

This PR adds support for handling bad values in ip and date fields.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

Related issues

• Closes Cisco Duo integration (v1.1.1) - fields are not getting mapped when auth_device.ip field has value "None" #3696

Screenshots

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-07-14T14:58:20.455+0000

• Duration: 22 min 49 sec

Test stats 🧪

Test	Results
Failed	0
Passed	54
Skipped	0
Total	54

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (5/5)	💚
Files	100.0% (5/5)	💚 3.049
Classes	100.0% (5/5)	💚 3.049
Methods	100.0% (50/50)	💚 10.792
Lines	93.253% (622/667)	👍 3.048
Conditionals	100.0% (0/0)	💚

[andrewkroh]

If the pipeline appends to error.message then the global on_failure should also be appending so that no messages are lost. Currently it uses set so it will overwrite this error.

[vinit-chauhan]

Oh yeah, I missed it. I'll update it.

[andrewkroh]

@vinit-elastic Is there test case with an IP field containing "None" already in the package?

[vinit-chauhan]

@vinit-elastic Is there test case with an IP field containing "None" already in the package?

Hey @andrewkroh,
The reason we didn't add the log is that adding the log in the pipeline test would make the test fail with the following error.
unexpected pipeline error (unexpected error.message type []interface {}): ['None' is not an IP string literal.]

[andrewkroh]

Ok, thanks. So in order to support this type of testing we need a way to ignore the error.message from the test config.

[andrewkroh]

Related: elastic/elastic-package#912