Add deployment APIs at tenant scope

[Tiano2017]

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[openapi-sdkautomation]

In Testing, Please Ignore

[Logs] (Generated from b943cc5, Iteration 15)

[AutorestCI]

Automation for azure-sdk-for-python

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

[AutorestCI]

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

[azuresdkci]

Can one of the admins verify this patch?

[ghost]

@OpenAPIBot sdkautomation rebuild

[PhoenixHe-NV]

@OpenAPIBot sdkautomation rebuild

[yungezz]

@Tiano2017 there're errors in CI. pls fix them.

• modelvalidation error: https://dev.azure.com/azure-sdk/public/_build/results?buildId=74633&view=logs&j=8d2f9c49-cd83-5a9d-f3fe-2fd651afa742. Error is MISSING_REQUIRED_PARAMETER
• semanticvalidation error. https://dev.azure.com/azure-sdk/public/_build/results?buildId=74633&view=logs&j=95dbed5b-845d-57ba-33d3-f6c5e69afcf4. pls define scope parameter

[Tiano2017]

@yungezz Looking at my example file: https://github.com/Azure/azure-rest-api-specs/pull/6720/files#diff-30a00039c98a25059cce3712940c7032, I see both parameters are provided. Not sure if there's anything I missed. Can you help me understand the error?

[yungezz]

@Tiano2017 try put parameters parameter into body as defined in swagger file. sample: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/authorization/resource-manager/Microsoft.Authorization/stable/2015-07-01/examples/PutRoleDefinition.json#L6

[majastrz]

Looks good to me.

[Tiano2017]

@yungezz I did pretty much the same as PutRoleDefinition, but it's still failing.. any more suggestions?

[Tiano2017]

@yungezz I tried a few approaches, but am still getting errors on model validation. Do you have any suggestions on what I need to do to fix them?

[yungezz]

no need to add error code in swagger file, pls add "default" back.

[yungezz]

need to remove error code and add default

[majastrz]

    },

We never respond with both validation results and error, right? (partial failure)

---

Refers to: specification/resources/resource-manager/Microsoft.Resources/stable/2019-07-01/resources.json:3788 in a18e248. [](commit_id = a18e248, deletion_comment = True)

[Tiano2017]

@majastrz For export template we can return a response that contains both results and error. For other requests I don't think we do that.

[ravbhatnagar]

signing off from ARM side on the changes added after the last sign off!

[yungezz]

is this a typo?