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

Multiple options "Decode_Field_as" in Parser in YAML has invalid format #9725

Open
heejew opened this issue Dec 14, 2024 · 0 comments
Open

Comments

@heejew
Copy link

heejew commented Dec 14, 2024

Bug Report

I have a "classic mode" configuration a parser with these two lines:

Decode_Field_as escaped message try_next
Decode_Field_as json message 

and I had a problem with converting this to YAML:
I tried to do this

      decode_field_as: 
      - type: escaped
        field: message
        action: try_next
      - type: json
        field: message

and that

decode_field_as:
  - escaped message try_next
  - json message 

also,

      rules: 
      - backend: decode_field_as
        type: escaped
        field: message
        action: try_next
      - backend: decode_field_as
        type: json
        field: message

BUT, it turns out, working config in YAML look like as

decode_field_as: escaped message try_next 
decode_field_as: json message 

And this is incorrect formating in YAML and i can't use autogeneration YAML, every tools when parsing lose one of the parameters.
Please, make it more correct everywhere.

  • Version used: 3.2.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant