Skip to content
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

[Bug] Elasticsearch analyzer "keys" field is required but should not be #1291

Open
gaistou opened this issue Oct 25, 2024 · 0 comments
Open

Comments

@gaistou
Copy link

gaistou commented Oct 25, 2024

Describe the bug

The description of the analyzer says that the "keys" param is not required. However, leaving it empty when running the analyzer with a local config files generates an error.

To Reproduce

  • create a local input.json file without a "keys" field
  • run the analyzer with the local input.json
  • you get a "cannot iterate on None type" error

Expected behavior

The missing "keys" param should not generate an error.

Complementary information

The issue comes from the "zip" function call on index,keys,users, and passwords.

Work environment

  • Cortex Analyzer/Responder name: ElasticSearch
  • Cortex Analyzer/Responder version: 1.0
@gaistou gaistou changed the title [Bug] Elasticsearch "keys" field is required but should not [Bug] Elasticsearch analyzer "keys" field is required but should not Oct 25, 2024
@gaistou gaistou changed the title [Bug] Elasticsearch analyzer "keys" field is required but should not [Bug] Elasticsearch analyzer "keys" field is required but should not be Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant