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

Microsoft.Authorization/policy* entities 2019-09-01 #7380

Merged
merged 4 commits into from
Oct 30, 2019

Conversation

pilor
Copy link
Contributor

@pilor pilor commented Oct 1, 2019

Compare to iteration 1 to see diffs from the previous api-version.

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.

@pilor pilor added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required DoNotMerge <valid label in PR review process> use to hold merge after approval labels Oct 1, 2019
@pilor pilor requested a review from Tiano2017 as a code owner October 1, 2019 22:15
@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Oct 1, 2019

In Testing, Please Ignore

[Logs] (Generated from d01dc89, Iteration 4)

Warning .NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
  • No packages generated.
Failed Python: test-repo-billy/azure-sdk-for-python [Logs]
  • No packages generated.
Failed Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]
  • Failed features/resource-manager/v2015_12_01 [Logs] [Generation PR]
  • Failed locks/resource-manager/v2016_09_01 [Logs]
  • Failed policy/resource-manager/v2016_12_01 [Logs]
  • Failed policy/resource-manager/v2018_03_01 [Logs]
  • Failed policy/resource-manager/v2018_05_01 [Logs]
  • Failed policy/resource-manager/v2019_01_01 [Logs]
  • Failed policy/resource-manager/v2019_06_01 [Logs]
  • Failed policy/resource-manager/v2019_09_01 [Logs]
  • Failed resources/resource-manager/v2016_06_01 [Logs]
  • Failed resources/resource-manager/v2016_09_01 [Logs]
  • Failed resources/resource-manager/v2018_02_01 [Logs]
  • Failed resources/resource-manager/v2018_06_01 [Logs]
  • Failed resources/resource-manager/v2019_03_01 [Logs]
  • Failed resources/resource-manager/v2019_05_01 [Logs]
  • Failed resources/resource-manager/v2019_05_10 [Logs]
  • Failed resources/resource-manager/v2019_06_01 [Logs]
  • Failed resources/resource-manager/v2019_07_01 [Logs]
  • Failed resources/resource-manager/v2019_08_01 [Logs]
Succeeded Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
Succeeded JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]

@AutorestCI
Copy link

AutorestCI commented Oct 1, 2019

Automation for azure-sdk-for-python

Encountered a Subprocess error: (azure-sdk-for-python)

Command: ['/usr/local/bin/autorest', '/tmp/tmpvxxjqrlm/rest/specification/resources/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmp0a9crve1']
Finished with return code 7
and output:

AutoRest code generation utility [version: 2.0.4283; node: v8.12.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Failure:
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4405/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4405/node_modules/@microsoft.azure/autorest-core
    at main (/opt/node_modules/autorest/dist/app.js:232:19)
    at <anonymous>

/root/.autorest/@microsoft.azure_autorest-core@2.0.4405/node_modules/@microsoft.azure/autorest-core/dist/app.js:33
    autorest_core_1.Shutdown();
    ^
ReferenceError: autorest_core_1 is not defined
    at process.on (/root/.autorest/@microsoft.azure_autorest-core@2.0.4405/node_modules/@microsoft.azure/autorest-core/dist/app.js:33:5)
    at emitOne (events.js:121:20)
    at process.emit (events.js:211:7)
    at process.emit (/node_modules/source-map-support/source-map-support.js:439:21)
fs.js:612
  return binding.close(fd);
                 ^

Error: EBADF: bad file descriptor, close
    at Object.fs.closeSync (fs.js:612:18)
    at StaticVolumeFile.shutdown (/opt/node_modules/autorest/dist/static-loader.js:352:10)
    at StaticFilesystem.shutdown (/opt/node_modules/autorest/dist/static-loader.js:406:17)
    at process.exit.n [as exit] (/opt/node_modules/autorest/dist/static-loader.js:169:11)
    at printErrorAndExit (/node_modules/source-map-support/source-map-support.js:423:11)
    at process.emit (/node_modules/source-map-support/source-map-support.js:435:16)
    at process._fatalException (bootstrap_node.js:391:26)

@AutorestCI
Copy link

AutorestCI commented Oct 1, 2019

Automation for azure-sdk-for-go

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@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 Oct 2, 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.

Looks good from ARM side.

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.

Re-reviewed after latest commit. Still looks good from ARM side.

@pilor
Copy link
Contributor Author

pilor commented Oct 29, 2019

@myronfanqiu This is ready to merge whenever you get a chance

Copy link
Contributor

@mmyyrroonn mmyyrroonn left a comment

Choose a reason for hiding this comment

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

LGTM. Just left one comment. Since the assignee is @zikalino, I will leave to him to merge this PR.

"description": "The policy's excluded scopes."
},
"parameters": {
"type": "object",
Copy link
Contributor

Choose a reason for hiding this comment

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

I tried the previous api-version before. For the generated SDK, it's hard to know what is the right structure for this field. Is it possible to add the doc link into the description?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've changed parameters to an explicit model. If this is too much of a breaking change in downstream SDKs I can revert. However, it will greatly increase quality of life for consumers of the generated code.

@zikalino zikalino merged commit dba69f2 into Azure:master Oct 30, 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