Skip to content

Initial 2019-09-01-preview for LVA#7247

Merged
anuchandy merged 3 commits intoAzure:masterfrom
BrianBlum:master
Sep 24, 2019
Merged

Initial 2019-09-01-preview for LVA#7247
anuchandy merged 3 commits intoAzure:masterfrom
BrianBlum:master

Conversation

@BrianBlum
Copy link

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
Copy link

openapi-sdkautomation bot commented Sep 18, 2019

In Testing, Please Ignore

[Logs] (Generated from ae35d5e, Iteration 3)

Failed .NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Succeeded Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
Failed Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]
Warning Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
  • Warning mediaservices/mgmt/2015-10-01 [Logs]
  • Warning mediaservices/mgmt/2018-07-01 [Logs]
  • Warning preview/mediaservices/mgmt/2018-03-30-preview [Logs]
  • Warning preview/mediaservices/mgmt/2018-06-01-preview [Logs]
Failed JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
Succeeded Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]

@BrianBlum
Copy link
Author

BrianBlum commented Sep 18, 2019

Adding WaitForARMFeedback label for this PR

@BrianBlum BrianBlum added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Sep 18, 2019
@AutorestCI
Copy link

AutorestCI commented Sep 18, 2019

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Sep 18, 2019

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@majastrz majastrz added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Sep 19, 2019
Copy link
Member

@majastrz majastrz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signed off from ARM side.

"put": {
"summary": "Create or update a Media Graph",
"description": "Create or update a Media Graph in the Media Services account",
"operationId": "MediaGraphs_CreateOrUpdate",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is creareOrUpdate a long running operation? same question for delete.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both PUT (CreateOrUpdate) and DELETE are not long running. They complete synchronously.
In our API, START and STOP actions are Long running operations

}
}
},
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Media/mediaServices/{accountName}/mediaGraphs/{mediaGraphName}/operationsStatus/{operationId}": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this is to retrieve result of long running operation, if so usually we don't include this operation instead annotate actual LRO operation with x-ms-long-running-operation.

Copy link

@PrasannaKudli PrasannaKudli Sep 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both long running operations use "x-ms-long-running-operation": true. See line 560 and 608.
As part of long running operation, we return operationId in response header. User can use this API to get operation status.

@anuchandy anuchandy merged commit 76666f1 into Azure:master Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants