[azure_metrics] Fix compute_vm stream YAML indentation - #18822
Merged
Conversation
Multi-line flow sequence continuations in compute_vm/agent/stream/stream.yml.hbs were indented to column 5, less than their parent `- name:` list item at column 9. Older YAML parsers (go-yaml v2/v3, js-yaml, PyYAML) accept this, but Kibana 9.5+ uses eemeli/yaml which strictly enforces YAML 1.2 rule 9C9N: flow sequence continuations must be indented past the parent block. Installation fails with: Flow sequence in block collection must be sufficiently indented and end with a ] at line N, column 5 Re-indents the affected continuations to column 13, matching the convention already used in the resource_ids and unless branches of the same template.
Contributor
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
andrewkroh
added
Integration:azure_metrics
Contributor
|
Package azure_metrics - 1.11.1 containing this change is available at https://epr.elastic.co/package/azure_metrics/1.11.1/ |
herrBez
pushed a commit
to herrBez/integrations
that referenced
this pull request
Jun 1, 2026
* [azure_metrics] Fix compute_vm stream YAML indentation Multi-line flow sequence continuations in compute_vm/agent/stream/stream.yml.hbs were indented to column 5, less than their parent `- name:` list item at column 9. Older YAML parsers (go-yaml v2/v3, js-yaml, PyYAML) accept this, but Kibana 9.5+ uses eemeli/yaml which strictly enforces YAML 1.2 rule 9C9N: flow sequence continuations must be indented past the parent block. Installation fails with: Flow sequence in block collection must be sufficiently indented and end with a ] at line N, column 5 Re-indents the affected continuations to column 13, matching the convention already used in the resource_ids and unless branches of the same template. * Update changelog PR link
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Multi-line flow sequence (
[...]) continuations incompute_vm/agent/stream/stream.yml.hbswere indented to column 5, while the parent- name:list item is at column 9. Older YAML parsers (go-yaml v2/v3, js-yaml, PyYAML) silently accept this, but Kibana 9.5+ useseemeli/yamlwhich strictly enforces YAML 1.2 rule 9C9N. On 9.5.0 the integration fails to install with:This PR re-indents the affected continuations to column 13, matching the convention already used in the
resource_idsandunlessbranches of the same template. Confirmed witheemeli/yaml:Affected lines: 40, 45–56, 107–118, 169–180 in
compute_vm/agent/stream/stream.yml.hbs. Whitespace-only changes (no metric names added/removed).Test plan
elastic-package checkpasses forpackages/azure_metrics.azure_metrics(Virtual Machines policy template) on Elastic Cloud 9.5.0 — installation succeeds.