awk for azure resource group can accept unformatted json#659
Conversation
|
/test-all |
|
/test 4.7-operator-e2e-azure |
|
@kaovilai: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/lgtm @kaovilai If I remember correctly, It did pass for Azure before and picked up the resource group properly, maybe formatting issue ? Thank you for looking into this! |
|
Closed in favor of #654. Edit: reopened since it had lgtm. |
|
oops didn't see lgtm. :D |
I think it depends which config files you end up getting which may differ from region/cluster/zones that are outside our control. But sounds like majority of (at least recent) the clusters had unformatted, no newline, json. |
|
Got it. Please close this PR when you see fit since you have already included these in the #654, you might have a clash or need to do a rebase if both goes in. |
Fix #658
Make awk regex used for azure resource group work when input json is an unformatted single line.