Skip to content

Conversation

@leonardbf
Copy link
Contributor

@leonardbf leonardbf commented Dec 4, 2018

  • Incorrect pool resource reference
  • Name elements of property not required
  • Correction to return status code
  • Add put (and patch) for snapshots.
  • Service level definition changes.
  • (NetApp internal ticket NFSAAS-1505)

Note : breaking changes are acceptable as this is for the initial RP version (previously only preview).

leonardbf and others added 8 commits November 20, 2018 08:04
NFSAAS-1505 minor update and validation fixes
Put (and patch) for snapshots.
Service level definition changes.
NFSAAS-1505 correct resource reference and limits
Incorrect pool resource reference
Name elements of property not required
Correction to return status code
NFSAAS-1505 resource and property changes
@openapi-portal-comment
Copy link

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-python

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@amarzavery
Copy link
Contributor

@leonardbf
There are errors in the model validator, please fix them. Either the example is correct or the schema definition.

Validating "examples" and "x-ms-examples" in  specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json:
 error : 
operationId: Accounts_List
scenario: Accounts_List
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - accountId
  message: 'Additional properties not allowed: accountId'
  path: value/0/properties
  title: /definitions/accountProperties
  description: NetApp account properties
  position:
    line: 1164
    column: 26
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 13
    column: 27
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Accounts_List.json
 error : 
operationId: Accounts_Get
scenario: Accounts_Get
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - accountId
  message: 'Additional properties not allowed: accountId'
  path: properties
  title: /definitions/accountProperties
  description: NetApp account properties
  position:
    line: 1164
    column: 26
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 12
    column: 25
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Accounts_Get.json
 error : 
operationId: Accounts_CreateOrUpdate
scenario: Accounts_CreateOrUpdate
source: response
responseCode: '200'
severity: 0
errorCode: RESPONSE_STATUS_CODE_NOT_IN_SPEC
errorDetails:
  code: RESPONSE_STATUS_CODE_NOT_IN_SPEC
  id: OAV112
  message: >-
    Response statusCode "200" for operation "Accounts_CreateOrUpdate" is
    provided in exampleResponseValue, however it is not present in the swagger
    spec.
  level: error
 error : 
operationId: Accounts_CreateOrUpdate
scenario: Accounts_CreateOrUpdate
source: response
responseCode: '201'
severity: 0
errorCode: RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE
errorDetails:
  code: RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE
  id: OAV111
  message: >-
    Following response status codes "201" for operation
    "Accounts_CreateOrUpdate" were present in the swagger spec, however they
    were not present in x-ms-examples. Please provide them.
  level: error
 error : 
operationId: Accounts_Update
scenario: Accounts_Update
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - accountId
  message: 'Additional properties not allowed: accountId'
  path: properties
  title: /definitions/accountProperties
  description: NetApp account properties
  position:
    line: 1164
    column: 26
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 13
    column: 23
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Accounts_Update.json
 error : 
operationId: Pools_List
scenario: Pools_List
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - accountId
  message: 'Additional properties not allowed: accountId'
  path: value/0/properties
  title: /definitions/poolProperties
  description: Pool properties
  position:
    line: 1242
    column: 23
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 14
    column: 27
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Pools_List.json
 error : 
operationId: Pools_Get
scenario: Pools_Get
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - accountId
  message: 'Additional properties not allowed: accountId'
  path: properties
  title: /definitions/poolProperties
  description: Pool properties
  position:
    line: 1242
    column: 23
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 13
    column: 23
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Pools_Get.json
 error : 
operationId: Pools_CreateOrUpdate
scenario: Pools_CreateOrUpdate
source: response
responseCode: '200'
severity: 0
errorCode: RESPONSE_STATUS_CODE_NOT_IN_SPEC
errorDetails:
  code: RESPONSE_STATUS_CODE_NOT_IN_SPEC
  id: OAV112
  message: >-
    Response statusCode "200" for operation "Pools_CreateOrUpdate" is provided
    in exampleResponseValue, however it is not present in the swagger spec.
  level: error
 error : 
operationId: Pools_CreateOrUpdate
scenario: Pools_CreateOrUpdate
source: response
responseCode: '201'
severity: 0
errorCode: RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE
errorDetails:
  code: RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE
  id: OAV111
  message: >-
    Following response status codes "201" for operation "Pools_CreateOrUpdate"
    were present in the swagger spec, however they were not present in
    x-ms-examples. Please provide them.
  level: error
 error : 
operationId: Pools_Update
scenario: Pools_Update
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - accountId
  message: 'Additional properties not allowed: accountId'
  path: properties
  title: /definitions/poolProperties
  description: Pool properties
  position:
    line: 1242
    column: 23
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 14
    column: 23
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Pools_Update.json
 error : 
operationId: Volumes_List
scenario: Volumes_List
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - name
  message: 'Additional properties not allowed: name'
  path: value/0/properties
  title: /definitions/volumeProperties
  description: Volume properties
  position:
    line: 1362
    column: 25
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 15
    column: 27
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Volumes_List.json
 error : 
operationId: Volumes_Get
scenario: Volumes_Get
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - name
  message: 'Additional properties not allowed: name'
  path: properties
  title: /definitions/volumeProperties
  description: Volume properties
  position:
    line: 1362
    column: 25
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 14
    column: 23
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Volumes_Get.json
 error : 
operationId: Volumes_CreateOrUpdate
scenario: Volumes_CreateOrUpdate
source: response
responseCode: '200'
severity: 0
errorCode: RESPONSE_STATUS_CODE_NOT_IN_SPEC
errorDetails:
  code: RESPONSE_STATUS_CODE_NOT_IN_SPEC
  id: OAV112
  message: >-
    Response statusCode "200" for operation "Volumes_CreateOrUpdate" is provided
    in exampleResponseValue, however it is not present in the swagger spec.
  level: error
 error : 
operationId: Volumes_CreateOrUpdate
scenario: Volumes_CreateOrUpdate
source: response
responseCode: '201'
severity: 0
errorCode: RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE
errorDetails:
  code: RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE
  id: OAV111
  message: >-
    Following response status codes "201" for operation "Volumes_CreateOrUpdate"
    were present in the swagger spec, however they were not present in
    x-ms-examples. Please provide them.
  level: error
 error : 
operationId: Volumes_Update
scenario: Volumes_Update
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - name
  message: 'Additional properties not allowed: name'
  path: properties
  title: /definitions/volumeProperties
  description: Volume properties
  position:
    line: 1362
    column: 25
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 15
    column: 23
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Volumes_Update.json
 error : 
operationId: MountTargets_List
scenario: MountTargets_List
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - name
  message: 'Additional properties not allowed: name'
  path: value/0/properties
  title: /definitions/mountTargetProperties
  description: Mount target properties
  position:
    line: 1567
    column: 30
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 16
    column: 27
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/MountTargets_List.json
 error : 
operationId: MountTargets_Get
scenario: MountTargets_Get
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - name
  message: 'Additional properties not allowed: name'
  path: properties
  title: /definitions/mountTargetProperties
  description: Mount target properties
  position:
    line: 1567
    column: 30
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 15
    column: 23
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/MountTargets_Get.json
 error : 
operationId: Snapshots_List
scenario: Snapshots_List
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - name
  message: 'Additional properties not allowed: name'
  path: value/0/properties
  title: /definitions/snapshotProperties
  description: Snapshot properties
  position:
    line: 1706
    column: 27
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 16
    column: 27
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Snapshots_List.json
 error : 
operationId: Snapshots_Get
scenario: Snapshots_Get
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - name
  message: 'Additional properties not allowed: name'
  path: properties
  title: /definitions/snapshotProperties
  description: Snapshot properties
  position:
    line: 1706
    column: 27
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 15
    column: 23
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Snapshots_Get.json
 error : 
operationId: Snapshots_Create
scenario: Snapshots_Create
source: response
responseCode: '200'
severity: 0
errorCode: RESPONSE_STATUS_CODE_NOT_IN_SPEC
errorDetails:
  code: RESPONSE_STATUS_CODE_NOT_IN_SPEC
  id: OAV112
  message: >-
    Response statusCode "200" for operation "Snapshots_Create" is provided in
    exampleResponseValue, however it is not present in the swagger spec.
  level: error
 error : 
operationId: Snapshots_Create
scenario: Snapshots_Create
source: response
responseCode: '201'
severity: 0
errorCode: RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE
errorDetails:
  code: RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE
  id: OAV111
  message: >-
    Following response status codes "201" for operation "Snapshots_Create" were
    present in the swagger spec, however they were not present in x-ms-examples.
    Please provide them.
  level: error
 error : 
operationId: Snapshots_Update
scenario: Snapshots_Update
source: response
responseCode: '200'
severity: 0
errorCode: OBJECT_ADDITIONAL_PROPERTIES
errorDetails:
  code: OBJECT_ADDITIONAL_PROPERTIES
  params:
    - - name
  message: 'Additional properties not allowed: name'
  path: properties
  title: /definitions/snapshotProperties
  description: Snapshot properties
  position:
    line: 1706
    column: 27
  url: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/netapp.json
  directives: {}
  jsonPosition:
    line: 16
    column: 23
  jsonUrl: >-
    specification/netapp/resource-manager/Microsoft.NetApp/preview/2017-08-15/examples/Snapshots_Update.json

@leonardbf
Copy link
Contributor Author

Examples updated, @amarzavery .

@amarzavery amarzavery merged commit 1b63166 into Azure:master Dec 5, 2018
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Feb 6, 2019
* NFSAAS-1505 minor update and validation fixes

* NFSAAS-1505 bring in line with RP

Put (and patch) for snapshots.
Service level definition changes.

* NFSAAS-1505 correct resource reference and limits

* NFSAAS-1505 resource and property changes

Incorrect pool resource reference
Name elements of property not required
Correction to return status code

* NFSAAS-1505 status codes

* NFSAAS-1505 tidy up examples

* NFSAAS-1505 tidy up examples
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.

4 participants