fix: remove trailing dashes for multidoc yaml #1331
Closed
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.
Fixes #1330 #1296
Description of the change
While introducing multi document support for JSON and YAML, we introduced trailing dashes for YAMLs, which violates the YAML specification. This change will separate JSON and YAML with
\n
for JSON and---
for YAML, only if there are multiple documents given. It will not append a new line or dashes for the last documentBenefits
YAML specification is met, linters will be happy.
Possible drawbacks
Applicable issues
kubeseal
appends extra document separator---
when format is YAML #1330kubeseal
adds trailing newline to YAML output #1296Additional information