Add Agent Jobs and Login migration for SQL to MI public preview scenario

[hitenjava]

Approved PR for private repo - https://github.com/Azure/azure-rest-api-specs-pr/pull/427

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

• The title of the PR is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
• Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
• If applicable, the PR references the bug/issue that it fixes.
• Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[AutorestCI]

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#2071

[AutorestCI]

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#1474

[AutorestCI]

Automation for azure-libraries-for-java

Nothing to generate for azure-libraries-for-java

[AutorestCI]

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

[jhendrixMSFT]

One comment on a change to an operation ID, it's not blocking though.
Have these APIs been reviewed by ARM and the API review board and are they deployed?

[jhendrixMSFT]

I would change the name to ResourceSkus_List since Skus is already in the operation group, else you'd end up with a method like this.

ResourceSkus.ListSkus()

[hitenjava]

@jhendrixMSFT - If you look only at 2nd commit, you'll see the diff of what is new in this api-version. The previous version is already in public preview. This wasn't really changed in this version, it has been present even in the previous version.

Yes, the APIs have been reviewed and deployed.

[jhendrixMSFT]

Oh thanks for pointing this out. If this is ready for building SDKs I will push an update to the README to include this for Go, does that work?

[hitenjava]

Yes

[hitenjava]

Yes, this can be published.
I've been updating the azure-sdk-for-net repo after this (for previous changes), not sure about the Go part.