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

Fixexamples #3092

Closed
wants to merge 10 commits into from
Closed

Fixexamples #3092

wants to merge 10 commits into from

Conversation

vinayada1
Copy link
Contributor

@vinayada1 vinayada1 commented May 16, 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.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

EvgenyAgafonchikov and others added 8 commits May 7, 2018 16:18
* Created May folder. Updated version for exampls, commands

* Updated package to May version

* Returned NW examples

* Fixed API version; Fixed NetworkWatcher examples

* Fixed VPN Gateway/Connection examples

* Add changes from PR#2975
https://github.com/Azure/azure-rest-api-specs/pull/2975/files
…nfig object for enhancing the Network Watcher cmdlets (Azure#3023)

* Adding optional traffic analytics parameters with existing network watched flowlog configuration

* Updating the version

* Updating latest versoin in readme.md
* Adding optional traffic analytics parameters with existing network watched flowlog configuration

* Updating the version

* Updating latest versoin in readme.md

* Adding optional traffic analytics parameters with flowlog parameters

* Reverting old chnages
Expose new SKUs for VMSS VPN and ER gateways
* Initial network error fixes and suppressions

* reworked exception to specified code blocks only

* Added express route fixes
@AutorestCI
Copy link

AutorestCI commented May 16, 2018

Automation for azure-libraries-for-java

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

Command: ['/usr/local/bin/autorest', '/tmp/tmp_u57iwo2/rest/specification/network/resource-manager/readme.md', '--azure-libraries-for-java-folder=/tmp/tmp_u57iwo2/sdk', '--fluent', '--java', '--multiapi', '--verbose']
Finished with return code 1
and output:

AutoRest code generation utility [version: 2.0.4262; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/root/.autorest/@microsoft.azure_autorest-core@2.0.4278/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4278)
   Loading AutoRest extension '@microsoft.azure/autorest.java' (~2.1.32->2.1.70)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
ERROR: Syntax Error Encountered: Unexpected token , in JSON
    - file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1928:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1945:0
ERROR: Syntax error: expected a single document in the stream, but found more
    - file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
FATAL: swagger-document/loader - FAILED
FATAL: Error: Syntax errors encountered.
Process() cancelled due to exception : Syntax errors encountered.
  Error: Syntax errors encountered.

@AutorestCI
Copy link

AutorestCI commented May 16, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented May 17, 2018

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

@AutorestCI
Copy link

AutorestCI commented May 17, 2018

Automation for azure-sdk-for-go

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

Command: ['/usr/local/bin/autorest', '/tmp/tmp3xhistop/rest/specification/network/resource-manager/readme.md', '--go', '--go-sdk-folder=/tmp/tmp3xhistop/src/github.com/Azure/azure-sdk-for-go', '--multiapi', '--use=@microsoft.azure/autorest.go@~2.1.105', '--use-onever', '--verbose']
Finished with return code 1
and output:

AutoRest code generation utility [version: 2.0.4280; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/root/.autorest/@microsoft.azure_autorest-core@2.0.4280/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4280)
   Loading AutoRest extension '@microsoft.azure/autorest.go' (~2.1.105->2.1.105)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
Processing batch task - {"tag":"package-2018-05"} .
ERROR: Syntax Error Encountered: Unexpected token , in JSON
    - file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1928:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1945:0
ERROR: Syntax error: expected a single document in the stream, but found more
    - file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
FATAL: swagger-document/loader - FAILED
FATAL: Error: Syntax errors encountered.
Process() cancelled due to exception : Syntax errors encountered.
Failure during batch task - {"tag":"package-2018-05"} -- Error: Syntax errors encountered..
  Error: Syntax errors encountered.

@@ -0,0 +1 @@
{ "parameters": { "expressRouteCircuitName": "circuitName", "resourceGroupName": "rg1", "api-version": "2017-11-01", "subscriptionId": "subid", "peeringName": "peeringName", "devicePath": "devicePath" }, "responses": { "200": { "value": [ { "age": 0, "interface": "Microsoft", "ipAddress": "IPAddress", "macAddress": "macAddress" } ] }, "202": { "value": [ { "age": 0, "interface": "Microsoft", "ipAddress": "IPAddress", "macAddress": "macAddress" } ] } } }
Copy link
Contributor

Choose a reason for hiding this comment

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

Please configure your git to check in Unix style line endings.

Copy link
Contributor

Choose a reason for hiding this comment

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

@gimotwanMSFT was it done?

@AutorestCI
Copy link

AutorestCI commented May 26, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

Copy link
Contributor

@MikhailTryakhov MikhailTryakhov left a comment

Choose a reason for hiding this comment

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

Please follow comments in the PR

@MikhailTryakhov
Copy link
Contributor

@gimotwanMSFT please push your PR to Network-2018-06-01 branch, merge your changes with master.

@MikhailTryakhov
Copy link
Contributor

@gimotwanMSFT please make your changes in 2018-06-01 folder instead of May one

@AutorestCI
Copy link

AutorestCI commented Jul 3, 2018

Automation for azure-sdk-for-java

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

Command: ['/usr/local/bin/autorest', '/tmp/tmpy04otfnh/rest/specification/network/resource-manager/readme.md', '--azure-libraries-for-java-folder=/tmp/tmpy04otfnh/sdk', '--java', '--multiapi', '--use=@microsoft.azure/autorest.java@2.1.71', '--verbose']
Finished with return code 1
and output:

AutoRest code generation utility [version: 2.0.4280; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/root/.autorest/@microsoft.azure_autorest-core@2.0.4280/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4280)
   Loading AutoRest extension '@microsoft.azure/autorest.java' (2.1.71->2.1.71)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
Processing batch task - {"tag":"package-2018-05"} .
ERROR: Syntax Error Encountered: Unexpected token , in JSON
    - file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1928:3
ERROR: Syntax error: end of the stream or a document separator is expected
    - file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1945:0
ERROR: Syntax error: expected a single document in the stream, but found more
    - file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
FATAL: swagger-document/loader - FAILED
FATAL: Error: Syntax errors encountered.
Process() cancelled due to exception : Syntax errors encountered.
Failure during batch task - {"tag":"package-2018-05"} -- Error: Syntax errors encountered..
  Error: Syntax errors encountered.

mccleanp pushed a commit that referenced this pull request Mar 23, 2022
Removing header details in the swagger
konrad-jamrozik pushed a commit to dhung-msft/azure-rest-api-specs that referenced this pull request Dec 4, 2023
…tch-7

[Internal testing] testing openapi-alps PR 510778 - Test 11/15/2023 / 1
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.

9 participants