We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please describe your feature request.
Sorry, I searched but I did not find any similar issue.
Consider a YAML file like:
apiVersion: v2 appVersion: "0.1.0" description: A Helm chart name: mychart version: "0.1.0" dependencies: - name: anotherchart version: ">0.0.0-0"
And what happens is:
$ yq '(.dependencies[] | select(.name == "anotherchart") | .version) |= "1.1.1"' Chart.yaml apiVersion: v2 appVersion: "0.1.0" description: A Helm chart name: mychart version: "0.1.0" dependencies: - name: anotherchart version: "1.1.1"
- - name: anotherchart - version: ">0.0.0-0" + - name: anotherchart + version: "1.1.1"
Describe the solution you'd like
I want the output to retain the original indentation of the array, i.e.:
apiVersion: v2 appVersion: "0.1.0" description: A Helm chart name: mychart version: "0.1.0" dependencies: - name: anotherchart version: "1.1.1"
Describe alternatives you've considered I haven't found any way around it.
Additional context N/A
The text was updated successfully, but these errors were encountered:
Yep this is a known and documented issue with the underlying go-yaml parser :(
#465, #462
Sorry, something went wrong.
Thank you!
This is quite a dealbreaker when using version control where fill diffs are important.
No branches or pull requests
Please describe your feature request.
Sorry, I searched but I did not find any similar issue.
Consider a YAML file like:
And what happens is:
Describe the solution you'd like
I want the output to retain the original indentation of the array, i.e.:
Describe alternatives you've considered
I haven't found any way around it.
Additional context
N/A
The text was updated successfully, but these errors were encountered: