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

[Fleet] fleet misrenders yaml string literal #200449

Open
efd6 opened this issue Nov 17, 2024 · 1 comment
Open

[Fleet] fleet misrenders yaml string literal #200449

efd6 opened this issue Nov 17, 2024 · 1 comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@efd6
Copy link

efd6 commented Nov 17, 2024

Fleet appears to render invalid yaml in some cases. Finer details in internal backlink that will appear below, but the summary is that the user is using the CEL input and has a program that looks like this:

bytes(get(state.url).Body).as(body, {
  "events": body.decode_json().field
})

but is rendered as this in the pre-config:

          program: |4-
               bytes(get(state.url).Body).as(body, {
            "events": body.decode_json().field
            })

This is broken because correct parsers expect the indentation to be 4, but all lines after the first are indented at 2. This breaks tools that need to be able to consume diagnostic bundles.

The stack version being used here is v8.15.2.

@efd6 efd6 added bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team labels Nov 17, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

2 participants