Extract go sdk configuration#4089
Conversation
vladbarosan
commented
Oct 5, 2018
- extract Go sdk configuration
Automation for azure-sdk-for-goThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-pythonThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-javaThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-rubyThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-nodeThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-jsThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
|
Can one of the admins verify this patch? |
|
Fixes #3442 |
|
DO NOT MERGE>Will merge after sdk generation confirms no impact |
jhendrixMSFT
left a comment
There was a problem hiding this comment.
Found a handful of extra new-line characters at the beginning of some Go config files.
f0e7f55 to
a922f16
Compare
|
@jhendrixMSFT ok should be good to go now |
|
@fearthecowboy , @salameer are you guys admins here ? I need an admin to merge since all tools crash from extracting the go config. I generated locally before and after and there was no change. |
|
|
||
| These settings apply only when `--go` is specified on the command line. | ||
|
|
||
| ``` yaml $(go) |
There was a problem hiding this comment.
FYI -- in the readme.go.md having $(go) guards is optional, since the file will only get loaded when --go is specified anyway.
It's not harmful, it's just not necessary either.