Skip to content

Service Fabric REST API specification version 6.2 RTO#2855

Merged
annatisch merged 10 commits intoAzure:masterfrom
vipul-modi:master
Apr 20, 2018
Merged

Service Fabric REST API specification version 6.2 RTO#2855
annatisch merged 10 commits intoAzure:masterfrom
vipul-modi:master

Conversation

@vipul-modi
Copy link

@vipul-modi vipul-modi commented Apr 12, 2018

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes. (Not Applicable)
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@AutorestCI
Copy link

AutorestCI commented Apr 12, 2018

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Apr 12, 2018

Automation for azure-libraries-for-java

The initial PR has been merged into your service PR:
AutorestCI/azure-libraries-for-java#102

@AutorestCI
Copy link

AutorestCI commented Apr 12, 2018

Automation for azure-sdk-for-node

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

@AutorestCI
Copy link

AutorestCI commented Apr 12, 2018

Automation for azure-sdk-for-go

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

{
"Key": "__GeneratedServiceType__",
"Value": null,
"\"<GeneratedNames xmlns=\"http": //schemas.microsoft.com/2015/03/fabact-no-schema"> <DefaultService Name="WebServerService" /> <ServiceEndpoint Name="WebServerTypeEndpoint" /> </GeneratedNames>"
Copy link
Member

Choose a reason for hiding this comment

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

Some invalid JSON here

{
"Key": "__GeneratedServiceType__",
"Value": null,
"\"<GeneratedNames xmlns=\"http": //schemas.microsoft.com/2015/03/fabact-no-schema"> <DefaultService Name="WebServerService" /> <ServiceEndpoint Name="WebServerTypeEndpoint" /> </GeneratedNames>"
Copy link
Member

Choose a reason for hiding this comment

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

Some invalid JSON here

Copy link
Author

Choose a reason for hiding this comment

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

thanks let me look in to it.

@vipul-modi
Copy link
Author

@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

@annatisch
Copy link
Member

Thanks @VipulM-MSFT.
There are a number of errors in both the model and linter PR_ONLY=true CI jobs, for example there are many properties with this:

"Property named: 'PackageSharingPolicy', for definition: 'DeployServicePackageToNodeDescription' must follow camelCase style. Example: 'packageSharingPolicy'.",

And many of the models:

Found errors in validating the response with statusCode "200" for x-ms-example "Get Correlated events" in operation "GetCorrelatedEventList".:

Could you take a look?

@vipul-modi
Copy link
Author

vipul-modi commented Apr 13, 2018

@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.

@vipul-modi
Copy link
Author

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.

@samedder
Copy link
Contributor

@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.

@vipul-modi
Copy link
Author

#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.

@azuresdkciprbot
Copy link

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: specification/servicefabric/data-plane/readme.md
Before the PR: Warning(s): 9 Error(s): 715
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@vipul-modi
Copy link
Author

vipul-modi commented Apr 19, 2018

@salameer and @annatisch this is ready to go. All issues should be fixed now. #sign-off

@vipul-modi
Copy link
Author

Ping - @salameer and @annatisch

@annatisch
Copy link
Member

@VipulM-MSFT
I can't leave comments on the diff itself because it's too large for Github to load it.
Can you please remove the newline characters from the end of descriptions, for example:

    "BackupSuspensionInfo": {
      "type": "object",
      "description": "Describes the backup suspension details.\n",
      "properties": {
        "IsSuspended": {
          "type": "boolean",
          "description": "Indicates whether periodic backup is suspended at this level or not."
        },
        "SuspensionInheritedFrom": {
          "$ref": "#/definitions/BackupSuspensionScope",
          "description": "Specifies the scope at which the backup suspension was applied.\n"
        }
      }
    },

This creates strange formatting in the generated SDKs for example:

class BackupSuspensionInfo(Model):
    """Describes the backup suspension details.
    .

@vipul-modi
Copy link
Author

@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.

@azuresdkciprbot
Copy link

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: specification/servicefabric/data-plane/readme.md
Before the PR: Warning(s): 9 Error(s): 715
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@annatisch annatisch merged commit f037370 into Azure:master Apr 20, 2018
mccleanp pushed a commit that referenced this pull request Mar 23, 2022
Wandisco.Fusion - Creating new API version 2020-12-01-preview
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.

5 participants

Comments