Service Fabric REST API specification version 6.2 RTO#2855
Service Fabric REST API specification version 6.2 RTO#2855annatisch merged 10 commits intoAzure:masterfrom
Conversation
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-libraries-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
| { | ||
| "Key": "__GeneratedServiceType__", | ||
| "Value": null, | ||
| "\"<GeneratedNames xmlns=\"http": //schemas.microsoft.com/2015/03/fabact-no-schema"> <DefaultService Name="WebServerService" /> <ServiceEndpoint Name="WebServerTypeEndpoint" /> </GeneratedNames>" |
| { | ||
| "Key": "__GeneratedServiceType__", | ||
| "Value": null, | ||
| "\"<GeneratedNames xmlns=\"http": //schemas.microsoft.com/2015/03/fabact-no-schema"> <DefaultService Name="WebServerService" /> <ServiceEndpoint Name="WebServerTypeEndpoint" /> </GeneratedNames>" |
There was a problem hiding this comment.
thanks let me look in to it.
|
@annatisch - the issue should be resolved now. This should have been caught with our internal CI/build process on the Service Fabric swagger specification repo. We will improve this. @salameer |
|
Thanks @VipulM-MSFT. And many of the models: Could you take a look? |
|
@annatisch - this is not an Azure API specifications so the naming suppressions are already part of the README.MD and approved @salameer . @salameer - do you know why CI is not picking up the suppressions from the README.MD? This job https://travis-ci.org/Azure/azure-rest-api-specs/jobs/365940147 has failures that are already suppressed in README. |
|
We also suppress the example validations due to issues in the validation tooling. Once they are fixed we can re-enable the checks and those failures should turn in to blocking failures. @salameer has the context on the issues. |
|
@VipulM-MSFT I believe the supressions need to be in the README.md at the root of all the versions, the same one that contains the tags for generation. Take a look at this pr that added supressions. |
|
#hold-off There are genuine failures in the example validation, we will fix and update the PR with those and ensure that the suppressions are added at the root. Let's wait on merging this PR for now, until I and @samedder sign off again. |
…nder data-plane directory.
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
@salameer and @annatisch this is ready to go. All issues should be fixed now. #sign-off |
|
Ping - @salameer and @annatisch |
|
@VipulM-MSFT This creates strange formatting in the generated SDKs for example: |
|
@annatisch - the SDK generators should trim before generating the descriptions. I have removed the newlines. If there are no other issues, please publish the specification. |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
Wandisco.Fusion - Creating new API version 2020-12-01-preview
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger