Skip to content
New issue

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

[Bug fix] Remove read-only constraint for management policy, and change properties types from integer to number #6551

Merged
merged 5 commits into from
Jul 17, 2019

Conversation

zfchen95
Copy link
Contributor

@zfchen95 zfchen95 commented Jul 3, 2019

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 Jul 3, 2019

SDK Automation [Logs] (Generated from 0e6f149, Iteration 6)

Succeeded Python: Azure/azure-sdk-for-python [Logs] [Diff]
Succeeded Java: Azure/azure-sdk-for-java [Logs] [Diff]
Succeeded Go: Azure/azure-sdk-for-go [Logs] [Diff]
Succeeded JavaScript: Azure/azure-sdk-for-js [Logs] [Diff]
Failed Ruby: Azure/azure-sdk-for-ruby [Logs] [Diff]

@AutorestCI
Copy link

AutorestCI commented Jul 3, 2019

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Jul 3, 2019

Automation for azure-sdk-for-java

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

@AutorestCI
Copy link

AutorestCI commented Jul 3, 2019

Automation for azure-sdk-for-go

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@zfchen95 zfchen95 changed the title [Bug fix] Remove read-only constraint for management policy [Bug fix] Remove read-only constraint for management policy, and change properties types to float Jul 5, 2019
@azuresdkci azuresdkci assigned Juliehzl and unassigned NelsonDaniel Jul 5, 2019
@azuresdkci azuresdkci requested a review from Juliehzl July 5, 2019 20:26
@Juliehzl Juliehzl added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 8, 2019
"type": "integer",
"minimum": 0,
"type": "float",
"minimum": 0.0,
"description": "Integer value indicating the age in days after last modification"
Copy link
Contributor

Choose a reason for hiding this comment

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

Description is still calling it an integer

Copy link
Contributor Author

@zfchen95 zfchen95 Jul 11, 2019

Choose a reason for hiding this comment

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

In the server, the property is defined as float type for testing purpose. But in the real use case, we expect the input to be an integer-like number. I added a constraint in the update 0e6f149, which will only allow number that is the multiple of 1.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, but since it's no longer an actual int, the docs shouldn't call it that. Maybe just change "Integer value" to "Value"

Copy link
Contributor Author

@zfchen95 zfchen95 Jul 11, 2019

Choose a reason for hiding this comment

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

Changed "Integer value" to "Value" 870609e

@zfchen95 zfchen95 changed the title [Bug fix] Remove read-only constraint for management policy, and change properties types to float [Bug fix] Remove read-only constraint for management policy, and change properties types to number Jul 11, 2019
@zfchen95 zfchen95 changed the title [Bug fix] Remove read-only constraint for management policy, and change properties types to number [Bug fix] Remove read-only constraint for management policy, and change properties types from integer to number Jul 11, 2019
Copy link
Contributor

@ryansbenson ryansbenson left a comment

Choose a reason for hiding this comment

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

Approved from ARMs side

@ryansbenson ryansbenson 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 Jul 11, 2019
@Juliehzl
Copy link
Contributor

@myronfanqiu Please have a look at Ruby SDK.

@Juliehzl
Copy link
Contributor

@zfchen95 Please have a look at checklist and try to fix the error in public.rest-api-specs.

@mmyyrroonn
Copy link
Contributor

@myronfanqiu Please have a look at Ruby SDK.

It's a known issue in the SDK Automation. It doesn't block the real SDK generation process. Currently, we are working on it.

@zfchen95
Copy link
Contributor Author

@zfchen95 Please have a look at checklist and try to fix the error in public.rest-api-specs.

Hi @Juliehzl, I looked at the errors in public.rest-api-specs (model validation) test. None of them are caused by the change in this PR. Actually, all the errors are caused by "missing" schema in the storage swagger. I will try to fix them in another PR, not in this one because it will require an additional review..

message: >-  
  Response statusCode "200" for operation "StorageAccounts_Failover" has
  response body provided in the example, however the response does not have a
  "schema" defined in the swagger spec.

https://dev.azure.com/azure-sdk/public/_build/results?buildId=66099&view=logs&j=8d2f9c49-cd83-5a9d-f3fe-2fd651afa742&t=43324f1f-6724-5d61-785f-f0ac9fd256a1&l=25

@zfchen95
Copy link
Contributor Author

@zfchen95 Please have a look at checklist and try to fix the error in public.rest-api-specs.

I have fixed the errors in #6611
If public.rest-api-specs pass is required, I could rebase this PR on another. Otherwise, it should be fine to merge..

@Juliehzl
Copy link
Contributor

Yes. Please make changes in this PR.

@zfchen95
Copy link
Contributor Author

Yes. Please make changes in this PR.

Updated. All the checks pass.

@zfchen95
Copy link
Contributor Author

@Juliehzl Could you approve it?

@Juliehzl Juliehzl merged commit df89eaf into Azure:master Jul 17, 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.

9 participants