We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When requesting a long running operation (LRO), if the response is 200 OK, generated code will not start polling. For example:
https://github.com/Azure/azure-powershell/blob/58ca05dc9185895a19c6cedbb92c5e54546daa8a/src/Databricks/generated/api/Databricks.cs#L1204
This may cause some cmdlets to return early with the resource not fully provisioned.
The cmdlet should start polling until the resource has successfully been provisioned.
The text was updated successfully, but these errors were encountered:
According to https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/Addendum.md#creatingupdating-using-put If the request is a PUT we should expect a 201 Created or 200 OK, otherwise it should be 202 Accepted. But now we are just expecting 201 and 202 for all HTTP methods. We'll need to re-design the logic.
Sorry, something went wrong.
isra-fel
Successfully merging a pull request may close this issue.
Current behavior
When requesting a long running operation (LRO), if the response is 200 OK, generated code will not start polling. For example:
https://github.com/Azure/azure-powershell/blob/58ca05dc9185895a19c6cedbb92c5e54546daa8a/src/Databricks/generated/api/Databricks.cs#L1204
This may cause some cmdlets to return early with the resource not fully provisioned.
Expected behavior
The cmdlet should start polling until the resource has successfully been provisioned.
The text was updated successfully, but these errors were encountered: