Skip to content

Conversation

@erelh
Copy link
Contributor

@erelh erelh commented Feb 12, 2020

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.

@AutorestCI
Copy link

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask [email protected] (or NullMDR in github) for additional help.

@erelh
Copy link
Contributor Author

erelh commented Feb 12, 2020

@ArcturusZhang @tjprescott can you please review? thanks

@ArcturusZhang
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Feb 12, 2020

azure-sdk-for-java - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Feb 12, 2020

azure-sdk-for-go - Release

️✔️ succeeded [Logs] [Expand Details]

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Feb 12, 2020

azure-sdk-for-net - Release

️✔️ succeeded [Logs] [Expand Details]

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Feb 12, 2020

azure-sdk-for-js - Release

️✔️ succeeded [Logs] [Expand Details]
  • ️✔️ Generate from d9d0078 with merge commit 292c7ad. SDK Automation 13.0.17.20191226.1
  • ️✔️@azure/arm-security [Logs]  [Release SDK Changes]
    [npmPack] npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-node-resolve.
    [npmPack] loaded rollup.config.js with warnings
    [npmPack] (!) Unused external imports
    [npmPack] default imported from external module 'rollup' but never used
    [npmPack] 
    [npmPack] ./esm/securityCenter.js → ./dist/arm-security.js...
    [npmPack] created ./dist/arm-security.js in 757ms

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Feb 12, 2020

azure-sdk-for-python - Release

️✔️ succeeded [Logs] [Expand Details]
  • ️✔️ Generate from d9d0078 with merge commit 292c7ad. SDK Automation 13.0.17.20191226.1
  • ️✔️azure-mgmt-security [Logs]  [Release SDK Changes]
    [build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
    [build_package]   warnings.warn(msg)
    [build_package] warning: no files found matching '*.py' under directory 'tests'
    [build_package] warning: no files found matching '*.yaml' under directory 'tests'
    [build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
    [build_package]   warnings.warn(msg)
    [build_package] warning: no files found matching '*.py' under directory 'tests'
    [build_package] warning: no files found matching '*.yaml' under directory 'tests'

Comment on lines 201 to 203
"404": {
"description": "NotFound"
},
Copy link
Member

Choose a reason for hiding this comment

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

Should it be 204 when we are trying to delete an item that does not exist?
Randomly picked example:

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@tjprescott
Copy link
Member

LGTM. Is this PR sufficient or do you still need the other one open with all of the other changes?

@erelh
Copy link
Contributor Author

erelh commented Feb 13, 2020

@tjprescott i don't need the other one open, you can close it

@ArcturusZhang
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@tjprescott
Copy link
Member

Is this a management or data plane swagger? Data plane swaggers aren't reviewed by ARM. @ArcturusZhang

@ArcturusZhang
Copy link
Member

Is this a management or data plane swagger? Data plane swaggers aren't reviewed by ARM. @ArcturusZhang

Well, the changed file is under resource-manager directory, I suppose this is a management-plane swagger.

@erelh
Copy link
Contributor Author

erelh commented Feb 16, 2020

@ArcturusZhang @tjprescott what is blocking this PR from being reviewed & merged ?

@tjprescott
Copy link
Member

As this is a management plane change, it should be reviewed by the ARM team first and then the management SDKs team in Shanghai. I'm part of the data plane SDKs team, so the bot should not have assigned the original PR to me. I suspect it did so because of all the changes that were pulled into that (the reason so many people were tagged as code owners). @KrisBash who would be the right ARM team member to review this?

@erelh
Copy link
Contributor Author

erelh commented Feb 18, 2020

@KrisBash @ArcturusZhang can you please assist in getting a reviewer for this change ?
Thanks

@erelh
Copy link
Contributor Author

erelh commented Feb 23, 2020

@ravbhatnagar - are you OnCall now ? can you please review?

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

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 Feb 27, 2020
@ArcturusZhang ArcturusZhang merged commit 292c7ad into Azure:master Feb 28, 2020
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