v15.1.0

[jhendrixMSFT]

Thanks you for your contribution to the Azure-SDK-for-Go! We will triage and review it as quickly as we can.

As part of your submission, please make sure that you can make the following assertions:

• I'm not making changes to Auto-Generated files which will just get erased next time there's a release.
  • If that's what you want to do, consider making a contribution here: https://github.com/Azure/autorest.go
• I've tested my changes, adding unit tests where applicable.
• I've added Apache 2.0 Headers to the top of any new source files.
• I'm submitting this PR to the dev branch, or I'm fixing a bug that warrants its own release and I'm targeting the master branch.
• If I'm targeting the master branch, I've also added a note to CHANGELOG.md.
• I've mentioned any relevant open issues in this PR, making clear the context for the contribution.

[azuresdkci]

Can one of the admins verify this patch?

[vladbarosan]

#1487 I reproed the issue.

2 causes:

1. We didn't regenerate the preview folder so some types are mismatchign ( the repo name switch from uuid to go.uuid from Satori) . Let's fot 15.1 maybe manually fix the profile so at least go get works. then after Handle preview specs properly #1136 is done it should work.

2. For some reason some Automation operations and Iot although they have a rsourcegroup parameter in all operations , one of them thinks is a client property not a parameter. I had a look at the specs for Automation in Dscconfiguration and couldn't see a reason for it. All methods have it correctly except the PATCH operation.

Note that for 2, fixing it would mean making one client call a breaking change but at this point is not working either way.

[vladbarosan]

Also the CI should catch these issues. Even looking at the PR CI here there are packages that dont work ( Automation, Cognitive Services ). https://travis-ci.org/Azure/azure-sdk-for-go/jobs/361872520

We cannot merge like this.

[vladbarosan]

@mcardosos can you have a look at why the CI didn't catch these ? I know there was a similar issue in the samples repo

[vladbarosan]

@mcardosos apparently it takes the exit code of the last command we need to check for the status code of each command. and fail if its non 0