-
Notifications
You must be signed in to change notification settings - Fork 395
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
Cleanup YAML formatting #1328
Cleanup YAML formatting #1328
Conversation
Hi @FaithKovi. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Thanks @FaithKovi! This looks much better. Apparently there's a conflict with #1324 that just merged. Could you rebase the PR from the current |
6ae0632
to
76ca44c
Compare
/ok-to-test @FaithKovi I rebased this off |
673e1b3
to
872e815
Compare
/assign @AverageMarcus @drew-viles |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Just want to double check those backslashes are correct.
@@ -15,33 +15,33 @@ | |||
- name: Download Cloudbase-init | |||
win_get_url: | |||
url: "{{ cloudbase_init_url }}" | |||
dest: '{{ tempdir.stdout | trim }}\CloudbaseInitSetup.msi' | |||
dest: "{{ tempdir.stdout | trim }}\\CloudbaseInitSetup.msi" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to double check, are these backslashes supposed to be escaped? I would have expected them to also need to be with the quotes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are these backslashes supposed to be escaped?
Evidently single quotes work differently from double quotes in ansible. The best guidance on Windows paths in ansible I've found is here.
# GOOD
tempdir: C:\Windows\Temp
# WORKS
tempdir: 'C:\Windows\Temp'
tempdir: "C:\\Windows\\Temp"
# BAD, BUT SOMETIMES WORKS
tempdir: C:\\Windows\\Temp
tempdir: 'C:\\Windows\\Temp'
tempdir: C:/Windows/Temp
I'm not sure why ansible-lint fix
prefers that variant, but it works.
See also #767.
Thank you so much for being so patient with this @FaithKovi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Thanks @FaithKovi !!
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AverageMarcus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes #1313
Additional context
Add any other context for the reviewers