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

Add a new field to SignalR Resource property #5661

Merged
merged 3 commits into from
May 29, 2019

Conversation

juniwang
Copy link
Contributor

Changes:

  • Add new property features to SignalRResource, which will used to query or update the FeatureFlags of SignalR resource. Corresponding examples updated.
  • remove enum property of api-version. The extra enum will fail .NET SDK generation
  • Add x-ms-long-running-operation-options for long runnint operations.

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.

@AutorestCI
Copy link

AutorestCI commented Apr 16, 2019

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#5532

@AutorestCI
Copy link

AutorestCI commented Apr 16, 2019

Automation for azure-sdk-for-js

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-js#3268

@AutorestCI
Copy link

AutorestCI commented Apr 16, 2019

Automation for azure-sdk-for-ruby

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-ruby#2514

@AutorestCI
Copy link

AutorestCI commented Apr 16, 2019

Automation for azure-sdk-for-go

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

@AutorestCI
Copy link

AutorestCI commented Apr 16, 2019

Automation for azure-sdk-for-java

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

Command: ['/usr/local/bin/autorest', '/tmp/tmpemwsrxce/rest/specification/signalr/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmphook_9rm']
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/@[email protected]/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core
    at main (/opt/node_modules/autorest/dist/app.js:232:19)
    at <anonymous>

/root/.autorest/@[email protected]/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/@[email protected]/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)

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

adxsdknet added a commit to adxsdknet/azure-sdk-for-net that referenced this pull request Apr 16, 2019
REST Spec PR 'Azure/azure-rest-api-specs#5661'
REST Spec PR Author 'juniwang'
REST Spec PR Last commit
@adxsdknet
Copy link

adxsdknet commented Apr 16, 2019

Automation for azure-sdk-for-net

A PR has been created for you:
Azure/azure-sdk-for-net#5823
.NET SDK Commits:
adxsdknet/azure-sdk-for-net@5ebc936
adxsdknet/azure-sdk-for-net@0686f82
adxsdknet/azure-sdk-for-net@9eed052

@dsgouda
Copy link
Contributor

dsgouda commented Apr 16, 2019

@juniwang Please fix the merge conflicts

@dsgouda dsgouda added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 16, 2019
Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

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

LGTM

@dsgouda dsgouda removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 16, 2019
@dsgouda
Copy link
Contributor

dsgouda commented Apr 16, 2019

stable version but additive changes, don't need ARM approval.

Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

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

Will approve once merge conflicts are resolved.

@juniwang
Copy link
Contributor Author

Will approve once merge conflicts are resolved.
@dsgouda Conflicts resolved

@dsgouda
Copy link
Contributor

dsgouda commented Apr 17, 2019

@shahabhijeet @NelsonDaniel Please approve

Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

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

@juniwang the diffs here are hard to read, can you pull latest changes from master and reapply your chanes

@juniwang
Copy link
Contributor Author

@dsgouda Thanks. Resetted using master branch and applid changes.

@juniwang
Copy link
Contributor Author

@dsgouda @shahabhijeet Could you have a review again?

@dsgouda
Copy link
Contributor

dsgouda commented Apr 25, 2019

@shahabhijeet PTAL

@juniwang
Copy link
Contributor Author

Hi @shahabhijeet, Could you please have another review? It seems that the PR is blocked by you

adxsdknet added a commit to adxsdknet/azure-sdk-for-net that referenced this pull request May 13, 2019
REST Spec PR 'Azure/azure-rest-api-specs#5661'
REST Spec PR Author 'juniwang'
REST Spec PR Last commit
Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

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

Left a couple of comments

"additionalProperties": {
"type": "string"
},
"x-ms-client-flatten": false
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: This doesn't need to be set explicitly

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed. This produces a warning:

WARNING (AvoidNestedProperties/R2001/SDKViolation): Consider using x-ms-client-flatten to provide a better end user experience
    - file:///mnt/d/workspace/github/juniwang/azure-rest-api-specs/specification/signalr/resource-manager/Microsoft.SignalRService/stable/2018-10-01/signalr.json:924:8 ($.definitions.SignalRFeature.properties.properties)

If it doens't matter, we may suppress the warning in future.

Copy link
Contributor

@dsgouda dsgouda May 14, 2019

Choose a reason for hiding this comment

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

I see, we discourage too many levels of nesting especially on input parameters hence the warning. Please mark x-ms-client-flatten: true

"type": "object",
"properties": {
"flag": {
"description": "Name of the feature. Required.",
Copy link
Contributor

Choose a reason for hiding this comment

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

The description is a bit confusing since there can only be a limited number of values. Type/kind of feature makes more sense?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see any changes, not blocker though

@@ -319,6 +322,9 @@
}
},
"x-ms-long-running-operation": true,
"x-ms-long-running-operation-options": {
"final-state-via": "azure-async-operation"
Copy link
Member

Choose a reason for hiding this comment

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

@juniwang any reason you are adding this to PUT operations? I was under the impression that this is only for POST.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Telling from this doc: When x-ms-long-running-operation is specified, there should also be a x-ms-long-running-operation-options specified..

Will remove it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed

@@ -354,6 +360,9 @@
}
},
"x-ms-long-running-operation": true,
"x-ms-long-running-operation-options": {
"final-state-via": "azure-async-operation"
Copy link
Member

Choose a reason for hiding this comment

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

@juniwang same as above, why specify for delete?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed

adxsdknet added a commit to adxsdknet/azure-sdk-for-net that referenced this pull request May 14, 2019
REST Spec PR 'Azure/azure-rest-api-specs#5661'
REST Spec PR Author 'juniwang'
REST Spec PR Last commit
@juniwang
Copy link
Contributor Author

@shahabhijeet @dsgouda spec updated to rosolve comments

@juniwang
Copy link
Contributor Author

@shahabhijeet PTAL

@juniwang
Copy link
Contributor Author

@shahabhijeet any other comments? Or can someone review again on behalf of Abhijeet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants