{"_id":"@axway/api-builder-plugin-fn-swagger","_rev":"294-756ebbf71f40b677b50e7fd87f4ef6d0","name":"@axway/api-builder-plugin-fn-swagger","dist-tags":{"oas3-poc":"2.7.0-rdpp-6269.fcdbdf.0","qom":"3.2.4","riga":"3.2.5","next":"3.2.6","sunnyvale":"3.2.6","tauranga":"3.2.6","unna":"3.2.7","villasimius":"3.2.8","austen":"4.0.0","beckett":"4.0.0","christie":"4.0.1","wicklow":"3.2.9","xiangxiang":"3.2.9","dickens":"4.0.2","ellison":"4.0.2","fleming":"4.0.2","glaspell":"4.1.0","huxley":"4.2.0","yangon":"3.3.0","latest":"4.2.1","irving":"4.2.1","lee":"4.2.1","joyce":"4.2.1","king":"4.2.1","latest-4":"3.3.1","zaanstad":"3.3.1"},"versions":{"1.0.0-1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0-1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0-1","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"81817c5c5f35d801ee2c6b7cbb0751c3255e4777","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0-1.tgz","fileCount":13,"integrity":"sha512-7RCKOnVOkzUa26+X4bHS3pVCZ+i7HqpLdfDLAnFM2ml6XFP5hiEr+1UXRjGiOYBZsGYdSjnRTCaX8Mam7mJREg==","signatures":[{"sig":"MEQCIFJXeKIDitGkZubutuqeiVu+ie6+okMi2KPy11AVGER4AiAWCkWTeisNMWS7drjIIa8K/YCBs2h/MyR9Zzq/EApmaw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":66864,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbJuGyCRA9TVsSAnZWagAAxnIP/0NRIwUHWHQMBnSlBMDC\nTLnrtORLlrjDc92jQZ/1LukdMOH4nDJrpga5H7srIU9CbOvz8yHyMBCbDrWi\nyIgscbjhaXhmlPTC3GJf8TFS4LOSugv9At0Zg47OUPlt+9ySb6NCVmRYhMu6\noBtHPPV9Tu3Q94vtz7GaObain2gQisIEmsE77X1dtCs226AhLrZciSP03ZOR\nUB59Ptc78Nz003EcU+nnwAsa9HkTWIy/NOe7bODrmDDa+niteWB+QeBwg4Rq\nDP6OFUkmTQPdXHGGTdATZGVJdRkdK0rr2SPK1uO7w+j6+O0zTQSGWvPa6kXU\nvJHYKwADutHeCi718UQBjz8wsw1XkB2DOs8C4AuTs0sjQ4iyauRRjUQmv32q\nKZ8d5hCNuTnwLC/EIxwlxcRjouFg5ZdbsJJL6d2lQEpelcE5oUgj8e14kzTO\n6dmE/RFyHfs5pONRhbSYB0iHc/OhG89vXJpnGSfPX3Ok8EdR6Pa0Uvrxn/yf\nLMrnG+JIyY2FfUsKuiZEJdqHG7b3zKuiyFTn5NiBrOFIX0tO1y+dWQyqP+kG\nL/u2pA5MGjWUmgHGWKBo9f8khICyhusHh/pIxyQHVGnzpG15YxuReIqQK0ba\nrZZTtoJjx6brpXlfLZDuch2NGGmN9Yg83l05Z/TU4gtgUSO1ACkdMTCETt4B\n1Gfy\r\n=v0Ld\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/create-swagger.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"old prerelease version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.4","dependencies":{"capitalize":"^1.0.0","@axway/requester":"1.0.1-1","nodehandler-utils":"3.0.0-6"},"_hasShrinkwrap":false,"devDependencies":{"@axway/api-builder-admin":"1.0.0-43"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0-1_1529274800989_0.7279042204799417","host":"s3://npm-registry-packages"}},"1.0.0-2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0-2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0-2","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"57ee48772567c3e97015e739eb8003d02dd9d27f","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0-2.tgz","fileCount":13,"integrity":"sha512-UYrUbPD3vMa0g7P85P5fb7pbItbU6IfFypdEa6JL3wD1nNEo8MrM/6NhfQu79GdfPTklvbFBGrXhLQJgOfCa1Q==","signatures":[{"sig":"MEYCIQC0991yKCGbExOixvw//3NDF9yAyYnLzPH/QY0soka4SwIhAP3aqEgHUnQawRpfZOwwubJUZsUIzB4df3HDf+igyDQN","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":66864,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbJ6EzCRA9TVsSAnZWagAAqWQP/1jLSvDmhOiCN8gOWMqk\ncnyEcjfJWR2nswmTsDD+aPc2DZ1Z3LHWdezN8czpPs7hB20nBJu9yyk0Q4iQ\nTjWBJoJPhx+7Gmx71cF7I16bGE7MzKQAPBni6b0sryUKHgqP2M0Hw7piuFEF\nVPZ0QTa4l7fSPAg2v6YI6K4zjjlKVG7YAbqlHF2o4NDb0KyhayOGzD9p2NyD\nL06wFJ3nlyR9otza8kC8lnNNn1Ln4uDnAONbRhA+ZVRgf0VExg/4OYiJeiYI\nLyf+F5cUAiXllW+FJGEvocLOMpCV/1qaqaX2K2qekeOjHGeyYPTq0gDpANtA\nkvcss+QE2IN0/+vjRKJyJNuF2u4FUBHknAAbwqmGwK12jFN2qA/J3mTMD003\nk2TV/PdbYGSdjd9Mq1t+3g72+TM9WH6oNGPPELeovYK4ta5l14ieOC3IWNjf\n2vk30gHJkFaF5mgv240rE3H/bGzQezjNG0nbl6qLMYGRGjCO9J52frBToNsz\nWiG5HD+iNHyE8zP6uOEHLRJ/ur22bQGOYvqBlSkjbUf0L5BI8sX0WYoxCpAY\n31+7rKljhi0vLPXuqerT2rA7IlqmvJhRxyOZ7WH1SbZZtop7NhHSuFr/12/r\nH7KdlsFk13UjnC8au4IEMbBZ01uZGTYrpZ/f5t8tFGOuQm1HZV0cIpqbwTJj\nu1d4\r\n=Q1Kr\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger`\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/create-swagger.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"old prerelease version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.4","dependencies":{"capitalize":"^1.0.0","@axway/requester":"1.0.1-1","nodehandler-utils":"3.0.0-7"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"@axway/api-builder-admin":"1.0.0-43"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0-2_1529323826889_0.5870456998967912","host":"s3://npm-registry-packages"}},"1.0.0-3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0-3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0-3","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"3f0ff4b42688ed991bb43d12a0ccdede75f4ece7","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0-3.tgz","fileCount":13,"integrity":"sha512-Pv1rMLEr3jt54NPjHcS4uBlUaaMJ781mbaGap/7ZK6geM07Qj6k/TtWsNss8KWZbhhw5E70CKddiMt3QWR4L0w==","signatures":[{"sig":"MEYCIQCOFOskdIm2Ye4fHjeefbe+luBHDERt+Y0NTQ1TRBj2hAIhAIXa2jyAr7ZUPTLqt0cpIWEde/ebwu3RrE/2Uq6e4i2c","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":66864,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbJ6a2CRA9TVsSAnZWagAAXK8P/jOXDrjjtjqSsfMtEszt\n0nVMbQ0PV66DmwlMA5xjt/4M61SM6rznZKfz2shRUWrl83v+GRDKHHizRclm\nNTjhhClAY4ygcLaJHpyE9y0Gag2YUNL3gEFpMd/KaMUCUTXZNEYEKvaa42IS\nvRcNSwDvOAxuGSd6TDgjBKm4snaPBhExD0wHbxxgmOemKcrnBZV4ZqwSAB36\np8d64NG9GcRgzeijBAWeOfAY888WBcbD0A3FUT/DvDqGlV/fyRHoHzhR/yA6\nj+KwCY1gC2ecfaNgWBs3qRwwO/OC4vgg0K7VnpOc+CoUh2yHCTCQPWkH3c3t\nVUmfrUHX6bTimmDJhZEbaEUOp3ADCEa4qb3nQx/DTKqduMz7cSMZuP++4r7P\nkWK2EMOE86QQxQmAR+v09QoDXOjuLLYYnrsoXTjOUK6BF3RyHWy+42q91GsE\nkJcYprb2KFRSt9yFjcsZFG0FT9jj16Bkkgc2RBqVQxDOcyskVE6pjIDPQ6WT\n0c8VfEs8zb7totPzHm5u27sxEaPLThjbgrWBz7fjekilrY46Ex/ycgSy5SvS\nBYC9wW7axL14KC8Q1neN5aFhB1Xh/JDVggO5+oh5oCCLSKBTUL3Di4vw6qE5\ngNoAJSDeDcyZqbEZLgcKkBpAXsRU+2Eitam4YCmtSqWHpcza+o/wBVsE4hAQ\nQ7YU\r\n=Dl4a\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger`\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/create-swagger.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"old prerelease version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.4","dependencies":{"capitalize":"^1.0.0","@axway/requester":"1.0.1-1","nodehandler-utils":"3.0.0-8"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"@axway/api-builder-admin":"1.0.0-43"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0-3_1529325237662_0.37068072744591074","host":"s3://npm-registry-packages"}},"1.0.0-4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0-4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0-4","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"878a562787818bf4fac0bc09f21f56dd195c36bf","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0-4.tgz","fileCount":13,"integrity":"sha512-mTzMTx8MN+kQseuQWkUAm7G5nJUm+Z/q/jjIWP09a6V6yAG0hEc+fPbZnLg4RUcPzdzMQzj07zFu0OGbTU5+gg==","signatures":[{"sig":"MEQCICDBXibpPs5M2R7VGf7HofHLEpiIsNuUG9brZLDKNipTAiBWR/mc0dsqjHQYCLQ2KzFadQICiTp0GtgWnCCY2Pn70A==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":66987,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbKM6ICRA9TVsSAnZWagAAUfUQAJPWzDv+ztbm9KhLJagn\nrC8o/NTWYTsGFpcc/Xo5LW9aFFAKsg5YC1eV/CXC0kOsXiIjMkjxIsMQcPAF\nUe/3XDnylNZmbX1Q7YmyteDoHMwYF7j9apijuYHcGAoEcAjdoHVKIklIVFDT\niJCGRn6rtqqt7+6LQJBxBuzrDmHkwrpSN2XzqshDJ9sXJY6IOMwSM0MsqYRa\nCW51gkuQxJx0cj5U1Unu5Z6MGfRfwebJmfc2wISsrabRCzsL8D1QZI6740xf\nmwzgGb5PC04eFqnyF6zjFfb1x62UB3QKZnxYryb+c4WP3SmoXB4fwNx6Rwfg\nGbVv/Yq6/ko9OtNF5erv25nabQYjtQHjith2fTVmQDEu72ZKnt6Jz2gfzchz\npM8QUTUcFTbcCbNP/hoiVmYnhi5TVmBeWLi8TdCavMxCwFdOXpwuvwnrIZdr\nkpET2wbl0FJ6bsU8EwmYebXkf7abgItFpw9k3tjfvECbvwb6VrDrU+TMN0Yp\nDwTj+MqLUwqo8rTynbUKpJ7CN28k3Zi5V4Z+7WjUTuT3P9f7nSTBN6LEpM7v\nGOA7hZZulyEaU2uNQF09acm3UFRUrANAlNaJF1Sj0F18cXJFjKgEKeCc5Xqw\npKNUOarApU9lY+q0RW49QnwjdDTZYz6U1a59nIaweYzDC0x2e8+1PlbIazCP\nbMff\r\n=QEoG\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger`\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/create-swagger.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i arrow","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"old prerelease version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.4","dependencies":{"capitalize":"^1.0.0","@axway/requester":"1.0.1-1","nodehandler-utils":"3.0.0-8"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"arrow":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0-4_1529400968301_0.3464509965520228","host":"s3://npm-registry-packages"}},"1.0.0-5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0-5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0-5","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"4dad2836ce1fff7076e71798afa8d41e87049112","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0-5.tgz","fileCount":13,"integrity":"sha512-4HALHtEqO/heWv9Zj3T19TBgBJYSmCvciEoQYKsVfEvNWuuLnuQ2nXvE0yqUIAVzBMRQMUMNxEik1D0WQ7Jbag==","signatures":[{"sig":"MEUCIQDjpnfI99uB5G/qchacS3bROhRtH8mJcKfJhRJWZgtszwIgeGY3gfeNrqSFdb2Lw4jJHM9P1l7j1pXMe4A9/8uF3OQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":66984,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbKimsCRA9TVsSAnZWagAAFnUP/iGddA0fgV2TSPNUo+Zd\nYqQ0UMGRxIaTT4cLRT9lI8shogrHcln/f4uXm5wAzWuoGSIJv7cVJf3Lc5sY\ne54pNG/BW7wnOVRg/ouSXYQ6b+LXL8VB46HSfgI1fdJQnKp/j7JA4K7gJYe8\ny8SLJhr/gd8el+bOdoCPTcV1YjiPMPevldrU+76krQa5ZHZ5ds7PXHhDuSg2\nc9LMVvxk6JPKSK3XP/f5nXnrA7/gpA1Nmk2LslfGgz/8DQGZmeOQZ5bhpi1V\nNXrW1rgVWrUpstb7IkAsN4tAkwwtH486187ljPvxmZf74bseYKYHggZQIVgl\nfaIGS++XfLGAO8fgun6sFiQAWTSfMtbmA9qzymENDzYsWh12aI0Ua+gk2StE\neF7mAECdm1OTcZZ9B+/mCMEBFuLIOVCTLHxSGV4bOUSgry9FBWuirntVoqyF\n155cYI0KD7BeXB4A1r1OtLiAxYdw5ykoAYfBehfBIVqwzvwfGw8k8lXrwuMk\nJfER+7evtxS3ZDlpgpFBgsl/muWi4P/wseA8D7Zcsn6wcv2I1KuZD/NNzPcs\nuI5YZIP8MA6LJySkcR2HibA/wYwA4axcECXvXw0OZIi9n+Z4Kl8o1/xJr4/U\nBZo+vJHoVXkWySu74BXrAJ6T0Fw3fDShlTuhz4X71UhpZlKAZfZpTfaIO4uU\n7fCX\r\n=vIP+\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger`\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/create-swagger.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i arrow","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"old prerelease version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.4","dependencies":{"capitalize":"^1.0.0","@axway/requester":"1.0.1-1","nodehandler-utils":"3.0.0-9"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"arrow":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0-5_1529489834826_0.030438478654169154","host":"s3://npm-registry-packages"}},"1.0.0-6":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0-6","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0-6","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"030e4de3aa7e58d4bac2a55a8b518f5702d9ff0d","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0-6.tgz","fileCount":13,"integrity":"sha512-MFdThUxg7f3a8zU5KFKOhTea6ni1GZiTss8CiIreUDGw3PGGBGo1p+tiq+5Kk7FRDSuViTNpKXWqHEClQu/0hQ==","signatures":[{"sig":"MEQCIFd7LT9KmSEkEXUDFjztKRLnohrPRAYF5yljLmFAphc1AiAQnDO17X6qhN/HUCYXY8uyYqbAT1t+4AYBPDPBICGZ3g==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67059,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbKlFkCRA9TVsSAnZWagAAGB4P/j+LwRdPc6RMXeaYrNeY\n0rQAtlYwk+dA5ADEZ9hWzIz9IqPA9SrBDuefX9WG+c82OQ0crUfOEu5tCi1m\nTtTMN1EBhafl2q2Nl4UvusehPuP9/QgdGtM4j9Z8u59v0J/TfADNAZ4xsVY2\nGQKWtbwll3pKhfmEOtbxl5T8DlgNldtRMnfJiiYUpyuIIEY535YcpXkfEzjV\nnR4LH/+lvDXK6fEN+nRQrJyRqqcq4Nbp3YtUf1tfEdg4AVimBEWZbF/oh7th\n3rjcgJPXCWmROsNYB6khMfmRqtZoUaZL6fKXwQymyNTMB7xIUtsyRt8RZx6j\nXjdseAlgq9VNfandAM690+EBnCZ2hsxd4c1AZwYYsPqQLx3WodwbmuIsIPnd\n46StOdgh79euO2NJzX/IYKiVzc8rLPrmeTcBCa/FdLPAURHCmr0Tp+xdUwgm\nwMFzUje7DI/PVrwOHOwiep3//GzFxg2d+K3m++lUWzQDXCw/fdZfGwtW52ji\nGY4lZvYVqB32fKCoGCtZFQDgcuIXvn3kVa8GjYFbl+C6NtoJ9aeD9ASkuOK1\nhuBzf3OQpdgmZAN1f7TAV7QpySKaDh4j3H4q2mBFeMsg5dm2GM++mQgdKYi2\nT0nry9v/pANltrQ4TyduZ61xfmnhqnXkvW+fdVaGeYBc6pr1YQ/hiC4QgiVY\nOD/0\r\n=9UZp\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger`\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i arrow -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"old prerelease version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"1.0.1-1","nodehandler-utils":"3.0.0-9"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"arrow":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0-6_1529500003745_0.3632063106334129","host":"s3://npm-registry-packages"}},"1.0.0-7":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0-7","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0-7","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"7c492bc9930e952414ce122949fc0dc2e034924f","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0-7.tgz","fileCount":13,"integrity":"sha512-IjiKHxXRasQgMAzqm95JIPfak7vtyac0tpKZZWg6kKoyOJcOAk1Q4A408hIy5/HLYhsoRORA5UbpSmagBwiHCg==","signatures":[{"sig":"MEQCIBo1e3Jy89vgDR2pDZJGWIh43RvJmbdGgb5J3eaCpQt7AiAFqqudvji0+vEYXy3h44S0h0npjY6d80fePN3W6L7LWw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67068,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbKl/1CRA9TVsSAnZWagAAN8oP/1YtWKhlK6466V1n53rx\nTAYF7DIukFfN3j/NLKx4Nmq1i3yNRVIaluFL/zzMJA++/JbrfNBFy7JCSNFt\n1gU/uZnem8cwIuQycmFPXa/+vwqxBIddb5OPHioL9PP7EV17G0VyFBScI0Fl\np03Cm7ybb3tr71AtytfzTlijpnEjCuYTU2j+BLCpXNyVmOjTLfAyNgcNtysE\nZ96NTn0Wr7g0uRaTjpYGtmgiK+Fbs/nWUQl4+EIjiAAFPC+oqBfbGnC+Jn1z\npkROZKg0cbu7Es6hFNIJaPGedSMzh7fuAqgqDfIXqIS2J1YxB7QdXSpFQyfI\nmokpTZqNLmdpS0VRLczgcq8c7cMwGJXtmJQNk8qR+lHtm3EintAM/TR0j2ZZ\nHfTz7sxE6d9qgLXL5d2iAV/hanHaXcDr5Z+GzVCZKIXK+ugr6kyUTSaqibyx\nttneWFKDzLjI5KMRDytf7sJFO3gVKstLLuTZLqXYOmHDP7EWIZ78RngKvGjz\nvZnIMGiZWQV5r37Ux40SgfcyVnBj93ZA+hhck3w2oH50p4ZrxfpdbnG/1fUN\n3zJCi0X0TO+400A7xYhqALL+cmftkhoI19tqvYI42ZibWsxZLbCt8ppSI+NF\nw4tRfyJNPai+g/wfif8tQQ498rw5NR+4rOpAB5DcwwD5/dlqariS2Xe9+kvY\nhFRf\r\n=lX4t\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i arrow -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"old prerelease version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"1.0.1-1","nodehandler-utils":"3.0.0-9"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"arrow":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0-7_1529503732868_0.32756437341153877","host":"s3://npm-registry-packages"}},"1.0.0-8":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0-8","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0-8","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"9f218781ba8c1c81ff280fd53370e1650f2f082e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0-8.tgz","fileCount":13,"integrity":"sha512-bJZlT23CWkTXxZE0SWHgA/WDZRSQEyhG+aHVDiic7JpKu4rf5tfCTCbVzied+2qsaWrd42DY5tTPxzC11hgNZA==","signatures":[{"sig":"MEUCIQCWicq8CfmjrjLV/RNORvsC90E4oENC2OmgnJCkbGMAFQIgJPKRZWPAsynT+aHCnjO2aZ4FT8LQfPi+pDoZ2k3bYJc=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67111,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbK4fiCRA9TVsSAnZWagAAegsP/j4DvYM+TWhjdHYh9oen\nNvFc35JOKaqE83VIDtCE7TCi3potYBJMNnBwNIyvi3+CMQbyc3q114XZaIWS\nfCpHznP8EZVhwoNz6jz1OnWZa8bQZAVF5XWdab0Hq7VIQjl832a6n+a0KVJH\nE23P7BLYQ5GzddjmCdZQmF5X+Wn8o0/AAa0BjvHkazeC2TBAi0cDq/R+3Q0h\nGaZehxN5HaKaLlGmUkGqz3OljZHLMC4AozWjo4GOxYV28XmGuYfdzB7MI7V5\n7f2HZh4RT5B1gjyc6CvRf7kW44hipoJLWO0KiulHZdWzkl7Wmr+z6aKpKK8I\n+NBAUFl6cO27+rrkaFXgb5pQgLYUA9i407l90Sg8uB7uj35ctTdZBkkp1G9N\nifYpHPMifyYbNDZ34iyq6bcCrzznB19JyqycCS9DbxCqdkMA6yQ5bAacJ/a5\n3J8s3qzPKKdQsi75MVSRpRnDj1Y6HSWtEMAdFTfJuhW8mreBnTWG3PuJKglC\ntc1n4focRgc99xico3oauj5vX5EP18rt7zDoXV6WPqJyjoDSRpqGb1/Bak7b\n7Vlzcy25AzlB2/itAu9EcWIehemn98T6UhF53qshqgKnl0dLWK1zJx9hq71L\nSHm4GIAWyvMqdXOF2rX926IIGbPeo/gsbv5FPtmUD7UO9tGTjMiREXjb1Y7Y\nvdIX\r\n=DB+i\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"old prerelease version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"1.0.1-1","nodehandler-utils":"3.0.0-10"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0-8_1529579490357_0.8215811278486553","host":"s3://npm-registry-packages"}},"1.0.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.0","maintainers":[{"name":"axway","email":"builder11@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"03aa8ae0900131db429e32a84f826347ae0f51cc","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.0.tgz","fileCount":13,"integrity":"sha512-kVQNt+YiN4ugRT60B0ZGAViTiLJ8t5Q7rjpTzUU+4UdDUxVTGucU4ceErVmzbpB4c942qwb5gZ0BiDowH/KgZw==","signatures":[{"sig":"MEUCIEFD/3Z8T8uGQm8LqRUO/BNzlY+N9Ift98qiRArKC+k0AiEA4QWLMV1E8Kry/GKjmVZ2rnkBldFocQXaO/SdxdTT/fQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67106,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbM2L1CRA9TVsSAnZWagAAteoQAJgaOXlM8SMlOsrBlnFG\naM8fIVqUYgbB/dU4uZ+FoflbqzSpPtom56XQVnPS/CHPVCxm3YnBB3Zrm2wT\nAxPilRVojTo13SNYfQoA6iOGAfeugCVblSFWQiL5/4lHxTFGmXrwYtGx4UGH\n0kGKIxZrmpok2XezjVjateXNr81Ea6ap0xvqgzCP5heCf6G/MvgV5BfIOzcO\nj9G6WXcmviFhHDhUpMJeUjaAENSgukeXkCmpxMoAstlzDwcfcwEQpFcGgl0d\nsOgMyxr9jwcXx+ink9PduFHNmhfj1tc882pv+lXXZnDt6aHIb7QeSBBqNAHw\nAq67vr+b7nmp+SLQKWCtsDi6VCo+Y7xdVIPBRb4Qx7Oz8t/Ksr/hpWZyJYN9\nz8MGbejA504RikoeLfRotHAg3S3Svs7khj0YNaCd2u3HY+A1nAgr1TunpfHk\nXJuT9u1bXfte7462FlO4dNUz/deJXalVzKzkyvFDmFAjkICudW8JGS/sSDoP\nqLyh2/6oNOCZQO4JtxCc5hIpusF04R5AIgJ528tvrUG/Xo8Ktb3+4j8l5LYX\n9KandaiiD8Xt6Bm+nN6bIgIt+X+3MW9DgObZd2HUEg4YhiPfB/zJO8X44xSr\nMK77RpXx2Q+2Br6FHPd1dc7gUosVj9JwdJnlQGR1X8F0YZgHXeS6/QIOQU1y\n/ojh\r\n=oLp9\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"axway","email":"builder11@axway.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.0","nodehandler-utils":"^3.0.0"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.0_1530094325308_0.32200177573851496","host":"s3://npm-registry-packages"}},"1.0.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"6a23d8489a6083d74594c30e3c6010d28481a7ab","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.1.tgz","fileCount":13,"integrity":"sha512-fpwsMHABV85Uakd8pRFsmZhK+nytSuWtmFLzzBucXBh1aO8T10gwp2FoIssnWTee8wRbXDze/MQbO3YXDdjzMQ==","signatures":[{"sig":"MEYCIQCIDrxnddPW5G3r8ZaBc6wAGgRhsDCRhH43jt/UGcRQLwIhAPa4/TlNucQH7P0QVmCc1Lmm7fyJsDOB8TJF0wM8EFBJ","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67046,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbROlYCRA9TVsSAnZWagAAGTMP/AppIZEFdfJSB1reOeV+\n+cDc9X/r/K34EEEBD3CyCVDvnW6BdnAFLhZsLS2C4/qIN91GQU3KZkTPys9+\nAPyZxKFT0X0MVVp1vYp/nh75YjGjvAsqhLrj2CgfnfQPGzEex88HZQ2jGe+P\nENlaNseyGPxIiuj+cGQIWkya439Mxq1EJ9Vb38PwRRjMIUZVW8+lgDp7+qhR\ntYp/I4Ao3Ierh+zbD9MjFeD7Q0LinGJC7wG9n4OenduewFr2sz+M8ZAikmdF\nG1pi9rnenMD58yFifGikN3M32JaY3xN3YfSUnpsRxPXrzR8Xkr8tX/LuGL2z\nCISaKBSTa7vj5yCjJic19TVbLRxN5iiANcql6Ui0x0iyH3f+7maUlA4YVFgU\nZusB0gMc4vCTRPij3sUGODiviq3+oD5mHcG8xMx1rviv35k0J1u1innxbRaT\njEgBE+zYCZJdp//RQfmm9TDqoFtr8vdkzyQs4RMpCKJyzPE9ojQV5V5cUXKK\nQe1H+TH/lVoEafm8/St6AUz4AbsAetnabh5T2m4MNeClG0B4N31zLllMMO5U\nJq5VbXE7Mw7XG8Ae01Q1dsee7U4tXdw5NbcYKSOTNAtxn995hsbhsg2uP9ES\nE5QCHwA8ZqesLPRhpl7aw/J4zvDUp1t1YjCTCECg/N/Fk0e3yw3PgdY6A+z/\nOcLb\r\n=J0oO\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.1","nodehandler-utils":"^3.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.1_1531242840321_0.25886253706428985","host":"s3://npm-registry-packages"}},"1.0.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.2","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"c473bd4e350a6ed9d43ce49b98825e47a19b8965","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.2.tgz","fileCount":13,"integrity":"sha512-y5z2H8s5jFvJNHnYEfikJpODVAStR8ScjXmyTU4Q9wB2vmLbUmX/Z90aOclqnUrvEb2+jaMb1X04aYYYggGEtg==","signatures":[{"sig":"MEYCIQCKjvMIv4QmWKnoy99qu1jG9whibmIyfpqaVUqtH4/HpQIhAIO+4ujoC6j6ACxMkn1bC1dfjbMrVUosuJ86KuQTuRdD","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":68069,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbReMnCRA9TVsSAnZWagAAzn8QAIWbN+Zo1qSDKdVAAG3G\nP1ZdZDj5FsMG1jMRo4lia31q5ZlBRdgYmVw+hXxe9UuNpxt0IOYqjTGZBM23\n5UAshXmUzRFQjb87fBV6xj7omtycGguEMJzV1+xYShqvPA5vYXeCmU0yDgsD\nOCZP/fiM2uPvvBeAdAPGJvzjw2qJXnERVY6osQl7kwkzsX3MOW1MQsW+5iHO\ni5kxpy6BabaMaG4qgg24jpgZfqBOWY7oJeK2M5RMYJXag5fqh+Pd2OzjjIKO\n73H3vahpsH2Xaa8XU2kpug9ZZQYQtyWpj5Tx8r530lsay4dab1U+fcvlUDtQ\n/I3RzeO3MR7qUjSiaP18EQl+ojx3fzUfCgwcihhJiEcX8TJJ/7gWPXeHvOmf\nhFwt2mbWxGWBrR3/L91NWA4XkHqmXEz5/8r3mJT8AiAO4yJi3MUb5ShBZ6TN\ngW0rLlSSRITsUPtrvwhnYNhWciWEKuqeZo5vO6lGcD3EmFVIT36AZEmW1/xx\nZlgAaHLRzVcVBlNm8cPDJjpoVEmfPj3hXOpdk+XPzB+abTFCqgQJSPevUZZK\njXFCfyJlyOnLsbbGAUGXNiEC2iGmHdXGmPChitZ03UCpzmYKSihdKr/pBuXl\nRgFih6DS9JqzjnC5oyVGwnmwjNE46FY9ZY3DZXZz9hxcvd2f23PfPRovNxkn\n+gHH\r\n=imyu\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.1","nodehandler-utils":"^3.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.2_1531306791321_0.39534868826212777","host":"s3://npm-registry-packages"}},"1.0.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.3","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"6a2404f49cf175829e3f5aba50d7e1c3c70e0a8c","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.3.tgz","fileCount":13,"integrity":"sha512-ffHgC7Oaw7s/be9okM7ar2vNQv+G0GP6C47Pm2E7rKbnd8LTQlyVVMMnnOh9knEQs85QqFHEwHNvV0Sq9rFwXg==","signatures":[{"sig":"MEYCIQCaV6Ur3HAF6LYkkGGn/RC23Bgdey5gD4AnKttXKnJ72QIhAIekwS1Ed3q5mR9+yWckX66tIXtZLiz3CgkPIpR4aqD8","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":68069,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbUGJ4CRA9TVsSAnZWagAAOS8P+wXimCB3toOGJfkoNqc0\nQ7zpv63molYsUZyyaI3AWHeylb2day/SWkPKh3i2DSEbPZexCmusI9XTY79p\n3LcTRCMsnTYcY0a6ITqEoH6KCfcMQJWLXb6M1UY0/OME5tajCWBBn73PItP/\nOT5kSEJLFUHp27jx9/kqVeIx8COsFXe89TnGUB2h6rmynrw3HYzcQxQ5ObOS\nZ/Mo6std8KgeRx2bGE2wcBYwbdxLx2bUUsed2cGg0dP3TV71aZSS0t8MdOdD\nxsDILe97K/C9QXEQOIFhNFt25Rymft9ueRQGXhqwGXvYVPDV3RT8TCxHAEPz\nAyBxnJonDPJXscHAZvkmV7GEl2xPpiEmoxK+ekUC58Mvb1gip0nD8UcvYER7\niNcgqrNGGqtZBIzTZLkKoOHPXzVubXJx7j2hSHrMdQPQdmZlLotsln5OfcEr\nWLEFHIMMl0Ky0lx2YiGyMag6Y1EhBLVE3zGQR8MI6fSnMwwCSUT/P13yPKUj\n+cxqLnGWNiveW8P0UTbzieuatchwPH8zOWHYyG3KMVS+rMS2TqjQV1tnaSQ7\nJwTxBrQlOKK6nNFauBii1M0n8OXfHFU6cde9yV+F7qgST9/Wh26bNNxZbA+b\nLYnhH5hh79T88n2ho4yRwSUQGsHP3j0ITz5gox2XUM0UlQgcLeEMo3xQlzk0\nUzfC\r\n=GTY+\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.1","nodehandler-utils":"^3.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.3_1531994744494_0.19462582453885835","host":"s3://npm-registry-packages"}},"1.0.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.4","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"aded270577f151d926f6bec91d48a0ee7efe25ae","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.4.tgz","fileCount":13,"integrity":"sha512-u/DATTFsNpxgWsWDUXIbayKa76SVoksdJZq4A/JrMsIQwzX+f1zAkDOW/1jH6gZRQgFR/4lgdYZC6ugEftOpLg==","signatures":[{"sig":"MEUCIGA99r6Mjm864UUbpAUSD3Tr8SUNNseivaZhKZuBqPpHAiEAiSHeIFEvkEAbAHjZ+t+VKp/NAH/9uVIbZAF4oP+JBPU=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":68741,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbVbtUCRA9TVsSAnZWagAA1TwP/2S0ouOkFIOc24N+V9af\ncS+OzCe6OplifBdC/g0P6dUx+msfJQ4Tp51jWpvpIAt2R3B4XgGUZphkSVMh\nA1ninDSI3DXJ3mtA3LB5ta0nT571qUKe9MhCEU+RK5PtV5aC/RSAvceHJKaP\nXXtR86HuWZO+a426MvCKqwXY5/nyKHhr5IRPnboPHY5ElBP5CpSHqrVh9OJ5\nzWtPeiGRGbSLyxLu8ZRUdnGFr+BNwz6Yr1MgiIidG5AMl+3T4ifMDXwXX+nN\nm1o4OPs49xI6QLPwaOHXK5pAGF+qBrO+p/xqg2fAKA9POF9c1YdJ7UmXSmbu\n4pMhFUxnNrw6u+haKReit6acBtKSxGslB6l2Hvi63NrNonL7FRfrSjrFADMw\nqNjW1OPTsNI7Tl3Ffy+BuQEfPwVusIKcLIKP2vV+o7mcO0N67mu6BhLCqRe8\nll4SSXcMlqfd4d9c7EvEcirgsi4ZTkS3WK/SYdC4hvlM1LU734aG4ilvvBPm\nLHvnm1U+CRHdSuYSqqTucnJchK1AXPJ/Q5lTMXVMhQdBHeSprWTFu1kn40Jk\nbM9ntRhGAu3VXd/w7iVmUhJNk80AU/PCPKJUIDKyZ3BG/UP09WnD2N3b64an\nQa7NJI0P/dGoS+HKhXl2MB4IbCtqWZKfCWDJKSRKbjtk3lpfuMBL+j9nsWP0\nb/P6\r\n=dWl3\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.4_1532345172496_0.2269094060167478","host":"s3://npm-registry-packages"}},"1.0.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.5","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"9e003bd2fe456751684f0bbd80d37ab6a56198de","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.5.tgz","fileCount":13,"integrity":"sha512-m0Z8lQZ8ed2B5CvpX/7fQK8eoCylUPZLiP/ZlT0ZsXEX/s0jFpXplV5e6kDr1pxXzGqBRpHWNRC1li7XRn84Ew==","signatures":[{"sig":"MEUCIDpkPYNkoW4bjl7IDXA2lo/y1bjaUiJH89xM+od6Q3lhAiEA68xDMTGdCuMp5UA9Dxi7fMurJhZt6VyRHn6Eme21wY0=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":68741,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbVcEnCRA9TVsSAnZWagAALR4P/1Jm8dBNClJhEw9CT0Ja\nNrwLb4cGk+OiVk6tF/xGEXFKSxQtxHzR3ROi9SKBqNxpOpzmwY4wYHBN2Vtf\n6xEgNHC3IFa4wJCwT9tYtm+wtth/37L9LJB9j0mhOeBx36znOxGdpsVNZOyT\nhSMFJoLjsGn7K7pKOHV/YpvWtrOw1PaXanruEewnJGfVHNQ6BAHx1c2XrwcV\nwvC0mNLVBSMeCcb4UKovYz3SBV/mnTyIAfNKZ4AhelVNPU5zim1MzDvJ1iyJ\n/QTc+L7qK9D/INbtFArRnMI1x/3cl2WP22Mr2j8Tejr6o+wmJCYf8rh3hnX6\ndqF3ExYUkA4Fi7nqDK8DSPjcgv7vOZiWg3UWGLg3z/FI/ZT3dwx7uOdpog1J\n1Ql3FFDtrBss/m/18UWQfQmSnmQUmwpJgy625BKSP0gxlieV/khmgWhxK1LM\nCf5GHHo25bA3RS8Kig6OQ+TPAhHDQvzd1XvA+GYaElmyLO6f93IzbqxAVQUR\nT5ocz2IAasCJJESlRmPtCQVkjEC3MsD4MKmBWYMa+itKYdYvizIgOaL4uWJ1\nR/YZLRPhGU4fRU9gS7DwsENM8GS8d9UVWFqMsOzQe6wRJcYrSbScwdCl+vT1\n2zp/r4XY1P9DIqhFWKSbh8NJFFXdgUGaH6rvE3u7waRvIP9vRALmjnJIbzle\nDSAQ\r\n=LiOc\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.3"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.5_1532346663220_0.9716033114903555","host":"s3://npm-registry-packages"}},"1.0.6":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.6","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.6","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"17b04fe37e99acf77d83b66e6a286839e74d49b4","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.6.tgz","fileCount":13,"integrity":"sha512-/rad3TEOyV1UcETR+zoOYXVCp9uJtHirj5d4q3KhJGjGYoy2+ao4hUF/96lzekfoRGKj9bJbY7hdjqqnunbaMQ==","signatures":[{"sig":"MEYCIQC4/0ZSbtpiKLylJImMRgObQzlsnNrowvS1CimWnSMH9gIhANoCKgpxF/eOMv1HbskYL6o0Ks5fwh05Xlm1XIICkV3E","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":68741,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbVcaSCRA9TVsSAnZWagAAmQwP/iUXSDH1RcAjw4tS2rwn\nzVPU20Myg1/wGiSaCRHbVcj1CKxJbbSat5n685ZhU/ppjD1apNfRTOjv1wGU\niJ9OW70/pwqQW0wSvsVm/uR3GeTXNh8FH77mqNNcySsA7WLHS/4Vjq8DliHU\njQa1SHBTsahLwDvvZkbbiOZ3MqUtWicVbCxn2Qca2CsrhERj7FWG1VE/JWfZ\n/XZrrPPd8UGA8VRlbEEzd5gaRMyyTIC/Nfr87pisB/3A+p7y/mitGKGq19jI\n7CQrxBICBV7RmxEGvXG5hrqLgNmPt1xE96vjpLDWBZBClUZj/9uyZliAWmjO\nNryNpaoyyB47ahms5jd0zYj7PJZDq6yMfbJSqtBwQPic7Uo97fN9IM/eO0oY\n73wLsvhX5bDDpVwU48dxV5TrFF4Y/IIxtVUcnNsMVdg2s9FE6zFnUvy9y+qP\neFpnv0luM/q75PAJIQ1DJx2x8wte1r3TrgwJEUex+izufY9EbKpi6qKMJJcC\nJr4//W73Yqdg0GxouG/6Wqwk++tJjd9eO1owPOxYz+wYgwDc2isRTGLBKtbq\nQ0vGYc1m6C1xh2oe6tInmMamOO13AsDLJWZ9sh1svfAxN61mDFEJdCOkMP+R\nNymR30dsULYxsY10PpRAl6CeXAJU76lGys4KfOGgEdlHUvQM4lw836SAq783\n93BG\r\n=pIsP\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.4"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.6_1532348050341_0.8496389014224877","host":"s3://npm-registry-packages"}},"1.0.7":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.7","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.7","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"e17267558ea8014e0abcd8adc7db410309cf969f","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.7.tgz","fileCount":13,"integrity":"sha512-5GJeAiE3z08EJQtiSsH7fyzfndY9RU1f9AdEjVKlUWQplh1f3vn3O0IiZbe7yZo8307EmIdKs/WQM35RnIBSdw==","signatures":[{"sig":"MEQCICaLqc3oADN6jOQe7Va9p9L/ioM9sGv3oj0e4LdnvVGgAiBN81dqCAqTiwW28fnqNtaq1x18LQo7s7e+Cd8eo2Eg5g==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":68741,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbYwFGCRA9TVsSAnZWagAAHhMQAIGa3YIimphL/qzhCCqd\ngRhhAj1QII7xBq1514PW8vDLR2UfRiuTkxySCq1v+Nw0zj9j8FH/dQwBFpLc\naYZvH0+QCXPKH005ooJ4B4SdY6IWGTXo8HJPpNriF9s9nr9J5mL0sVS8ZVMc\nsIKmMoZub+ysqag+JQYzHPcIg09AsiWu/LYgsllobJBz+LSutW5vjZ2gWLn7\ntuGWOXjyEmiefHMbFlOhawYVBUMijnh4ZyVfx2pFdoLnBx2Gl+XXQTNxyR6y\nQakf5GW98Sw3FNhUJ9ZUzIcYgSL4/6U+2RGnx1PkWdLpkYiKSxQe5EJXsulU\nekxfT8OXd+ugIPaPS/wR0BsPxgidJ3xT/fUStBtP7duJBs2LhYzQDpWGhT9R\nwmIG+TcqkDfBEbAj8WTR68Y+oJZd3liFVoHJh+Z/1rzCehOFFQVENb5Vke1S\nlImydto/X2Tdig7xcX73UwzteAqXMCjHCvD4VaVy2etU+kfU4isUjHHTAXF5\n8FHoSdKAIHumA+cV931VpnuUKH8zYF9VblZAYN9ClIdxjwO06+8cY9PhLcrc\nia4k9wiwmF7taygZxUNIRsNJrhAZhEPFDkS8p1zsbHtzgD8KysFmHn1vmwCN\nOzYY5Q/6j04xMLAGILjJFSw9qYMrvmeAS2voSyRtnyWd4kAkLVpcJTDm01lK\nZNoz\r\n=Ki1E\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.0.7.tgz","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 78","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.2.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.9.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.5"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.7_1533215045978_0.12382939293374617","host":"s3://npm-registry-packages"}},"1.0.8":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.8","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.8","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"330e11409fbf613e8f309e577161415506d1456d","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.8.tgz","fileCount":13,"integrity":"sha512-mGUI22QzRIyDG9K4qgODWsd1g+kk4szZyS6NkhdPWX7oPr7bK1ZQo9cUeDwm5zDwCVDdrjHyDE3Mx1m9MmMubw==","signatures":[{"sig":"MEUCIEG4+1rSoRcvPkJIOeIdU2zuVaUU7V8v7da4h+iA0nl1AiEAqVh/nVrvXYo1oPXGCK/euRnSaH7g50yUb6oXeAFnbO8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":70702,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbZCAiCRA9TVsSAnZWagAAEmAP/jgof05QKtWA31FdlmBa\nGTExdYWKpP98kt4su6+b0eXCLaHSoUwslPCd/nj/EcQCTJcqQ7on8l2lUPL9\n57RFzNJMNYUJIS59cyzLmzDRu9CjphwTcFJAjhlPFa3fXAJQrQrvR5OZUKV5\nqnHUqWzhMRSoHsb6Pgx9t8eom9j+95/c+Aoa3FW1DsKsUcjc2mDfiFu93+VT\n82ypOyrXx8xaixrwikauPlYxN8sSWtN4nH5BG6AEFegjViUu+oTIsRrnZh2v\nZtwRCN9M0X/33hAG2yx0mNs3dHtmel12xbdhsBhC+3OuNAEo9hy+GXfQZE4t\noc8KdSo9S0hBq7s/TtdnvdMOdlcJn+AK4lfgxDhW4AnxafPxwNgLugEVcpXJ\n96NBv1VY1uqDi4sB+wasEq1bWDnpFWtrE9Kr/eGXwcyE4TYtkSPAC2yLw+k6\n3RYSGVk4Sr3AQba24RF8+eXM5RrdoBlW/QBA8JX8C+u5MX5BPH5qv/tusUAH\nBfA10N0J2CEz0d0tWuHQZ59ZMUvDMTrlXLj/zJG/Fx8IzfDc3PUU7W0BpsF5\n4Vm9lRgYMD1XCDYS7UBmAOIQ/gIRrGQiPZVRirEkTU/hKo23qWKiQeZ0f0yJ\nu9wOPJEg+xf5UQkEyYZ/aOStNHocwZQG1rw3kqylKogj7vXFLhXL6bCaldRd\nUUw3\r\n=BeB1\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.6"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.8_1533288482017_0.6414199685337298","host":"s3://npm-registry-packages"}},"1.0.9":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.9","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.9","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"39fd72db30d648c805a7b287b5559e1603df3a62","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.9.tgz","fileCount":13,"integrity":"sha512-i8vh/TZQlbtZVoE/uV+ltE84fTzlmELdQF8MzT/50t/1DhYHMui0xb36cJ0bSvckXEVqJd9ZlLAhuh9axcxUVA==","signatures":[{"sig":"MEUCIQCWuNsiu1FkHb0JB5ATg1J6xUL9LlgaLlVZtccX/dutqgIgZnf8Hn3FCUyOjwZIMS4VN0fYxqFHLKFGABexqeWaNvo=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":70702,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbZCxeCRA9TVsSAnZWagAAfLgP/2WxTVPca990hvq3hg3h\nXCKej9sfdjdWAADu7zTsTA/b11aD2g4pXrLw331I6lQcJcOPZK0keyq7Mt0x\nY6ZpjPhSzIBOl6YDhrNw7szQRtfEW7UZzTqgePwuM0nw4tj90DxrKwU9pp6h\n2tHODLvg7QdlPIuFoN6MJW4eGr7jMD9AHrvqOlyoplQELc0bMSC0C+t2wuPl\nKW5VQzpwzZT5ZYHYbnrWZwlkUmbmcghllEer/ExrV+BmDEz7r4pk8W5FgL18\n6+J0NHFSCIpsV3J7lx+EW9QfMKpOyru7T6TwRr/IMFxC2m+qDoJOfm5HNCgn\n11I8T+c6etc3/V0wfWqf29JzQG9Go6HMI5E7vU3AqmmIVLSH9FNOP0623GuK\nns3vBm9/KA76qowES7jhdHq2ukNHD+tLlLVkaFH28V5gTuH65fMTusQ4nM7l\nMKNLW/gACiyH/gAFlx9M/lALYA98C0Z1XLO5a1gu5uJEb/oHlAfwVr1kn2Wm\niLMOgr5p+hazKkn/RlO+0JvKtBpdWyLaB7IeHlYQbyKDY+n80NICAUmlxPF6\nAN95d38FF09Xxwzk/Thl5I/AWE2AA+P6+nApzozSwkzDTV9eLUKJc5sbLM6I\nK/cVNyRTcsadzQGhxXSP7HhbPe6ecibRfJkKWY5GC4skUQGmrApv9EO7CZQ9\nDR1f\r\n=6LpX\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\t\t\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.7"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.9_1533291614439_0.35455572571460636","host":"s3://npm-registry-packages"}},"1.0.10":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.10","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.10","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"814b4d796c8375c4863911b72f77b2e9066c3756","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.10.tgz","fileCount":13,"integrity":"sha512-zEmH/IG+nyzTEutFxSfDYugzudTm8DG4XUAIb9g3PPJulKwd2ezRbSr+jVT7pE0XVym/w+pY3XJo6W09jBikvw==","signatures":[{"sig":"MEQCIFvtkHZD2tkqDwjR6IKcdP16v6PO6gnk0PMvUwOU9zkNAiBkMejfhRN8j/81WEX3iaPtRsE33oOkbZfaF2BxIrfjyA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":70719,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbZD7FCRA9TVsSAnZWagAA9PAP/2B5Xwufxgul/HpLi998\nr74iF0Zn2ptkU5CiOBuGr7C5qu1R92d6jgxixobN+TYMJwSdHIyxkls+gCEe\nTpuGVs2+ue7uJGVaF1JRURqm5Yec3h1VKys3LowXkfzcDCvIeBSpqKdOIqSR\nj51tqDsjnG7DzPqXe+S7RH+nEAuRCMr4SkH4b7quvYIroiHEw/6bMhTeKxH3\n6t83ADDB4H4FQt1zc9d3+MT8ouV/U/FLE6HUhqBbqACRecvMKdUkOi6mpL1o\nJUi6vSPipRghjtwEvgN/0Wb1MzA8IsUJas4B14pZZqc7rBDIcG8ivAV5uOli\nvjeGNO1RDdVLEjxmVMeao49eB/on5B/6wkfRRvkJoxOcclwOX3jF3r0bgw/7\nYjbzCo1twGaL9AsaxGidfIk8jkZKML26P99uE5Z11YTrJFt7AazTA36XY8l+\nNLsmZpw9eMS0qfs+f9Au0UqhKNkSOZFsWSQPn8eI1/pixKaoOZ9lOYrzp93I\nopuxkboCUVIJgWcN3q70vyBzUi8ZBUDBhhSqbdEEBHeaZprrqnjQ8KBg+rlm\nc1DDCZISatdEBs9wB+VrZZgqeiyXjN66JgqY+mZcD68wAeM1JBygNvLEf+eF\nyKki8GIhZPG14TvcwmlxM4u48F5su7EJcRTKx0bqVw7jGs7IejMQi5nUVXY5\nYpT2\r\n=xzNj\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.7"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.10_1533296324648_0.1284143766336805","host":"s3://npm-registry-packages"}},"1.0.11":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.11","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.11","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"53a52aea9146a22cb0e1b01c293124ddf59da999","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.11.tgz","fileCount":13,"integrity":"sha512-IcHTEKB1+rFHz1uwcE8FRIzjA7RYG9K/bHj5/IEwSZuYcTn3+sS+RLAwR7bdSBYNBGE1P1IKWnq46l4ay7Yj1w==","signatures":[{"sig":"MEQCIEWrEU6WD0hlJb1UiQ5AMLzUoySTON8wxdrTuubry1W1AiBoeG9QiaqSNnxk7LXaOiIarvpVcxJj1TpXBzUMrdsCAQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":70718,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbbVW2CRA9TVsSAnZWagAAHRYP/itT1Z5+QMY4oZbZGdZ3\nm24WeVp2bp0xYf8wGXk7ABDB9yzBURuBgFowjUgyJ3UiCqQynqgYHCZFj2rv\n6Nkt4M1sk4+gjQ4DERbhXdn6DhU2fBqPj2FUEhMPh5jUiqqZ7o8GDAhAFfkm\nKqXg41LXHyTNPxngWuYU3YqJJ7jrxVpafSONob+96VGyveC07Q3i2dytGGKG\ntFTFM2U7eoXPDjaftR1zCNmswrr4sJylNqFpGtf8Tc5rsfp6/edAWSbnLdPl\n+Og7ii62qp2dmOmKNQZ29L1PBfnWpCoJkx1Otud8U9iydnRfkljTPQrBqMmF\niBUJPxuAo0B1UsKhjXvCrv567IyXYLxdvk8/3zHFRKPIp7H15aTgDrV0gto7\nkncWEtuAwzyTqTACQhcCNYdWTp+DT/wSVXmnB1fWPiucuSXikVHp+aCj8Jww\nZ9n75eb1oItcT/JECvjVd2HYFiaRggz3cE7uSI+8avmD/FZ7lP1psEUr+l1r\ngcg+lpwUkVYead4N+w4IoDDQqjU2OWZpdtRfq8SzzOYjBO+yx5kY43vpUdLU\nSLrsDc+EWcgJNZvviObcv+JwHEhNrQZxYGG6vne6yibF4Lrf3BsWS+mr17aZ\nWoPgoZ5pVJT+xb+T6wWIPRpLkfCyYoXA12T7WCpgQPwXcS1NVRKqwCoMaEPl\nMacp\r\n=fHaI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.7"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.11_1533892021201_0.503654340036368","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4940.3de41a.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4940.3de41a.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4940.3de41a.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"9fb259a65ee56239fbc3e8fca7f13ada036d3b25","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4940.3de41a.0.tgz","fileCount":13,"integrity":"sha512-xZwNNSUltw46XstOxz3p5heZEoigmJ/jFE9gRbyE0elY/cKl5cV5F/rfGtW1gQsaElKe0BzPccpp7RBCEVcRyQ==","signatures":[{"sig":"MEQCIAddaIrHcLyF2ytNANrk8rznHYmajyCIm/LjpcN374mTAiALxLe3c0NgsYBJyehuu4tn7ITTcLBUZs4+PechOiZZRw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":70935,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbcrfTCRA9TVsSAnZWagAA//IP/3RfFujbzrAdCdyXwAJ1\nbQ59G2rPlsCy+3HJkICWMf1N0S/ccjzzOu0mBKSR0TFzm2Of9HHvsV5Bc/0e\nMIbJyu/SdsDRQ0r1cnTSKsQvokpRDI2J73o7+VMbQGivq3YLG7RNfsCy1CXm\nz7fOYsgKRqFiNMJJnQtOuIug9KifiwcEdQsN7Xylrko9AopZYEB6t9YhJPPq\nPY2qEfjPtKoDbqEVTMxCQbdJTigJN2YO/W9sgsbLnNN4G9AcRmDXf/R0v74B\nXySbdTVLEVQbPsJMdXrfyDVF/ng6Iyzw+dJyBZQS0Ml0qq1GsZJOiBe84KAv\nl+S6FKPsyPnQuSTJTMty9hofwV1uVjlCLJMlRAJa9xYg8UCbCeKdt58tFuUn\nkpsxcRuLaPtQ35EMydx8l8qHMRs0p2+4jCHDb9WdfQto3ceYaZskwbiV98NN\nF+MuSigLNNDtgP4SNb6uEAk6MUTl028tWMXw7ZWYryKa6u0ywlhFBvDOswhn\na9K+7Dc1qJga0VvXsO9B7MCMs2e7XySX7Wc4a6f8OZlKRInbxoP+CtTxv2ge\nR0f+v27dqmuhigisFC9ZoQiD1Ok4XdX9JdcsonoLcs02Kph3KAroqjxKUjCr\nKnh3UEly/bCkda3RxhSKDY9PZaPCBjFNvpRRckTWsj9APrN7202ErwPqypia\nn6kJ\r\n=K2Fr\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### nodehandler-utils@2.0.0-0\n- RDPP-4918: Added pre-release support for authorization parameters\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.3","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"3.1.0-rdpp-feat-4940.3de41a.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.1.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4940.3de41a.0_1534244819464_0.8987155096896278","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.59fced.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.59fced.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.59fced.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"6990166435b6a9d30786aac0bf5795ab3e5c4439","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.59fced.0.tgz","fileCount":13,"integrity":"sha512-TXfncW7PBx274ScyR10UULKaiDI4mOeOQeCFdRjABhU+HNcPXJdir1UN3R8JYc2TcEvMXCny/e3dBx23SxuWKg==","signatures":[{"sig":"MEQCIAeuBjEJxAItYGX3yz2v6mRbRAYTcUb8SVsH7zifGf+qAiAFDmcjHrB1X46Ko/TL15o5sFVu1GHd9z4ggbXZqSWVJQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67838,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbfqWzCRA9TVsSAnZWagAA+i8P/2XjOkHZ7NZAtHpYjeL2\nFfnTc6Glz/I5JVTrOp0WHuhQLtrQisHjKnT9E5oCPFQbnxRzgN++Ct50YjJP\nm9YvPqtLODquHYp9+l92UQT2+VId0EcuArMziFWNIn+VZ+HmoJATpKZSAwy2\nbeziEWxdHxrEpElKDiBBeEhvmwFvhgiVU1RToppzun7cMGj8GkCrOtgH2aaa\ncsKBKsXU9YlWKE19xP6js6MVyy3AZeuetmbu04HXPPNvSmah9n3sy7G4AEwc\nSCD8hAw83HKAzD+hRs0svwPI91S4bi6nuZALF2IHe0cJg+pYMX4KBtoQJa/6\nmGhBNRrNntykACWcI4c7AOCpYXKvQiQeKcu8eb5gacAkxriSUVuYeApkXk2O\nT+uAhdS0v0ZBphTNWwYARZJyppiT5aNeR8qK4U8vZPMWwvDUwQL8rbyDVs5Z\nNFsoHxh3r0SQbwe/u+VYV5rCJ45/9tFgX5gnO14j/x18Y2MfKPgxYHj/a4cU\nqfeoJcW+e/gCmp0JihJDFO3ZJSGKDt2hEuTiBLcEZevW0O8jcSZ+KdaLx+mb\nn3L3X1fm84WnT/pk+ris90H7I4xa8APXHnCFVKemJSpU7Qsq8R332U5I7gs9\niL2qkSi8RxAAGygqQs+u/tGuoRlZ15ezlih0sm+zDqJn06JbKs+A6yT/D/r3\nb5ai\r\n=zPw2\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### @axway/api-builder-plugin-fn-swagger@2.0.0-0\n- RDPP-4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- RDPP-4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.59fced.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.59fced.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.59fced.0_1535026610793_0.208568927720155","host":"s3://npm-registry-packages"}},"1.0.12":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.12","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.12","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"0676850dfa8f0b536ca0d9e5c1548834780c1b98","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.12.tgz","fileCount":13,"integrity":"sha512-tIoHAW8Fyo52tOgmtoA11qg1C0yJOMfElhO9XQ0FpYzvKjt1W9nCXu77eZVY/fhwByj8WUo0TgyvWFWWB/8k3A==","signatures":[{"sig":"MEYCIQDHlXTnfUtT10Po/xtak9/8oy6igW0yDTDkFI1x375UggIhAL4nACaWYwO371cXKrbiafWn8/dOGXZWwxxxtd1D4Gat","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":71128,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbfx2oCRA9TVsSAnZWagAAhwwQAJWQ6dqHXoB3Uu273IoR\nOm04bfJv0mQm7zo3v/IRL3ehTlCYWvmGsw2NGnhTBfIF9S5UnTHppCMRquS5\nULxKkckAOPdeYNQE/oGgtP+MxXumMhQf593UT6V366A7aLgxSujWFsBqoMIa\nQxsSWtXl7UHIyytw6MoaQDWRLsYSE4NU9ap3egH/NZ5bosMqJENY+3vV9R6Y\nvdVLW4Yu6H8xOEuFVJ/gyiNefmp7SKMdX2NyvrgZVxQnJ3WPlt4QC0bR4OtP\nzqIgh0w2BQ5fqEHTHxdSHEBcu7H8j8VE5IseLXjvwiBwoubK70kJsPE8yYAj\nX+Rs0UYVkuG/nj01GyqmVh5neOIRetMkX2pruHb56V+J0Y0pSbdV5ytdrJOa\naysxL+clzlPHIW22XMF6Vyakdd4H1M1GLFTTLv/0U8WRZLGru/yGN7wM3YJ2\nOH+bdk1WajVO6RmzGZh0CtkC6R8q18HpUy+76HZ9L7SrwKW/sKa7lRZn6NDY\nZKk8ouVaylD9zlx1+2PKiJy7vRslmDCJexa/v87oFOE5Nac9ljL7If4XqaD/\nrzAe/uH2NZs3+J0Jf9xgX9rlkRbhIuGKWgIUpiKV6rMd7J+Ze1KnqeUWjPNW\n+uNIQ5bGL8oJMG4A8477/KDZz4OAs+c8bv12PYCczK1KSdHzvKm9PBVmICv5\nZ3uF\r\n=rR03\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.12\n- RDPP-4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.8"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.12_1535057318827_0.661909195493265","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.5ff06a.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.5ff06a.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.5ff06a.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"700953020764300c09e195d0ee01b0324e1701b7","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.5ff06a.0.tgz","fileCount":13,"integrity":"sha512-3cBRmFD/hQPRFvWL4zB8ZAbGEtws71V5kTCHQzTYqhBAOVpYc40gZYAHvfT47iZJ+KSdbFQaCq6odrRTzpqSrQ==","signatures":[{"sig":"MEUCIQDT6SBhVl50WiF6Yf1lkbhnGlLXDcDH7+x0cehgvDUx0wIgW10L3PUb3ImW5yWzQp+AC30RcG9t5NnlzKKbG1G53CQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67838,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbgBGuCRA9TVsSAnZWagAAHpEP/iqsXRaxWEFGhL/REzJC\ndVOe+9k7EoBajiulpoGe1DS1RUZDKCaAiZXgiXk9wf7HityBluPvfTArTvSV\nAmfFKXNzxkcvEv2yy0jsdtNvtNwYLmTwttdnAqxmYnD9gnPzO8WjfCo7k6GG\nete8QtanjBFMhAWp95VnSucNMFPAAowr3ljAvUTEjiPvXUWmOvJw1up3aOuJ\nMjRJjL5JBBckBNMN+Dl1ExiL+CXKbOaL+e/MR3G4En3mu/fd0A0EbRMrtUc9\nsOm4949D562xZURBNA2oB5uMJtgorPB1IVsNAMJG7GNvVp8nPf0UvL9V1cnu\nllE9P59MmZVkeS4umKY36oZaVsZT1TG1S1W3pJETVIanCrTKXyBv8mqOAKPX\nXmC9JdKWZczSLLsUh9sBKgoTcckf+x8nkQkrDaW3p8v+UtEy3vYZ/yVKfjfo\nj3cvRqlpPklhtjlOZnSZZ77OFVUgcgQ+NbFzLQ9L1Tfk3/yk6og66gVdVUct\nC9bwQJXYKxjKRjFHDlFyEKMhnx17QWtPNlD4JdoTs+AVaGnHZuiAAYjsuPCv\ntXc4nN2O1Mz12KpSHzNcHRipbUzuKCzLX3nI7Hq4qZIyyky9brlZ5pwGKW9E\nD8Zhi+ezi1bKrgrXmUH68Ls0t7/wcsP2t0JRDYx7CqSDXBYWiE5no8x3sJHb\n9wvW\r\n=VB8h\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","files":["src","scripts"],"readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### @axway/api-builder-plugin-fn-swagger@2.0.0-0\n- RDPP-4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- RDPP-4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.5ff06a.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.5ff06a.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.5ff06a.0_1535119790137_0.046153350717474506","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.bcf75e.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.bcf75e.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.bcf75e.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"def6c78ec953210ce5033eeeb698be88052f2c66","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.bcf75e.0.tgz","fileCount":13,"integrity":"sha512-aAdw2BiUIkCDHEilBCbUXn4zLDqwwepjaDeN1JmZdyDzBJRIopJ7VgD8XJyEelgUKA3aX2pbaaWRnw+tPXI+Wg==","signatures":[{"sig":"MEYCIQCcxHnhq7AmBLaAjIgLY3GUrBbc1wk7lQkqztS4Bi5ZbQIhAMlM1/ktIkYGvtRYzKNvZzBrAAPFp+QkqvlGvWCyJZsf","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67838,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbhlaGCRA9TVsSAnZWagAA0E4P/1z77/nlGmB6LDvrw9HO\nGrodcZrD9WNsoAb+aUFpmsxzRr7gbFlTQJ6zjW4qUF5DbaoR40wOnVZaWMml\nveYnKq8fn7Q/oD6a7iAWipWdYjB9zQOi03+ZVSXyV7MF6gvM8okoXeXpq7Ik\nnRxiXgjdAUWIiWtZDtYfe/TirGOSpzrtGiK/qBgfhesKUeo9/TmKcod21TyZ\nK+6irV8re1pEs/wqiqDnYXE296gDPl9+d1phUo+g3AU3BDYFEtvk8G+DiExw\nAOdy4MzUddKFUzodFJp82wikKVckwO9eI0s5KEP4swnrZQ/fwSnzNJPYNNEV\nb5NssHazzNGpAXdwtIHGtW/JJ07nyk57h5sGQtsEFuWf4x/CsP3PzaaqCUDH\n88eeKlDqhcShz27zpdgb3AUIqbwT6ncZxiF+if+ZUfK5oltsmnXMFnHELc79\ndRtvogi8sEz7X1sPZKIk46VeO6JUFJCmvgaNLMUl4zxlQWBJPw8dBprUr9vd\nVUwBAVFAdPgckggch9SXg9GfJ2y+uhZqyOT31kyYkGjP9nkgjcUT+EIX1fv3\nc3uw7dEtugvhtBnsWR/6r16b0H7ljo+Nmj8Hpd2j4++T98VrULpYoGDrxC/S\ne3lqJGiIiW3moP6yZA+PPi21adylBmqtW3C0xuuV8ibq5mGduUT32zE8kYzN\n17Sk\r\n=p7r0\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### @axway/api-builder-plugin-fn-swagger@2.0.0-0\n- RDPP-4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- RDPP-4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.bcf75e.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.bcf75e.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.bcf75e.0_1535530629264_0.8262540248808239","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.76d99a.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.76d99a.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.76d99a.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"d4445528a3f0b7f9a08c81494d4989973a2cd2cb","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.76d99a.0.tgz","fileCount":13,"integrity":"sha512-uksqHmjF7u3VDVyZ0GfMi2t02FnhXJljAHpDpPniHDALiu4cN5l+UG4qwCXJIwIWOzi2S1bYR2v69P6Ad6KK/w==","signatures":[{"sig":"MEQCIGKJ9QTPy9MJkNQNfO+rZTQ2jLBJTLsk6gORkm3NjLKWAiBY6M+gYSfLfgZ4sA2GJYh7hvQ0+GpiuWNJ/qFojQM9cQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":67838,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbiAvACRA9TVsSAnZWagAAcSoP/0mJSJ37zBcPRCfZIvSi\nywFO5y8iR04+EpTSLpXlE1VvNJs6PBlglSGkXg2A9w/QFrnJ1qgXQvufsy1V\n+90UpMTQYQixv3apR5o9NshFrtE98WqQlNrmO2uLgLW6Mxz3DWzQ3jnvV5gd\nruUNSPv/EyDhVSkuy4Ag8amICK+ZH2Y2tojIZhVxYoaV7rvmlSTzRr/tEyDS\ndHAqhwbwmxsOe5WmY48zHMi9j2QbH1T+AoxD2dvZ7tNvDlL+SmN5wGrRzuEQ\no3Lwe97Ldk7N2K86awPtbrHQNc8mO3sLWsFIKHqO6XR1ASxdN/c8Nl2dVdtk\nZ53YZv2e4rQ3OgAe9CjFb4NtomLnFYgSijM/Cb/zNSRhPWiycfuNOYqldbuD\nM0uMdpbMx/AzxSoRWX6UegC3eLzo4IARPdx+Q+QGCOYx73uyAJnksxziS+YG\nuUPg00TZC27tgXRMTnfb3kibvX209cvYG4b8nj1PJwpqJbLGoGM+uy7Ptqij\npVLuL/xtKbJwZc9cZFDUlZP5gkrYQiuThKZjbhhW7zhV/Lmy6xKEtJDwGoZZ\ntRpAhASfhqNGp4TTf3sFjdgo8DTVgEeYcZ5KFTy8HqK/vlNqCZyPVdxIwpLo\np6hXRLoNBGZciilz6jJMgJ+EozoCHMM4nXIHz1AYZBQ2Ubb+fXpFkBvGkuLM\nUgW3\r\n=QD5Q\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### @axway/api-builder-plugin-fn-swagger@2.0.0-0\n- RDPP-4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- RDPP-4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.76d99a.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.76d99a.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.76d99a.0_1535642559893_0.4057828833613164","host":"s3://npm-registry-packages"}},"1.0.13":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.13","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.13","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"6317575b06b37975c2224455a8034752a1fe012b","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.13.tgz","fileCount":13,"integrity":"sha512-Ks1xBS3NTDpvAJTVO2hsZ3MUohlsuUrixzSusqHPMf7tC/xNliuU/J0YJBfzBcwIe9Y8XU+mE0pt8VRO7jsvMA==","signatures":[{"sig":"MEYCIQDZULYOxxA3HflYU/VSeDEBGem7xQuiYpy2ZwubBcSw/gIhAM59P2dttBkTC/1TJM5HGGIWLwY2jhNKODaUzAuIThj9","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":71193,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbiQeHCRA9TVsSAnZWagAAM6QP+wcjt7IBEd51ErWSKEdM\nH6vi6oyjk5XwTCyHil7R/LjOhF71QMxq1abmREqwxvl5AVfu5D3mHakzc51u\nUxVawMr3vn5BDBzx9pFpYVXl9IXKFJdPu4QZ6cwHvtAwpgDmrUDOKZCCC4Zu\nuJUsq9L+duVw79+cdU6zmaziG9XFFiTGnapLG528NMNpnlgPsX7DFCqfve1x\npH4QkSWLxixnfSsrabxG6ZKOiAOBUp692oVAABAevIbgsTOB/J2HJR5MU9JQ\nwC5kiOiQgTuYmCBLzra4M+mZyRmrk8qVLplKvGXJzD1HYOVZZilMRt8zM4up\nIxYW2YZQKeQ3Hx/zuej5JvFLybDlmDSxofqKqtwmeCZYzF8Azw2RSsl0143Z\nHSW5U2gPNw1lNlOrivUll8p0Jc1nqdmxWQE9jnUcvncyjwkx4jYP0q3VCb/0\nDxGVpvrTsE3zkVLDSc/HF5QLk8nE2AdGfx3V7CKJtk4Hi7pBn8jfomo3li2f\ndTJuuJ5vy9WFRcMREp1IKcEtyj9tL9GJAgsSVHct90Je+KSwC8G24HmTZvDK\np9nD3Nfh74xVVh8evf2bIOtc7gsBg+B2xGe/dcje4iqwot1zaLU2KJMn0Cyn\nimMOFpGOTalnODm5DJX2IwU0LHw+Wl7K1JVxKviKF1v2s+4pZZ1MvmTUPJSi\ntLmL\r\n=uWme\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.12\n- RDPP-4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.8"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.13_1535707014368_0.6139147728504935","host":"s3://npm-registry-packages"}},"1.0.14":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.14","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.14","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"a50b58539a307639a8214cacef3246d5fe99a835","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.14.tgz","fileCount":13,"integrity":"sha512-a2AyDArgcadS2Lz20v7E7O8xiK5uQIBquKAKGdUQAsc76ZIn/11AR4K5BoFVSfLhWMZA6WwQMmKiijJV4Ey28g==","signatures":[{"sig":"MEUCIQDTW64BMTOmvJwNjuF6SO8ex161qbDGiY2WbjLuuCqscQIgDA5fHHLGu5QrE/oTZ3AwwKmquELWyGKuYUkjxS6Ju+A=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":71678,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbiSzRCRA9TVsSAnZWagAATKUP/RwFgL9qi7sOMfsoRchx\nHa918IAArJ8efgcf8qBF8Vy4evHYuKP5hVZlCcBUL+u/qzq9V39WfZA1K8cz\ngkWyOB+oLxdCNfo5p6h5r1Qyo7IhJMjnQxo8TOksTOEFjY0VJUraG6iq7pem\nOKpoAholAUDNWrAWRsPQCp+eZhUUi2FLE1mJ6u58xGfs4hn93D6NqO3qDUpQ\n3X50DMGfObNcJ6hLZr+aFCT6iLl/Xj5NfwqboRv6OHbtBIdHP1PIitEVyYNG\n3Ar/4KV66U+wIy4SKGAh4gB6EuYixVlNyXNVun1kOSKC/l0U1wHHb2g3XX5M\nZdZ5zXlSJ81m5k6DFnPHoPjVp40OMGkowoAcAst/S8ysP975lBGbCQxf/m3Q\nFDQ4RlJi+BWBOLIjFHHLFzxTcTtTAXEGFmf9vujqZ5RL+bKkNsLbX0P/A5qI\nIJAZ4Blk2a0spjqVWPDeIQYpoja262zcQAlsqmO46f2MPmiFPgeCnHw46y7P\nlVT/i41V6+iz5gm/ikdPt94idzdsB8/yBwYj9h+3Q8fU9YK2eyFTDv+3CUht\n56wQAhfSVJ6QrjEeKb9z8eNU+PlNC5BaWAmhC7wCFe9T9JW/U3lW9cJUMvWg\nHW56YwuIRv3azqLCTVbtqgpbeiKQ4KN7YWAwwphe0Wvsh48+nKvblqkUIpLm\nrpQb\r\n=K22O\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.2","nodehandler-utils":"^3.0.8"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.14_1535716560717_0.2759935043177262","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.0c3b98.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.0c3b98.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.0c3b98.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"dfe3ac117e9516cdda40a69d85761af2388a220e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.0c3b98.0.tgz","fileCount":13,"integrity":"sha512-q/9C5Bpu66XWppcHoLOEO2+2InkKgH9cUWrRWJM5tqe5L7Z15HWcyvG7XFpJbkKblyARTJWEqZAJan7pKGB+NQ==","signatures":[{"sig":"MEUCIDgjjlJsW7Rp2kw8cqGhNx+FDZVhYkCVku87gXN2lva6AiEAw76FBB31JH7BDUji1wC6OmM3MxiJFVWSN2jjCobLkVc=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":68799,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbiWVCCRA9TVsSAnZWagAAjwEP+wVRX0jX6QiB9HUGtBWG\nmSsN2aG000witlTjyived26KlQxduLrflDdo7KHy0pPGz6Jw8rtGoU9og8lu\no3H4XdQ6lJPh8SewKdRIhDanSauc2+hyGnY54S9BTWfDfPCehbRKtInlVBGW\n2vkywdATRN4m+y0XU8gi1q069j2FRzlA7IyUmvqPBI8E5+mfdYtVnt8S3R+9\nsjF6z6c4jAKxbtXeFELDReurmKmiA3Cho/1d+7w3kyZoKfqa6FEvNfki0flR\njm40FRg8Vy9hsAABHDxzK1OJz311nXZ65RdYXlZITJ7722IVlQcmuUVTAqKZ\nXkwt1/yjVUQmV5k3o7ckB8JAPDM9qc6A1/f0ll58c8F+DhaUkUltze7JYqqW\nRlNt1jCD+NQotnR9KJ9VDQEofCdi2YHhVN4aeNKK82/YDuOQnAw9tYfJSpmi\nChhosweTKTt9Y6aYS4oh/E9QZcXWdqXVR8gbx5B/iaDroRDIp6Qff98U/wSG\nwYwmW7SK77RWv05kaIWnkXNJfy62wJxbnqXwtJNHmZ2SU51JRDlEUKQF2SfY\n3rseSLoD2B2oy1so9G8ckyzOW/N+5XwmwoZwXQCPYYoBYq0Yzl3uIkRuFtXb\nRT9x0p01Jsqi5yhMpUb38PshgkIBNMBImnRCx8xBvXZRH8SaYLNPmMcXc2ZQ\nIDJ5\r\n=5B0X\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n#### @axway/api-builder-plugin-fn-swagger@1.0.14\n-RDPP-5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.12\n- RDPP-4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### @axway/api-builder-plugin-fn-swagger@2.0.0-0\n- RDPP-4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- RDPP-4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.0c3b98.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.0c3b98.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.0c3b98.0_1535731009859_0.40554103952356724","host":"s3://npm-registry-packages"}},"1.0.15":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.15","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.15","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"3979ff9cdb12194d0c42bb873a26280f8d1d4f2e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.15.tgz","fileCount":13,"integrity":"sha512-E1EqM4AKu1ozLGdCf2vog7eigtm+tZQ9ywliTRJyAZVQuwWsuwTGLQM6O/5v4AckZB+0gc8YbMpDsjZ0p6B5xg==","signatures":[{"sig":"MEQCIH901OhOXINnSJVWSbYb6mj0C4Q+U/Vv+oScKE9f9CmEAiAfhoBddJp4G5UCVTCOkkaXv2T8XCGXdOWP77w3xAV4ng==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":36319,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbkSoMCRA9TVsSAnZWagAA0acP/0Igq22VEC6f0vMNefs6\nwTP06SV/2onbxQb4CJWtr7wmqCwKd6rwXokLWi2Xd5ZMST3+vSbTXMumuy0x\niZdFj/BZ64B3Q7kfHYKjSf6BtkWD4w4hzVNHQM1WuRzUmAWPzHM3hQThG1jl\nRdX4SXBMQIl92H74X8msoKDdD0mI7CTFg1kV1yDDSIR4Kmj2VTOVQ/31gAYA\naqyS3V1j0d/0w35zmpW8SfgOavrAcJXex3mYLxGDYKra6BOA1v10hwqJv+Xx\nVGoU3WlYuwoFCng4g8jgiuyMWLwxltZsGHzlaXDE87QkImfDQmjlrlbLcuv2\nBoP3IM5eOt9U9YuAAKcBN99ljju+k59m6elyyTPXFFjMk1kqWbDbQyvfR5zB\nBYl7jqcfqNapQEHvIJc7gb3R5Nm2VputMGmoMyALeBTv4Wn5cotisNpOIDT/\nHJG7w8pd3AmTao2Vdy7Wf0RcISV1QzWKjJ+ahYzOFdyoftuhVzhrmYGrvMVo\nEdrcv/dIS8Bw+Ost4SmttN27S040XySRY8wk3b/j5O7sSFAshwYCGPrp0E6+\njOKrVoH9s3vhzEfj8VlCYBcyzyQCRTfoOGlQJKGogw5ANtevriNDin0HFYbi\nsiFmMaPusAgBnPZBrjnwSVtImNC6OU/cW6ByUN7UU4QM7Df2F/RK6RZGwANE\nra2+\r\n=attb\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"5.6.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.11.4","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.9"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.15_1536240139709_0.19889403964269903","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.adf516.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.adf516.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.adf516.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"24aede9798ff64034073ea3b94ad9e177c2a0abd","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.adf516.0.tgz","fileCount":13,"integrity":"sha512-aKi0BuTofu5hS97Ae7jtR1xRpGWwfsTJIl2TomRC8aZH22Qo+xBbm9Pqs3SZR1A90EG+z3AlNcc0yZxPEkt9nA==","signatures":[{"sig":"MEUCIQCbtPfCYfzmqIqE8qd8apBG0xcks8TOlpBF3DuHnfTSAQIgMRHPRZkCmSmR7ZVNxMRdYbG+O7EpV8iC1WDr+mx03/Q=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":68799,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbmiBHCRA9TVsSAnZWagAAUtsP/2QToIYyFGoUJZMbZDGp\nV0bBMkryP5ZCV+PCIT7z9KCyhSDvzhFYMzOl6vU9hfWLs2zDrmJuyzSQ81Er\nLu/1A3cKIip60lKl/t60OfK84c1I4YRerX+UZWKqDLtMdGR36Gi2Ta6uhavk\nbW7ksb5CwPBZ0PLo/194jQxjDdVxiI3eF9pEnbzYADBCv81h2EvhPpNdICeq\nmrbM8X0RegnsSbVAKm3DUOycZJFzbZ1bwnyh8tuksM1k3Euq4P3+26LfAIf0\nBYmdXU03ffSCjeTHlq40A5EhvZZ+MS0KEpcv2KWqkM9fcwQPZfZsvSxh1DeM\neBHqZJwaBw9pEsybPd7bX4OFVEs5gfPaZrqrw7AgItY7zPG/WU2UL4gL/6tq\nujIRUgRSe/Z5ygjC6msFy1TBcBF44FjWHMHvOaizhIQZyRSEtYzeNBwpD7kT\nQL4TBs4UwaQkawclFIPOfurbkRCLLFEHj6EQtNNNy22gWUg6hqwnH8427mfX\nVqmXfOV/+U6tKqczQk25gZgPWpODKBxZOJgVfX9YgRPSpCHIhltz+uOzwqIs\nCD6H2vEP3+XNKQgTpDZIC/J1mH1ViKciq16d0eIm1TgYuTWq0ZKAbUYerGIu\npFg8+AnxiRIu9oViZ0UcI3nwxXhd36VPrPwQDVyYV5pgrXlJ8BZml7CcMM0t\n65O5\r\n=56TE\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.adf516.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n#### @axway/api-builder-plugin-fn-swagger@1.0.14\n-RDPP-5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.12\n- RDPP-4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### @axway/api-builder-plugin-fn-swagger@2.0.0-0\n- RDPP-4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- RDPP-4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.8\n- RDPP-4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.6\n- RDPP-4757: Changed SCM repository and associated internal cleanup.\n- RDPP-4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies.  Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions).  Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.adf516.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.adf516.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.adf516.0_1536827463129_0.7700952769201319","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.083e37.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.083e37.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.083e37.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"11bd33b469bac5db3713665611ce3f239c2dd76c","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.083e37.0.tgz","fileCount":13,"integrity":"sha512-EFerWYPykn7iaOm6ePlEl6l9pukapMcwRajSOciuc5G/PcpTRsocvqZN6oNaT7ijw1aDfB8iPxYyNy4g4f3G6g==","signatures":[{"sig":"MEYCIQDhLQe3VxNavOnkAdEMa7DgCISpvhsAHhlGsqsSJhy3CgIhAPlx3vrH4QqKQZ6CG9XSkBc8t1/dad/l18pU9tYpmeX+","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":33395,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbmn2sCRA9TVsSAnZWagAAeHcP/j6bUS6DwC2qPv5CglyQ\nbVErn0jCil00CBnS/XPR2f84PTmeVuHnULmksNTqq3ePg94bEQFWrwi4jO9E\n4vPXhuGc79+BBEhdfHwwo9Tng8n4/2IWY/peJJzm7VEB7SEWZzQ5SuL/lweH\nopdCGE6HWVchfwsjpUHL3Lqz4RaQGCo5Z9tpkIxumNImtihB5Jfe2klnHNGr\nziVLKX7Mtf9RVT/iF94JWArhF2quWPdjg8KLU/4qGexBN0yTP4IY6l9153j3\ndMIyA4wP6213o4kaiIws0Ytz9nEZ3eiAOMYouEmqMpoyNYm4Np2DzWEo7IWG\nMx3UulvVMO+rlKAVhLvFCpi8HXTFFzoxVQEgX5atfD52kR9UrWGhVGhoqd89\nitsNlgQS0GPlj2diEDwetKFOLzlNL3HAd2b4KK2QOkm41kqNSaN0SOwholco\noqXkZO1yC3PS8oN855NygCZD7spCmGftXqol4arMct+qyQ88zqEcmBOwuYcv\niu2s9qSht8ydBGAVOpShT7ofP8rpzfKK41GkZRJ4lfDqcr1YWBZyh8PwREB8\nWzsMukBzf6tJ4//xn+U3apw6kf7ynxKJZi6yZlpLIoTGjVZosVVzg+MROig+\n3/GIGMJFP45Ja65Dh8XYJh7j7ZGxMaCNWj+NUQSCvrnd/IoMG/rTomxA4iVp\ng0aZ\r\n=U6XS\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.083e37.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 2.0.0-0\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.083e37.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.083e37.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.083e37.0_1536851372045_0.21930398652627803","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.416e64.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.416e64.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.416e64.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"2a336efbaa42e2e8b4b72134887495db7138cca6","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.416e64.0.tgz","fileCount":14,"integrity":"sha512-eTBWY0hY8ZevbdK1Kgn8mKwnIravJBRFO8J0ZLt9xgJWMV44GkMZajO0xO0JoFzk3dl0tpiNvEkiwqVLbU5tWg==","signatures":[{"sig":"MEYCIQCB4zBwYFddhMNHbPZnE/jx8KqxZu+eGpHdnp+DKPSYCwIhANV1R5t+Vm5ulkX56aqH2baiCvtBorj8id/TZkKTzc7S","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":38030,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbpOKYCRA9TVsSAnZWagAAALkP/RagQUxkuTdnadHMCPN0\nrmsqim2YMsduK+sRhHLcC2V9xtYbhmFOAg4xmTaYC23awjM2r+TriJnX+IqF\nq9tGp/IqvC9q+OnAfJRa3Shdq99smFg+X1QHB0kGutWV80e/2wwV8QQ73DnJ\ni5VA7z/hkfDF9WM0RQHLjSQf4iW10rUs3Y1H8upmEUe42LdAH1B0NROJe7MH\nuETstjmGltk5/25UhcKXI53Lqo1Bn6D2nfoT9iuCXZRLDzSXuAzRyBPtO7Jp\nEzeBMMxNRO+pyVO2zkpz6j1UbwIiJMZAiYK46ts+qr6R7sTbA0t6si8oT7Ak\ntcbsns00C1m9/YfdGw8gia9Kz6LaKPZ1YCqpRkStuDZqUZdx7VLM+7NApE7H\niLIxDxjLtpb4cud8XkW+QLlj4uNYuN3TssUK6D98AgxJ05ycvLNrgjVBLWEI\nMVzXZ5QcGGypaKpCVWomk/CCiK+L9HpaWacKA6Nh3rjp6fBy0Sjsb+0spFTb\nMTt0HvOs1AtbH2f6gFW5J3kup+vpuKeHmUaX/IsaRy7EUUhQ66aG/hK0rCr7\nE7k/cxxyP33UkQtMcwgE7EU8UT+m/KzeZSoqdShfyph6wTSM33TCSf+TEBI2\nhpf3q9rCfiN3mLpsn+mcJlsEsdYDjCubHHSjWE+zQF9lX18FCqr1XnYmZNyy\nSZT+\r\n=p1l4\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.416e64.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n#### @axway/api-builder-plugin-fn-swagger@2.0.0\n-RDPP-5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.14\n-RDPP-5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 2.0.0-0\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"2.4.1","capitalize":"^1.0.0","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.416e64.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.416e64.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.416e64.0_1537532567759_0.9013745227761745","host":"s3://npm-registry-packages"}},"1.0.16":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.16","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.16","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"5a3b5fb1c38df6030ed43969a261ecb296f8f264","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.16.tgz","fileCount":13,"integrity":"sha512-F/qrjFW6vYpOFcW7IZsF+2CoaFBCFFWa9YeXW+NDumdBO2+jZKnPiHV/vFP+v2vaTdlQIl32pCa06iuzX87yRw==","signatures":[{"sig":"MEYCIQC+PsehGa6/cHEwnEgc2es6Jrf4woh5fO8A+pZjEskmkQIhAKtB97sFUO+BpDHgN8kgY0Dk0gRHzQy+ZDbIucpyjNQF","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":36595,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbrQVxCRA9TVsSAnZWagAAoLIP/3Jbxrkt8jMot2Ez88AL\nmEdDNO5S2FydsBmA3AlZQ0xpM97tlwbc56mBJ7BzE5GVhTDi9Zs4A0wa2RtS\nn4xltIS8VKazYnF0MZpIe8DpoRL/n+xbxoSE7eMuV55VfT/ooBcPTfxbWW0T\nmofUSiOJ00GMpE28usbOgVyQoBHT94kRaZ98xMVZvGcfazL7bJ6yKJHh/c2/\nDTjL09kLI8Dy1XBxBU0FKPkkYt3VyAeTtev108zAsq8yh6gCLv+TxJrnGqPR\nRZIwI3nvSFET9Yvpzi4h+QszGKYMEsZ9j4yXKi+B2TJyKxB0fkuQrP0JDKDf\n+aRcfeK8G4s18TPnL7aOUnI5JE0SgIwRD2W9m+S/RPlHpD10QIPpK/geulDy\nZNUWvP0UA8FlhwAeig55hXVGVuxrk4OR2k3s4rwGN7WA7ZpXnXifl35HAcdS\n0sozJVVm/gEXLvnrR46/6rEiN4ZNEFCwYpq9Xw2qv+Uur53ue/0DvwNdp65L\nXYgWv4bYRamPo1ZHJQzbyNd3XGWJLz44Vl3sRH3atfOPktwDqh10qfxGbL7Y\nHJFhm7MR0Kzc5XACKBr8F3o6Qr7eHTJPRGgmSBBbGe5PQ4pwry/zujOy1dF6\n+xonCQJWd4n1zoN3S16a3bAElmcrI1bptTd+KxZYIfx1MuodBy/I9wA4vOs3\nhgtV\r\n=mjMh\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.0.16.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.10"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.16_1538065776206_0.5903703620916592","host":"s3://npm-registry-packages"}},"1.0.17":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.17","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.17","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"a6751eda5b326af738c77554651582bead28cb87","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.17.tgz","fileCount":13,"integrity":"sha512-JwRnSVwbTmJ34FOoJHwXtJI1LXhjK0HohgEZ/lZe2BghMLHf6zDlX+66RFkb4zUJtZPATDhR+s1u8IHoTKMcVQ==","signatures":[{"sig":"MEUCIQCse9DXRtVUZAIuFD+1XvAWHuxv69TXAfwvc/bwaJflTQIgG08lboC468BkUUJeMzgXzLggu1aqzSUjzBK7wgk05QE=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":36775,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbrfBYCRA9TVsSAnZWagAAsX4P/3TyK8IgdvI0I0hJHwH1\nfrwW4XzYtRzpzPrCsicdIWGCmGWP8uwuCWIVqLH76TPKLx/V4kS/ImV8kGU0\n7YDJJfXiKZ33+sAgMIKbeUcp++USNZC4HrmXPvSAOILkFBETwPLSgGW/SbKE\nR+umbVXqsZnLnTBTOlhclxjLekmuU7ZeKwwkBNmbrXY6t1InaTTm4XWbouna\nlbFQh1EliDkL7yf3fjsAAukBiFgMi0q//DTVAlDmLba8nt4g65cXnVraoCgU\n+asDxM7MiFnf0b92WNCHGv5TGHT3v9nqcpwB+Fr4XXgwSFM0yfeu2mwnSQ7/\nqn+NTMazlZmwC8GJNNQwXrktpA261osvQPr6ABGhOM+57BsnKuF2wtFcfO0a\nYP4FC7L8UBLVno2AeVjW/FaURKl+jzp68yFk0r9fYZzxD5NloKafygQAY8Cc\neEXFp491Yj+Qvp4dxRulLkMiZzzgYHsBbOYv5iUFEeAE0BBOnu89bvOnDskE\nInLYeX3CUmVwaTY2kMyXxrftf9/Jkwwy7gZsHxO0BrrOaBKG/FHGEKhM6krf\nhtmXUDno5AQXnrzaF4W5GhjSEWk7xYkieUVU2VToIK0l19g2ZGmwdPU99kZj\nltxmC4P4CfW4RUL4sClpVXLrljMn7VFaaAR8iQa2JLQW6NDQ2goYB2ZoctU1\ndY+5\r\n=zwod\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.0.17.tgz","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.17_1538125912014_0.0952158251581332","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.804579.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.804579.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.804579.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"8d98945d87b10c9e117751658b27f1c4e3a0edc6","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.804579.0.tgz","fileCount":14,"integrity":"sha512-ABiGrpRcmgEFMrSvVMYx0CtH66WJzsJpPAvLgMQmjPfeAW4EjSbJJHtuKr1vbP7CoMVw8MXMKAZCxiM57ri4Lg==","signatures":[{"sig":"MEUCICf/eszV3Az/m4Z5BEiuFR1ccDZLnOJ8lsbe1tDZ0k6AAiEAqaRuWok70UulcFbIXd+T0QDOkifQmKZO+h2fdatoPWA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":38485,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbrjJ3CRA9TVsSAnZWagAA/AwP/01WKPTencjhzVYJ512R\n+YfJYG4t8FhiPiZsXD3WT5j0YVXJ8oKtTzN5tzBVWb6ZMWOyXKNMfatcl9I4\nbg/eZFgiYu06I61vDsx6mdUzmLlhk3Px9qdXCfwYtiv5Qy+dvYMReB2DQ4t1\ndSxP2G93hVa8Wz4uI0aYDe+PThcrtDtiCtsjVKKO3HeyX5BE4HKlPXfG9sJ1\nROnnUCMhKKUMNy+HryrQiYqm2XK+OCFJKt09RnWjg3KtH/2BSos9P/qBZ1S4\nzELpkMfSMJOW+JZnI7Dlz4Zc9pJWDNlNoQo3iQ+ZiMStMTFr5DcxyJxQqK9V\nA8KL2PUEFlvF6aLze3Hk/VOwTZYnkodHBcrUb+KGck/ZB2sCi5SFkrbHgiGl\nCkE1pjVAO6Kr8unXaSEUGiurH9vZn4YBqw+F9CkdcVePjdZS6GOVJCWTmxnw\n68YbzAqF5gyX/yoZ5jV1itGm367IIWOdhuhmYrGt9fifnNBO0n05UGe9lxhI\nVdHESnOzK0ecKJZw417P18xPSjELGmb3xXV6OAZgG0L6A9qUTOPd0LdZjNOz\n1Ed2nr3QSzdhNCO8ogfTs74whyd3NQu6j6wvsQ/tqdNtZwL9aKrMHc/emNkk\ncxwRNmEGH2aV9S7Ae7zgZLOMmm+0bEbzl3MGr8mhv7wX6801DvuY7r0YFoUq\nqJSv\r\n=a2x6\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.804579.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n#### @axway/api-builder-plugin-fn-swagger@2.0.0\n-RDPP-5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.14\n-RDPP-5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 2.0.0-0\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- RDPP-4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"2.4.1","capitalize":"^1.0.0","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.804579.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.804579.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.804579.0_1538142838642_0.4826456707565887","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.a5e408.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.a5e408.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.a5e408.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"e12293e974652464d5f209a22b0215cb23769139","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.a5e408.0.tgz","fileCount":22,"integrity":"sha512-kigpbbkuhqSsnEivB26j6PVP+zUFyKmwnCcljmvgXE6KFRlYDnTW3a4lR8ewU0tqUoIZMjVT2/AogkczatcLsg==","signatures":[{"sig":"MEUCIQCUT+f2Pqhv7G6IM+CrYyHdzd76xubui+8YN3WWitbGGwIgM0gKHAebYeqmRKSIZiVcrkQ0+nT3Cu3pc11hZ48Jrng=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":46203,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbskNlCRA9TVsSAnZWagAAnbYP/RfevFwQm9Q2hSFsKCXI\nQWoG7XJlYTZGiOvwm3VmHKC/d9icsPpfsMu0tcVL+aUkmaYKPpjZjaKT+mT/\n1p3C3P2cxfMsjRe47iEAJPinNfIs8z9RGT++kwOwMiMbGRzi5LqMltB1QC1T\nBZlK77hu2r4fq1BcJWmtkCLSaUGm4NyP5Q7YavU+2gkReoKsc382nnNEOBcA\nWKg9DCpDynUNtjWKb1zovmprO3FC4dDqVyNHRg+jRNn4qiH4JRGViBseGjm8\negZjF4a7tcLBOsw2LgN5qYZm0Vok+6YBKQX4dplTK496nhi8Vm+OTwZEAFJy\nCI7jWoJoce6HEgR/BPgefQIC/bSxULtcEkbZ9brZqUS2NJk2JW/d5YKiNwvA\n0cVaCEAo6rKMCC4ipYJHPjH7KMUyvvLqgywYwTF+q0QVnIrwZtdrm3SNGXTA\nWj+vq4lG/jCiTPApZlPjwWZifqM5ntLJ1T+NsPvD+yPmZPlvI2RGcDDF/7iq\nl+ji8X10X917Q/tupMlI5jL+Hdn2IsV1ZKsJHaZS25A/oQij69bJKlYjP0Xr\noJI82hfA7Iukbrw1O1GaFgdb/nKQTF+QZmH0alkAE4AcDnJ8jA4RqsxFwNwY\nOx0f6VSfn1SF8/VuJneKyBbkLLlKL2fK2DNqqnv7qzKtEFxjB1Lt2rCn9KYY\nEDxM\r\n=n+Zj\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.a5e408.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n#### @axway/api-builder-plugin-fn-swagger@2.0.0\n-RDPP-5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n\n#### @axway/api-builder-plugin-fn-swagger@1.0.14\n-RDPP-5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.a5e408.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.a5e408.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.a5e408.0_1538409316322_0.5789323237680604","host":"s3://npm-registry-packages"}},"1.0.18":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.18","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.18","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"e13d0bd786ab3c0f3e71b22f273f15a75d250342","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.18.tgz","fileCount":13,"integrity":"sha512-DaLQDbRNrXcSlvUme0kddUlBe1HKiwFTaFypYAcz0E5ww/PSSmB1WbYBHEtaEvlSEs3dmjIQdlxIe4KXfhYxYw==","signatures":[{"sig":"MEUCICpbDH/GtB4cPvSboYKal1wJK5Lml+Z1myuuNrvrt2evAiEAy3oimYHU7r3TWDHr8TXoPGgu8439vhBR6ref013xTs8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":37129,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbtHYaCRA9TVsSAnZWagAAhwcQAIfvfWkF1drpvjLDTpta\nHhsdEXiJqxvOccIot5ruQBCr1Qi2YZnIGlFKxslrMFynRtaZMSTtyn1sNV0R\njlAIo9PhD+q10nh0UnJmbhdQUNwIqhgCZNYyaYhNRYgDHj2PSNn0Iv+A69Vv\n6FuDbaJpEISgqy3ino8AVdx1hxuHgF2EBfBrNBrwzDD5JOBQWWUFkkPQ0Rf3\n9JynabLS6hvVpq9ATEAKkT2tY8Q6WMySLvmzruOiHDvzCBhuokFsoNU9LqYX\nPYGj0ElwdOo78w3H1/IigpQ6DyMiEjaALB28T9d3NW0pkrhg8VEk6XiIASiO\nU2devKjyvDMx89emR4dXHxf+r3S8IzpdM4v0A7sx2Lnpc1rY5dKH1PocjIEq\nYZidg4H9B2l7k0+acfeD5dc/pbzTTaxFVu5TXVAnDYI7Rpz79lmr1dvXyhN9\nWx5T+H1YKnabwflqQJrh9pH+D0b/2GM2cpp6b1igpEvP6HbjnAHBFG95OoRN\n7iDcrRB4RsDW5V5eYqjp/jny3L5854gO+/v5Qg/1Oxks2JZjlGEMWT7u1662\n0OrbOAIiaq4CjWiKg6nYIynQlIdxKP55OK6u4CLKvPBxlOxRurcU1BdGbhA8\ngrufoVgqXE924RjTr3vIA9OSyqj9eWW22sgrhlH0G7bdvJdXeU4vOsa0+Flg\ntQ+T\r\n=/NsX\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.0.18.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.18_1538553370059_0.0020983215132286404","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.c3db6f.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.c3db6f.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.c3db6f.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"5aa59526f2f8140d3aa12792b5d78a257fcd46d7","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.c3db6f.0.tgz","fileCount":22,"integrity":"sha512-gnDtQqWs29CNxxkzyw+QaDjdYSWPXQbFSkPGNtqOhmnCp8qSvBdPvw+NrR8mc+ACePPmACClSehNDieBrqefGQ==","signatures":[{"sig":"MEUCIHEnaUg77pprZU5ZekXkxsrirMRill0Du4hFaag+e3xbAiEAm1qkxjoGGMq8ZeiLLBcYjQzq1Z2LmTOXox4/Ps7ks2Q=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":45791,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbtgIrCRA9TVsSAnZWagAADcMP/2uGAxMV9OO5coMellfI\nLYM2Mab0/EPo3zrQzSYJalebfdlBvoFrar4cLdcABhE5qkxB6tWOJatxuQfr\nGZBEFE4uMtr0tUCHOMccZbdsAyF4BSRNPqQXhP+WPZtfBi+E1CvKE2W9guL+\naqrOxsgnyNdppDdUDth9FUsXsUTVEHLpfHCL0UqitgWMl66bYch4V82mSlCA\n7DyPS74JfrfVbVrsfSuh1KWEpSSlH4lxXb3fG86r9H47kwhtYu0e6HPvkO0h\niimqk0e6qBNpSBQRgRrMLozB66VKivEs5DbBTFZjX2j0OnAvuw9T46yi/qDi\nKhkK7lB7S/Oxj3gYyZ1qmvN915q5d00ta3TFyL/+83Hblw/F9SewPnGRiuWQ\nRvOmdTeArB8VCzqKRSPnXoYXa9cWyM2PBLVP5C0tpArm3J8mIOBwIL4/cxgb\n2mpT70bTOapt8Zf3gIov4v3670SJATvmg6jqBF7upMy4RP5p2Gu3qsvsQ91N\nQinHEYTGE65wjxmz2APBEsrvJV20Ra/5EImXxYKEqaVUMY7itZ7b7ywaqChD\nYzLbv0xDAhQd8zZQ/opgzL9YxByP0YjDmXkMzfrqktnGxdsTTLDb8JF064Th\nA7/Gk+cTLThvsPK0xgiREJ0V41AeesZU/jOGt8Fs4kxPO/ZSP2xg01XuqmMa\nDdJP\r\n=y+nL\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.c3db6f.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.c3db6f.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.c3db6f.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.c3db6f.0_1538654762536_0.4690347631447489","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-5235.4f6541.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-5235.4f6541.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5235.4f6541.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"5c3e3da43180a54aeb673a72eca92457b11734e0","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-5235.4f6541.0.tgz","fileCount":22,"integrity":"sha512-vnlReMBLhGnZTTNcdqTN6VFi8i5hzJN89TLYTcgPMg9F+heME7tUk8PDy6YN5PF9nPYzqwvNy82bjHHpcuj+dw==","signatures":[{"sig":"MEQCICsTGTBPrpbIPiUrtFC/XAvQmiOCGh2uFMwPgNS6lr2kAiAdwJcvend1F5yoCJTD3QlrUi8WuPxQMJHTXMk+uR9Axw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":45842,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbt2e1CRA9TVsSAnZWagAA1eoP+QGZdjaxh9zXg7pgRpwB\nPYa3s8Rn38vf9A+QWaEmeYRzPPXEyO11PE8YLitDEuUnoGXrx1pEM3VyXzVO\nRCab4j7xlyb1HNsRid3StiN8H1zV48fVHZoH27VEgenWFBFIlGch73FSRqg0\n8aekEJpox45mfe0E2j/GwBN5xa20ifcZqR+vO1qk3wccuTaYfr2aub6GZd8m\ncPMaAyoIRoz1cHg20QrqFozfUF86hTr0Iyp2o/EMjvZ+XjrMuvLRtdi6oIs3\nt5upilaZ5VLJxFzhtEw8pc6FLGAxfs37nt+/eX3p2I9JrFU0+r3BdBb35+aW\nJNTcDExZ9INuhFReFqo7rtj3PjF0T90PkwtUWnwk/6Vgbh5pLAKGXXK9PQtm\nc5CY3JgjYUXV0wvJ50a/LsTQkhWNaMWE9fGv6rlzZb/aJ/8iaDC+z/kHsnah\nBnVH4cTdlEL4jCIpP3BWtg0A4FfhQ9pfamC6X/kku2csB3FFqtWbH2nLhDR8\nZ7vvlhCQmM5zyRt5knbbxT9Gll4olaK67OTiVM86F84xQWtCJeKTz4NWIXie\neJZSHqchtHOah/xzeRPQMG88uT21vi1v6RkmBQpvot11vJUaCrG7G8n0/AqK\nH2xkySXMuJmFvlWLgTcAppos6QAKLaYPOK01/wDoxgGw0JmZ+lPfl8ttNq+z\nSVmD\r\n=FeOB\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5235.4f6541.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-5235.4f6541.0","nodehandler-utils":"4.0.0-rdpp-feat-5235.4f6541.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-5235.4f6541.0_1538746292277_0.26860229763672017","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-5162.960006.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-5162.960006.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5162.960006.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"8575cf41dd69620d892e55e1ecf18160897b4635","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-5162.960006.0.tgz","fileCount":22,"integrity":"sha512-qzmF14yVUyQ9qF28CzrFve4LRpRbEpLpwF1NdfduLK/cPJ2pXBEKmZBb5k/ClLE7bhcNxqgIZLLM1vYgaZWdtQ==","signatures":[{"sig":"MEQCICg7wGhXCivhql+N6XtCj8ckzPpUA+Hpl0elMs1G4FhbAiAsOxR2Zpb2WVTsFQUSSAT01e4h/xMNDq4aUStZFUIUzw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":45791,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbu3GDCRA9TVsSAnZWagAAqbIQAINDxRnKLVqzyXFsada1\n8CRnRh8uEbMax5BJUdOJvGjlDNu+rlwXF4TcYJNGdDNNAwYFsqhUNvLeN3uD\ntvnDWA0iDfPhBggh2zg19waFrdNf3nQLna3P04SB9BjxEBiT0u6t0gkHSoLD\nQccuoKDp9vQmKMATuNBpnvdStwbQTOWk1th7nFvxnHOTdZXTq4MihYZXczj4\n9+9Kevz2nmj9nRgWpUqIVAgBlEwAOPZTEfffD8rX5nYXxMlAlXm5My4M0Oev\nMUOQTSrjDyGi3F8VDG6CHaGug7AF1ODhV9rsB/VbwJqaFmPS3e7q5p/3P3bk\n1mGnSpEKofWsungMPYHU7+HAeQjEMw6H6GgYF8Bg6WcSLX/UntPzgDspAHLb\n/uYcIx1KnHT2qo7cC8iFqLZn6ucmZ/L1nf41AY7ew7gEWT7oWYD/Ur7WtGe+\nxBHIDJwBBn4gcN0LrBM6pHrMf69yEdMFUQXt/1L7GZrRAe/UwR7AcCO1JmYa\n22TToMQweN//E7XSkUHpnj0zPIrnWvAC+8jpid8qJSKbDZoYVrjfzNC0olC/\nc//sK2IrNAR4ca1yRqAueOA58jelF7PkdiyJjU3v6tjnOaroIAs/CcFI0njD\nieAgdBhD9i86IEfbRpu98L9gWg6eI+SvYW1dmN/uHnCNVa+xMLySeMBQw5wr\nID93\r\n=HLp6\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5162.960006.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-5162.960006.0","nodehandler-utils":"4.0.0-rdpp-feat-5162.960006.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-5162.960006.0_1539010946854_0.6182718951294821","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.8bfb82.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.8bfb82.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.8bfb82.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"296177acb47966c451f25396699669f582e044e2","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.8bfb82.0.tgz","fileCount":22,"integrity":"sha512-3F1BOBrQ/mQJA0eqU4/Slt2EOCvA3i93U82fk8xXAcO8ydfhihwUSsmaOgjXa+e8lYdI0ZbrO4LTnBxJpj+Siw==","signatures":[{"sig":"MEUCICzbWdXcRlABN4dcZlDC5uMGZJ/OFfh32FpldUlnaaEyAiEA6hq6pKd29PywLfd0w2RPYlJKWnxqB53+JYXav3ejOaA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":45791,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbu3Z0CRA9TVsSAnZWagAA7YoP/AvTfSN1T4VAvhHBeydw\niTuBFGslDrmrD1/hTppagkgL/7FcZW/iGEe34ecmOXQNOuxjAVAEOvEU0R04\nURoXJBx0IpEUh/lF+2XuU6494a8f/AJf+ZAg+hrcbZao4InenNFkoxpE1hDN\ny1XD0bI2OxukM1zzGLs+o4L5z+cr6MuNQy23c1aFqPe5CQqupFs8t8Tj2CiY\nDVb72jKjebeTUw/rp30b+UofeZT3j+zvPkR7WaJza6l74xSHw7FKDvTbEBNK\nq0l+busGyg/hFhR5QMJbMmPV+Lo7Xzy+eGce0ZEPzjKOGCL660iCddwGG6ZV\nE/SupMy6534XBHtHuPURDULOlmseurmtSS8cF/sQvMAayAiP4zh5bkdef0eA\nv5BCTt1pAPhXv4IX5XhHNnq1s7OET4G7kofzOnHo6od+CiFDTgmKKsQAmTkz\nO71w9YaYe1lJ3OOzo6pGpqmmWy1tx7BdX3RKR6oNBQ7FLxTyxCngomu9Z+PF\nfTME4ueiCO4FQ7DgYjXYcZeG38Sjif5Bnrtxe2w1S7b6GvyCowKgrglTz1mE\nUmzVnyRmQov0xW5fxRSJQDAgxOyouC0NySMo27Wto27gqHg8Lsm4qwcwWIj0\ng5xOJeZNwm1Ah+E8iuz2FVaTMMNjzx98MVfutRfn8o6a3+80+C8ZHc4HBBEQ\nXRLA\r\n=bgBZ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.8bfb82.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.8bfb82.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.8bfb82.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.8bfb82.0_1539012211436_0.8989043551371378","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-5235.29dff2.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-5235.29dff2.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5235.29dff2.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"0df8afacc62b4e18926fa5e1c822fd1aa4d0f53b","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-5235.29dff2.0.tgz","fileCount":22,"integrity":"sha512-VYw8REdnsSMserSf9ocG1fovajQMBdYKEWTr0M1DCX1SOinYNOXHEISAVHUQfrOIHdIggdM6ewjtADg9ytARHA==","signatures":[{"sig":"MEYCIQDjatLuCEu/e5I4BdQk8OsIpD8427MdjfUDoJaLPQy7FgIhAMKu2lM9tDom4jOBJuT3VjYH9NNIrqbJCymgBzHpICoq","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":45842,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbvGn7CRA9TVsSAnZWagAAw3kP/R4bkYcCwtciyQq7MeCq\npVmB9/wnECLh2Z7hAYP39YMVEXWf+5xT3IruCgD/mpMJX757SP9a/M4rAyaz\nF+XqlxlPTL9a3lBXTiamH1VVgTMHgzirS7hb2Qut0fOWp0IBfQ1QSOK7B2CA\nqObGsKOLxKKvqumtz+YElsocZh8uW+LBBOodYQuEFbvNRHAlrYvwYIdxLIzG\n4OV7nwbWcFxetAmQG8kqPKVC5d/Ayx4TLD1F5xHgDNUWkRfbfnErtFRzMdOz\n/vNaA1Tca/zWCDn3vvDy5XUyjZcEYHYHJqDF5Rx3TWHGDBCweKidWNRsEUbB\n9HWbPs8huVHUYWtFREY5F6isjKQ69tT6Wd39VylmWEsasHR6mO6AQAnXdWfJ\nWVMmpHCNuQVs2O2Ww//f9NFKxOFPMWhPL0WnZoiiWvfuDkZLKWxrvVDlQ8sk\nZuxPU2fZD2sYqfujIFHAEThBE6b8AFHoOj6XNTKvn96Ce8HU8vHTUU0WUGDp\nXJ0OrwMXOrBhLvzvh9tWnmiSjvTh+hgu1cLdXsXNvwtbWteXgJc6Ci6XeG8z\nPcvRwbAkWoMTXYKEm8BWlWWajiotmddJIIHFG6iYOrLBs4h+aVb5JsOa2z9M\nGsQ7IuBBCXR4nh57NREa2QUGS0YPqZ5pP11kIkcL1JYwSUteMg4Mdo5qjDjc\nO60t\r\n=10BQ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5235.29dff2.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-5235.29dff2.0","nodehandler-utils":"4.0.0-rdpp-feat-5235.29dff2.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-5235.29dff2.0_1539074555030_0.7969213216384028","host":"s3://npm-registry-packages"}},"1.0.19":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.0.19","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.0.19","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"42e0118cba4b52559cea9d98b044487e46af7b19","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.0.19.tgz","fileCount":13,"integrity":"sha512-7ailG9a+i+4yeCXL/jd/0RSi3KHBfkN19MLUIYMUaayS6tifRiX04U7q+SMyEa1qIRl0RUaZ/DzZh02Jfbol8g==","signatures":[{"sig":"MEUCIQDC3MD6zz3+4cku5yJEHp1eZA60uK2fOM8OQc7VtEISDQIgYLXjWkOB9u0t4KtHM3hXWqH2daBSdjtMoThvKoIkLBU=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":37180,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbvGrrCRA9TVsSAnZWagAAQvIP/1/quIQ6Khnw9mJE934m\n+Y5/FfTzEPdJyQ4NnWcD36gY0pmCyPtjYy8D+5eTb1tLXgm1NzsOE13H5Xis\nAk5I/0JGkD3Xmx84OaMn5J9tbMNiB2NxJvEmQCYs2tQ+yu/RzEpdKMRQc+JL\ndCqapkuI+XFLORlM7hmAfqO+60v8j8fE9sg6nLSWXojmrvO9qbarl3/Y2iG6\nK4GKafrflQKUFD51yeQZXdPVBpDyW2IeyitawF6JUPaWdycFso92HD/UBe/Z\nGXKAos/u11oxMmEQ+pLJFCydJW9K4Fh/bQipotOpbjKLoqlaI8I4VbM0+Axp\n7KwLfrDglk4Z2roTkXUc9qzji0z2dLJQCe91B3GbEuD4KDcLMtfZeF/cJ2Mo\neNHmS/13ZvbMeBonIGzvqZ5Xx1KNBulbH+TJiM/UidTUHQfxbVn1QthMegux\nKjeMv2HYf5/lTigNQsZ1n/MvV9CsgV+26Y/pXH98hj8klDEYk2f5qa9YK4xg\naa01M3R1XKia4Ea9XeJ2RoxDOc3Gm1+PbQKUCLRpt4c76ZtSM+51cDQ+e5rU\nL8MXKm9Oni77BScLf2Q50WxAUDmU0n9o8Ks9t94oxmjb/ZNXL1pbjiZVujrj\n8jFdbDi3Awi8RfWir9rf5RzQAGhQqJ/Afyg+Bm5UOirLHUEYxqMNr+Kb20Ez\n38a5\r\n=us3c\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.0.19.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.0.19_1539074795063_0.5586511452468836","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-5235.b37758.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-5235.b37758.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5235.b37758.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"618fbe9c9a2d2d8a2bccb6ffc2bcbcb81c6938fd","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-5235.b37758.0.tgz","fileCount":22,"integrity":"sha512-9fWABxHbG8XEJ1hW2C8HBRUwqrjlvXUwA64LNJfQzokBCIBN4z4VZkke12mwVsqdfhqHvD88Y2iv3/w5lqmv6g==","signatures":[{"sig":"MEUCIGtIIO5eXIcTJenmKJmPyqLWdE6sUWf9ticLTGaP+FifAiEA6MZPJtLEZE8NM8u82UFJ6Hmnf4uFDSDoHqCn1E6GUWI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":46058,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbvIHqCRA9TVsSAnZWagAA3AUP/3y07lEmv5i9HsR7Kmgj\nv2q7T/p24rnE1jGGU2XtofoZXqO29wQphivKyv03Ti+1l5+tpNL4iwljovaf\nmk+wBRleXRlwu0ND2XtWe1QvuQuJSj4VXLEOhYJXmnmAddXHXgSTfazAH6go\nk2CDsRWIfFKJ2iFq/f0PMakzeklRULDZiQeSvXBMwG8gZM9nqEMgtOshoZgn\nn5tq4NcR4y3olS1ii+3hbGtba5m7SOiix0I4XzH5p3Fi1Y5fAMMru/88pTNh\nvfP7kIXfdOSX7QFEgSLfZk8uWJ+GpNnNSpZ+CAQgBVouiKADCwPPg4RnTaee\nEDCn8IIkygv1XQxLh2WHcTx2ttBEWFHgEc7sD97JWh1y3+CY5tWt7woPDziz\nxuA3XqEU+VrLk3TjibIKzp0Bs+owkaGrNlBcyJlf/1192B3Ob19Q4bjFmp6g\niLgyqcJuukAn+nS6PpvKDWqf3AGm5JudXZe0fVBEvVefv9Stx+NFiXwGAXvm\nMmEpLszg08qStnnDrKYZhs8trB8DByl3b8ofzUBHPInx/R2/ULCP1kRkEiQs\naLzSY+CG0E7hrMX7+IYkraEQNE4bOeehRvujC6W0iy9tBsfpgvCKxRoLdAXZ\nz0zgq8IpsONE5ChAZMDj42iV65HOatesjdPj1i1XOTi5PHs6i2pydBf6MU7o\nLH0i\r\n=jitW\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5235.b37758.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-5235.b37758.0","nodehandler-utils":"4.0.0-rdpp-feat-5235.b37758.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-5235.b37758.0_1539080682486_0.97873244909309","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.2d5162.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.2d5162.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.2d5162.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"6104be4320b603fbeb8f0f7b1df0cbaa9a47809c","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.2d5162.0.tgz","fileCount":22,"integrity":"sha512-5wmBujewTe7OQMUStBzlMRu/cT83hnYex8xhau4Pg3q57huhQupcvjRrXU22r2jYSn7D9fV0L4OCK5jbLX7pcA==","signatures":[{"sig":"MEYCIQCXRruUQFcM/r1o+l1jcPy7/FYtkH58jvlDjmNIoR0t/gIhALzAA0uHN8XBvMYh/Pk4KHrjNNkjnFmPyb4Di7V3Zx0N","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":46058,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbvINBCRA9TVsSAnZWagAAAAIP/iNx4y3hlDmTo8Vs4Ktt\nAALGh7wNLghG9Oym9odfjQgyL3V4iXhA1FpcbcrKi58NmRobq7pOddQc9Xfx\ns2MmSUNIGfOBx08Vu73OzvI5ho3qTZjly4SDM/VszqePsEjgjphUjrTJliXo\nbxdIKVYMAHbM9xj08evjQ98dMs1STKgabVROD3O2vSKzSjqtCzfLPkFhnbKa\nnRj9zTpxDDicncSnrkfr1ihhatGe0hVNCN0kX6PImHaQd8tL3WLBtM8rRsfL\nwL1H+oVc9Vo3DhQCIbQWhr8Q+AsNON0jUYHSnjiEr9RQQgx2rmYqtWDR1evk\njTO1jJCcKE8XzANd+UG/OrlJNYvTSihLzzKK3m/DEEI1nAR4O/zZIRH3/4XL\nR2nVIy1LtAAMesfTTUraRx0VP9R9V58ljAw0Y1HR48Yb7UiZsJCzA/ea/ejn\n7D98b4UDHKyjRAVzB1n4vU1/CPhxWbqFhynkjC3IL2hm3A85An9i6wVLVcUo\n2IdR3tE4ZfMqxjzqrIT98BWFeWEgxBK0qIEqEKiFZdLx79q+7ZaBMZJzUtL4\nEvxMPrDoLjynvMWeJo7rwZkrqZ5gh+k51jR0F/M5v8yocsbMvUJL0rry+/ap\nqeXVaVC8h4rJvlKnZ6ytLgZ759beAnt6B7uwwKzAwERufW674YjXKlo5jOJB\nJOzb\r\n=y+u2\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.2d5162.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.2d5162.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.2d5162.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.2d5162.0_1539081025076_0.6945635985534517","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-5162.b48298.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-5162.b48298.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5162.b48298.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"c856d7ca453fed530a2cc24659ca041a0d2de442","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-5162.b48298.0.tgz","fileCount":22,"integrity":"sha512-hfO4EVZ4AYr/nyb/zVSNQ5DlbHakEeVxq5pxFSDEmreNv34bxIE/hRMpVclF6xCWYni0Lzc1pTAkfxCSmygC9Q==","signatures":[{"sig":"MEYCIQDRVNLxxOpeIZhYzdweVLH/I9K3ad7PzDwCuxJZosDt0AIhAPVA/vQbwrREi1FqeGl6NKsqrFrOqfI+pjqD/8TEJPqW","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":45791,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbvJjUCRA9TVsSAnZWagAA3WwP/jfrKd6FqD/ZeVMab7wJ\nfqTu4R6yA8lp0gbYHq4kUN1TgJ1GyWsMKIjBbNrxtP1UyBV5YMuqUkD+RDmV\ngl7/fsK1DHpO9y3Vw64Hmow0sdmzcNUZxiBDlqmxVO2OQFvg4yc0aWbCQTl2\nJmitrdOkhlFhv1aaGezZEz1+3SZN5mpF3adBux4QNSyRgRZr1e8jyHZ/WqIQ\nnYUpKv54S30fwWEhJa7oh3bXGmzH7lfVDct2W10viDHj6oWqdJIUw8W8DGzk\nvyqhvrlyBIsX4nGQQwLQXxjkD5GUEZXa0ALkpqMjHRM0oRV0ameIU2IBvmrX\nHfv/IoDO0hNWtw7/loMD3NWe5ve+g/Jk6H/RR791INL6u/xG1Vx3R+Hrxtmu\nLoAvmxZLqN8oLBLSZ6ulxdHsN62D5vGgHfCeL5VrxC3Qh0dshuSmy9scnMC7\n4QJ6YypUzSsBTvHrRQ2PdgCrfJpKjdqPj+DwG1FnToF0cBRYXSHSk6L8KmmA\nyPY2eKbONV4MKHK/PgL8P6PsvNKe6ip5Ij+NTotRGByCMndAsM8VlOT+PiKA\nD/1zpGfShSSJSCDIfQM6G7dObu4ralRZNL1wMHavPrh3jFmkbhH7RH7N5fxw\nytgOMDe0cM2IbOzzQPw79bTn8eH9aaJE2JhUt90uchaZBtmcz4AovrTjBMZj\nJuIM\r\n=priZ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-5162.b48298.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-5162.b48298.0","nodehandler-utils":"4.0.0-rdpp-feat-5162.b48298.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-5162.b48298.0_1539086547467_0.31671513494759274","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.6bd6b7.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.6bd6b7.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.6bd6b7.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"23ecf17eedb3cb2d6498ab8cb95a5901dd52e112","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.6bd6b7.0.tgz","fileCount":22,"integrity":"sha512-voDFqEOjdnF2Uerv8fcwXjpIPSmzjkQVxou7G6PIeGWZVARPvKslx286EghYhjg29k/iULcKsU1xKkI+WvUHsA==","signatures":[{"sig":"MEYCIQClPIOaSAOwdmobMTIjrHSrbi5Ai8v8rddSAXkCn2BVvQIhALapD0sg4Rf+eoACgf9OGbqSP0D9I9+ry0+g9UOLlU/c","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":46058,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbvJnHCRA9TVsSAnZWagAANjIQAIfdBt/VwCuw7eSQfooH\nizmhFb7SPAGcZ0F5Lu4JYcE0CQCklEto0fDilkmfOIO+XvImLjiBbZQmKgO0\nfW25t0vZ8hFnEWppqe5VMrjAyQOMP7Rb8hoXkQzPqN1Rg4J65f9//BsPobS1\nJuDJGzih0nygWlwMw6wSnE0zc/bacLKZR7Bmb5ug3Ts3q2TeKSu6wbbHWtxR\nC6R0GiM2oDXiWywlJ/dAc4QBl7j+Kt0TzL7LIMsk7RJIGgJUYL7iwXhOcLfP\n3ryjAiTUJJ5eNQAKjbI1lCYn4VN7DplRgW4zz+3shzwd4BLwRhxY7+nhdbQE\ngLQBlXO1S3DxRv+95ms+xL31ZGJbwLo+xjrp4ryP4CCTdSGj5ah1ZjK5IAE8\nPn3ZsdGToSqfDh71iVxxAmoyZvq6fu3rgxEFK7t9iIlzaiF9tlO0lLh9UDio\nwcDS6owiAThg32vZbNwH7qUibWr1sugtIf/10ROL6r0i4vAQ8TQxZ18JLad7\n+9OCov07lmo3Ik3pV/HMjf3Rpg1rQn2OLGCkX3k1tnxkGTfwTfg4gdNR+Lvz\nmdsHr9r7yCInwwWLKne69QiZ2L9k6bTLv0tm+l7zzBTy8Hv1VcITX1yNBCzl\nIojfVBRaJ3l5qGPR8I1vrnZ/toi+QA94igpwILPpA/egzFxLPOsdC5Q7hHwp\n/3bb\r\n=J84v\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.6bd6b7.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.6bd6b7.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.6bd6b7.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"sinon":"^5.0.10","mockery":"^2.1.0","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.6bd6b7.0_1539086790611_0.2025031636214687","host":"s3://npm-registry-packages"}},"1.1.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.1.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.1.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"f671578f024ba058a76ab84a9cb2f9e361e47fe7","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.1.0.tgz","fileCount":13,"integrity":"sha512-IBHGZ7xijBeh0ja3gAridBqgEf/HadPq2hwMaCp4xmphMucWJix9T4R3Eusoauu+ASwwAA3SQfinjihe2d07rA==","signatures":[{"sig":"MEQCIBKQUYHfsF4yvM7W8bc4DE8i2N3bn0FNe6H75oE1peEkAiBSv+T4k8bQ/gHaYzBPY4OX5eldtMl+9Ywe7th6XCtiCw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":37839,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbv88tCRA9TVsSAnZWagAAKgwP/A3jvjfT7nTexnbno7HC\n5LeaoM9ZYdOGKlrblb284nI3VuP436bg2c1k+SS/Fs1mI2U4RhCqNrD7RNup\nRs4XqbIlKAhLolgDNaxKlfywBfgkZbbhMpVjsjfGtRbVPhEXSsJzlRbyEH5Q\nGmRoGJ7h/KReqi09AaJWdojhGeTHfQv34AY55HLOtPGCQ9Q6VRKWysFuil91\n9Q+bpRwOH1gTH8OQc28RAw5zUczXDQiFtryOkrGndfvg4Q61F389s3riGZB0\nyGtHWX1B2bmAudhN/uL3f1mGql0d3LnhF3ScGqtOOiV31NJJ0URsixMrL4Fv\n/gTbryqc78aSfwFSdNv+cmb8qlmklZ6vd7mWVwvoNslcGtLK7bvfn/bEGYd9\nTdvbArbFlxdTE5n6y2g63CeiXLe9XytuS3Cdb+7NlIwAzBkIjtoOVVrIJ7bi\n4Un622RpppLk/LNFTksV4HZNFTuQG8w01ZZeR0060HN+xV4QoAe9BirteAa4\n9ifH0R9bIn8hVEVL6Tz9amWEZsp57yroxlf5+APUXf4rv0ye/kLummv0/hBN\ncYf0YcLm2HkAZgpkkkPKO5MOX/oJh9L9sQRIjWugZDf5PX3djPMKHrgGt9S4\nzKJYEOWR3uk+vZHsmMYiIcz09zmLkPGR10/ekBYHzWtB6fUf8fxMyW+ApG+6\nAnmm\r\n=21H9\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.1.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### 1.1.0\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.1.0_1539297068369_0.47354933627804874","host":"s3://npm-registry-packages"}},"1.1.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.1.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.1.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"76c9dc7970781bf6073da90df6b9fcaf5ab69995","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.1.1.tgz","fileCount":13,"integrity":"sha512-e6RZFPweD8Lfyftk51xen5Q3ygNFzt7ydmQM72mdq1VG4t2Vw1+l/vXIL2cJU/3nuLJngk2wmJjGV4PbHBONaA==","signatures":[{"sig":"MEQCIDKQ2ZS2lnqAq+oiBGvgnshPIJb0mqVI1kO7p97EGmGZAiAmIU0Cvg2ty4c8ENgq0ERw1F7pyRLLtLXinI/HevaO0A==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":37786,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbwIS+CRA9TVsSAnZWagAA8MwP/18nYGY3R9kpRcx41mKH\n3A80I7VMa2rlE8fFF1PsZAkWDZECeyDxs6K967Z8IaXB1MGCCI3d9zjR//xb\nn1zGz8AzzHsOKUw68bQS6VZCdXh+Vw1fCmCWNFcVy/mJTq8+CGBQa2zPuFiv\nu9zbFMSzTXPyH2bh6RxVvWy62tPkEvpNMdMWYMoEQzWsJtJd7DDxqn0A9vGu\nScRM6U7FZPRQpCNToWf/IKOqibASMIV1KACU1/82QknyXAZVRhbmREBmnqlC\neFxnX4W6qzj9j52zPJ3nUQwwsKdz1VbkNKJz6hnsXsMJ6alDdvlmEE0YO14K\n3TvkHWocZrRi8502GEpFRKV++y0ti7F6fOCFCdbbfzl/XxejTZ7Szn2uTppf\nv0RtE//C7XAaL1sVALCpJc7FPLUq5hmsw3l6qQTU4/13o8C3xsOK2SkKbKwS\nxXzJlGiAHtUjAfGTpIIpgHs41owyy6Go5ExDTG5LPvAVELHIxVo6Fl7PVKnc\n+Bz0e/O+ivENdTOVbu88/E1s4CfmN05h5WVEjDxV0HFXpcnrTvrRMZi9qyle\nmr8bdhlrLd3DCSH+DoAksR/srTAb1s7VtizYdsS/18UEzwzkPxTkDg+PmkG+\nvgRU1vE9Ujx3Ql20yt3ORdPV0zHDBllgJBI/znkdk7jbcX5cM72aR5189C6m\nfd71\r\n=4BwN\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.1.1.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### 1.1.0\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"readmeFilename":"README.md","peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.1.1_1539343549775_0.5783950988284026","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.50304a.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.50304a.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.50304a.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"07cb16fdf6b68cb3f416879374d3d4d814e3396e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.50304a.0.tgz","fileCount":21,"integrity":"sha512-ep+3Ov6YUO4M1IfJ94N7RHtzpIzXdxNVDqbKW0C+Uu1fNdCS1+CMMyCGBknQkyXj7tS9fOG2HWF+ZNe0J59CHg==","signatures":[{"sig":"MEUCIQDo2hwlUp5xpbMAK9G/0sMAflhpRc6RKS5AgZmK9Wd9owIgBBMnKMkDdy2oF//A79cjvInZpx3yJY9MdClvxBVSzOA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":44564,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbwIWSCRA9TVsSAnZWagAA+B4P/A9mvWGusoPrioZy2Y+g\nkzaE4jl5nnM4PO6zG61oUzcZtVRsi1a0T53fokYvD4RJvfjbxyCFAFbqb1cT\n56B0SQQlsPbgvnrw94FyHp6yo8+PkaC5A8M5YucnIDsA3w8mo5su5SgCXvJt\nL27xDWzaDE+8Vq4lu/wNrvbxE840xdSPhtM4qBtt3rnOLwUeo8a8T4Jsf24j\nrrdF8QiSakUb4GEorlEpn9ow8UK6k1hJGAaSRwdBZztDC//xCznCqYnK5xrH\nlqlDVypvqsuFCVUjwGGO0nIboX2amzfuuMLoLT17rhb0buuA9BczZjkrJL6N\n3n3js5C713VrUQAsn6YGOK7DEERbOXtlhSqLWC4/bNmaKIphz5KjHyvvGhdb\nTz//+Twd8j4v1GESVDftVx+qduHlBBDHKQoB9nk18A6LYIQyFnxXx5x10RUC\nIEh3OfeMJNp8dgkTv5w5gWWDaUhCyl104gY4xKxlGl98XxGETBEDh+IrSPmK\nFO5Jnp/HjhGh/VDZ4W9k0n3wmx7/+FImNDZrgO6TZeFV4oVi0B5nFddLHfeY\nMfDf1SlTAOFlDPpUMTQfU1aG6EN3nt66Febryej2CADm1SI9CuQwA206yFfC\n8lODiz6GyLU/b6gyR2wNdVys21B+8PLZIfQDRqcB2Pc+iqARFOCeWWlQWFYz\nc1nJ\r\n=J0Ju\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.50304a.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.0\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.50304a.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.50304a.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.50304a.0_1539343762214_0.1412042594145826","host":"s3://npm-registry-packages"}},"1.1.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.1.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.1.2","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"7bd6d6e090ff48f074de69230af57d5a09aec19d","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.1.2.tgz","fileCount":13,"integrity":"sha512-yfsPzcl1FdtNLUBeRBZQ2/ieRTUi613GmfJml235AdV2Iyw3lZ92VYfeD/8yLOPt1LyAhRg5w6PiXOT2dEZhPA==","signatures":[{"sig":"MEYCIQDFc4kixoDSJI34LBAa8XcoebiXBp7AjCRvS6+ijueRTAIhAMKNGtbNYiUKRw9uK0/g8NyCwfb+k6bRMFtS3J19bID2","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":37701,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbwI9FCRA9TVsSAnZWagAApOcQAIXx9WbxsjowSaTdaLUO\npud1Zut2z81QxSahJdyF0BCR04lkWsRgGOj1rYSXqpISMbucPGzcHWANE3dd\ngoQnT1dS/5K0aHHSCOPcJAXeoYJlJ0k0hivY9aB15ba/tbcdTnFGj+srmld0\n4cxPOy2NspZMzHtja6Tu5/A23YbFN6JTO6EBIModtgQvFp8UNSiBq/OL6Y3L\noJfaBedojfiUvBc+FTaOQttbYNJTCDMj4huUqaZY/FPyCnTLTrlLsgWs3NAN\n0TYX7dntIiMBt0RzRdiSR7kjYtfdMUEI7M0UuVMFlSePGLNQjTg8hDOqvkVx\nUJCTni7x43hxVyPmbNPgIBcbw6hr7u4Bolo09y5qUKxmi5WKkt9r5bF2sSSR\nuTuxWYj+ZkEqT0pVpwXTxK9zQqNh8ZjG8verayRcAvzy9PMEoL3A43VjR+pU\niPV+Ivd/Jb+evdG0EwPB+rugoTn+VLuxpgTe0k1g0v/8gwe7KE9/5InHru/r\ny6WZ0g2LhqXIb8qRd6l7G4qLQ6MjEU1g2r27xdEbAnMV8b/HjfHX9bBvFgZe\nbfGnmI/Mtj6Zqp7JAUI2T95A6Ie9LN34h/b6VPU3R9SWV74C8Z3DdgeHSGPM\nVzYA+cu+u1e33/9cDuIN4bEBqGSiJWG3VRy2mR71BqSlfOTzt0ThjncjLTcU\nr65x\r\n=8bjH\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.1.2.tgz","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.1.2_1539346244949_0.10246107784167191","host":"s3://npm-registry-packages"}},"1.1.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.1.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.1.3","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"2bb4ac2a555db802f942ca1ae537d803d765ae25","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.1.3.tgz","fileCount":13,"integrity":"sha512-ULroJLJXy8Xh8Gs4Edb172QM8863gWbcXsqHm2pW+svYa2gUSRzRu6rFdhgE3iQ1IdGI27RCJzCTuZsfJvrX6w==","signatures":[{"sig":"MEUCIQCgubO5IOCdGjnraDnuXDzcTrRz5zYosRctrQ3zcEKt3gIgYrx5LbyuSCtekub0esiQreKVW92X1pgFfiXU760u9ao=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":38089,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbxxQHCRA9TVsSAnZWagAA37IP/A5+Zfaz0mu8Nm4Z96B9\n+EIgPTjwD0MPoQGC+DdysqHkTX2s/FneGR7M2z3/N9TjpLCQ9gGIsk2dxFes\nUvZIOUVBkW/e/tLM1lSOVjGknGNhtwzz+UJ/pnz1neUMhBX+EELGs3tpN4ij\nSN23sfnBDUk/LRPkJpeorO6HBwyWJM+Jc8unUuqzsKIGyDKRf1VPhVC3VUe6\nRwtjGMmlqQsytN6/ATzrld96pFCf2Dq7a0cHWwg2r4t3WUsIDeTpvqRc+L4W\nInjQ4ZZmKwiUmIUsD0qtTjvScq0kEh8ct4Tn4IDqw6xp/+idYR8QWyx+G/KU\n2au2kgYzbrr8qTSaCULqCPkwn4AnvmVdIb+mLQHKp8dzpC/EjQ+m3vWSgVYE\nZ9wsoDgYnT/X+JZcPBBFSkKwNbR5pI8suTzpusMk96FmTF8JpAXQxP504wTy\n9kfYEtiU4NePqaQpkkxv/qqBwJU3tffec6kHhgY/dkhuc1rtzCH7SyF/ISgF\nhnCuvtxE0HFL7lWNjd/yOuYP8+QwyyaPV68Kt89/SnqaLQ1mzrFK8RZ7Xp77\nXxrKac7bW4pQSRcZ1Or06eOro5raN9sFsoyR8ZBNAktGUO7aeZVM/FXH7c6h\nKQWYFoPwYEQOyjDmNLBOkMjhHVC49wsMp5c3hhiH9rFljgMksFx+Y6q1inrv\n1EMq\r\n=0m3S\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.1.3.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* File upload and download are currently not supported\n* #5235: When an error occurs while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document.\n\n## Changes\n\n#### 1.1.1\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.1.0\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"^1.1.3","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"readmeFilename":"README.md","peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.1.3_1539773444591_0.3172530862549945","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.629929.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.629929.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.629929.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"6f0af9373c54438c978be7bcd412987f4bf36d58","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.629929.0.tgz","fileCount":21,"integrity":"sha512-sF18tFGHH6tMUZHt3gLGqx0lIqFHeo2NnAIU4E8ea18+i1KFcKG5yclLnc2FTdB+isIObEejVdMXb5YcK7llNg==","signatures":[{"sig":"MEQCIFiErbRgQDMAnAmjqpcxBoyIPH1jKRIU1eE9Rk3BhLSZAiBY/+G7jxeXbzUE2umS6Jr7NROAME5ZB3ub5Iyb8GRJ4A==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":44730,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbxxTwCRA9TVsSAnZWagAAVM4QAJIfHnT9y51qB0jIeJx6\ncQasq/HXcrISNtBES+bd+oqVHH/GvwTUCnNK/sum/jDhMpn6EeY8myFLS3WV\nK1/UDgyCpH57jRuwtd+HZqJxG0vVFsfJDPChhuCdsXmRivHPltsg66lTlXdk\nqbP6Acmu35MT6I7y1qd5PVe8JWW2ZwPcH1ZEUGkNy4TujKplnnWYtg7iVOk0\nkzyhd63zMfmCl7tU+GvAObe0VsyMGV7pq2m0jGigA7K1MQMyJZxFfsaIMN7S\nttW2temsv8gMZSlvDQlSCfipfJ+cdOPSCl81TzlOsYXv9FjlquogAZ9ZqbEH\ntqgAkU3VJVhXojIMd423Oi6c8ur6DxIDB2kkzbBgp+TQuWnrFjXoltx2+ctg\nY39sve4IJd5uynQI8AyoxzF9I/sVXrp9ND7h0xziTUbkAvx3PWhcNHQxMkrx\nJJQW8DdigDicHSUY0a5WIB5QxdGDor/j/7XEDWDyDkdFneNflS3Z9cWLY4xB\n4n4J/xAErQ0mMZhnAc5v2eY7CNj/uiW2DdxrAIQ3l4SJJ24ojAZLq+XAGC3S\n+BHg916RNN8Mocl4pWDREGcIr0rMXuAKWw9za/iItHTvOg0Tk8gFTfnlIR3y\nZGVP/bgvoNGsI2mN+O0fpa2CcRQIOnhyejpoCj9IlzVZyzD1SqRSprzOKURj\nFQyV\r\n=24vG\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.629929.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.629929.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.629929.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.629929.0_1539773680108_0.9931898361791998","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.38ef09.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.38ef09.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.38ef09.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"5aadc0d271f8064135ef36268209843382a8895b","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.38ef09.0.tgz","fileCount":21,"integrity":"sha512-HxjO/3L79vSoz3UW9/sV6dRqBb+Y8KjyEB3M62djpJYGS+e2Kbi2QpsSOyUrqp0vlxnmJJAVBZ9iisl57Vfn7g==","signatures":[{"sig":"MEQCIC7voz7sfkJxSiUiHNRxUykzfK6hYgoPoYahNbPkTxRZAiAVGIkeek8mYjqPu/oJqgfvl7ExlvV0BLxYIoE0EXcSTA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":44730,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbyNBbCRA9TVsSAnZWagAAAYwP/2aLBiMj9H0lHfPJEq5A\nQIt0KHW/Sq+vfoO310yXHkmeTB2IR1SUQQsbmj6Sbykc+ZaFZvd+IaCQkLwU\n69PMyaqjWPuCPzpyu11eup5NEzKsGqOxkMTU3NQcBQ1JgudSoek8BzXedFlg\nhz5YtjEs6fM0FvYIEVRoanRWjJ2OCTnUfB/Y0dki3IZZKPUWbJ3+3n4P2KmC\n/Q+zOmtj7lFpvXcII7Ub8pgTTIMviYskWspUlgby22zKdqlRL+aLRnorbgOa\nFJHsFynHcc/x6QbKM8CUywl+2TZlPA3PvueGUNuZc0okKcIwnVLUcxV/4ieQ\n0lxEUEaF6K7NcPrEKwgWfa2ZCRizH5I/yviy36dChXOPt2XOy95UffkGtsOY\nrXGR1Na0XMDmhjrl3cFZMW8dI9Ti3QIIMMnidDdGJcZHUEoh+353ZDn4eeAI\nZCcyQKdxmUxn6BbBxBWwXDdHyA36SuomdZRndICw+uUXjCxmR3ZLn8lUIvco\n09qXtZ2H/+7HbXaW3Kb1S/x8YC9lCBuYCK56PIWLgYdph9HLMaAJ90+2IWJT\n5pfA8GAt+5aQh8rcdjKMEfpyIANtCywt7CAlRGIoltln7tY66Da7k9tzZ5lE\nixZSHkPesfq/hvKRbpKBsnws4dueSNAlLgvQWrhnuDlCVgsX2OettILZSAD0\nigJR\r\n=5EjQ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.38ef09.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --save @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.38ef09.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.38ef09.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.38ef09.0_1539887194950_0.17157224810880023","host":"s3://npm-registry-packages"}},"1.1.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.1.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.1.4","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"a234ae90643a2167082a8a7b5a599391301ff6e4","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.1.4.tgz","fileCount":13,"integrity":"sha512-maNjEGnG1xk+W8jSgCo/djI24QvtExB1sbcrlEifw76u4EhcnvYK5xosUHwU98+ox8+LIvbawngYwP5Pp2R37A==","signatures":[{"sig":"MEYCIQC47O7Qap1bQE8WCBdybDco0x445etRZTBSr256h8FNBwIhALySHLSlWNGv3Wm+trXEuKFv8RGyMhMjC4UtjB1NXC/B","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":38403,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb0I7tCRA9TVsSAnZWagAAO7kP/2qPgN5Qg/1Diz4qFOmE\nhM2xzt66HHo9wOnloFVcgHW0b89XMqs6OmEUePQav3lLg4Q28k9u0N4v5GAs\nG3idKufO8d4c5L5pGUzP9Y6H6z/z6nqdPVE5wbflQVZZIYTR81PYOSUK3jH4\nqaN3bH4ivJx99jGS4MsiMMdx8Txjia8mlmUIDnk0JuJvn0Agrhnzx5mdv65s\nhpdg7AHx+cLccvea8JeNBhQ6LKkHWayhrj7oDaO3/AuVKbgIS69tSdEfsGhT\nWbGF3m9oThoTjAl9vZhYm4NChtaP3LjRff46elzS1+U7dNpjJaHqzdRz/MtC\n93rC8LCP6U3yF1+I6Bp8ejrfwoRo4o4RCDfT+BsSCK11tzbiKtvNghyzYq6Z\n7FPBrjyrstdoxiq6xZA0qYBObSL6nRQPM10GiJuN2xHYFIriVJflNi9YKzSX\nY41/Y1z4T+scZx+OjwfHzXZ0cOEzd0SpDw51N3ixKxX/nFo8YGqxxIHWDSaR\nt7spIqvHfX3l6kb+E02HK1txuLKgAe+/EbzPahgQwvgGHvTFJPfeW8It54ev\nnAsobP3hLtwJzDXK7/u9GYRMrkI0J6w2Loaa33MuIyaPb0sCiDE5HHK5vZTw\nVwfOOud6sm4RDH540lcao37UvVhAJXXjmNCvqq2D8K0EbNjEnxB/FDI4jiB4\n/+xy\r\n=xXeS\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.1.4.tgz","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is no longer supported.  Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"1.2.1","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.1.4_1540394732575_0.187472519377343","host":"s3://npm-registry-packages"}},"2.0.0-rdpp-feat-4918.d87e6a.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-rdpp-feat-4918.d87e6a.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.d87e6a.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"f148edb3600e859756f3641a72aa91bd9071efab","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-rdpp-feat-4918.d87e6a.0.tgz","fileCount":21,"integrity":"sha512-sJaR/EZwX1O4kcaKUK6XiKTWmo/sEq6zy/IsHSGqMDbpyp5Vq1gMYg/+lptZC/J4PGi2Qs3ZR/mUKIFQ4oeGaQ==","signatures":[{"sig":"MEUCIQDuh1YJnXdPanjoaPguUZdjy9PfDee+LSOMt+EMVOB4igIgA73kCBe7Hsvxazb3xU31borf0KaowVCrV5RWoSZLqig=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":44737,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb6rpSCRA9TVsSAnZWagAAJBwP/iemw4nik9HHaXGk2Oae\n2YZvK4BZcgbgokuzlegxn7iJSAKcox0+A08Vls0OPGB3YUnpMrNU4/Qqeijc\nkNKLTzVtkn4zciNam1/DPKDfPlQzdQ5QRyx7maxyPosOsJ3UkG3L37QmsjL1\nCebhBvtJmTaPCPxnb7jUt+6/mVacaugLU6lqHqTKIRvo6a+mzzzeI+KOdnz5\nXNRdCIJpTy/rhhW6xqTbCsiAPMvuI4VSIQIs2mG1RpDqj3YccszFofeatSis\nHA01y6dm006sAtZW4Uu66bhHsTw0xB5o8ibzM+VSMsSCQsMk4yCzgyWRd2ZN\nECipLsimYwqhv2TNBQTXVHs35AtBLYi7R0ULiwqJiLh0mdZ1sARrma7TAU6W\n4c9IWfhjbAqqAtDQFtZkh0URF21tbDza+iQFvioGVYC2ej66KcYyAnOBnG8F\nKCLadMP+14vxQF440WZJmXz7PTnLXDx+N2krCa6ZNL9/bwOcwDeegDoZkBdA\nFwu4Zc4tGBEG2BW0Xvf4rbFgQIpPZcyVBsiTgvyWhPYlQ0NlMtR6iYdSmosO\nOvn9X7ULVJaQdmxw10MTRHTTVEGSfhyNRttEs/S+dUAFYVZE8LdFyvbPbDff\nb84x3v5+nQrv3RHC71cSiFWV2lHpfBxqOAF/NdYE8u0ccp3PtZ+v79QKihTQ\nWub3\r\n=L1oA\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-rdpp-feat-4918.d87e6a.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-rdpp-feat-4918.d87e6a.0","nodehandler-utils":"4.0.0-rdpp-feat-4918.d87e6a.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-rdpp-feat-4918.d87e6a.0_1542109777249_0.9443310565205862","host":"s3://npm-registry-packages"}},"1.1.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.1.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.1.5","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"93b30c08014dee87b1ca13707fa9bb3d2351cc25","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.1.5.tgz","fileCount":13,"integrity":"sha512-J2l2KKLa7xekugH+zWeZmTc9hjZnQ+/mfdSfq7SxbXgSsPN1eZw2080xPmZ+kDJorJu7TbccEzKo3HGi2BC6CQ==","signatures":[{"sig":"MEYCIQD8APPhzQBR9VEatWNU6qBJQyrVaUkuI25ISQ/GUR2IJQIhAJBkip2WVJnaUKsibyILsBmQgmW1C0R6BQgZzJZrBQEl","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":38410,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb6rquCRA9TVsSAnZWagAAS8MP/3WQc+snBJ/CTKjoUBH5\nxZ8y5RbIy672HMcugCd9kc/2TQP0LT+ANPcN+2xxpmSJ/2lbVlcTGssAw7j5\nKvgd4QI2bPQr7WY0lnJphPjLDuahjtZz9UCByL8AXDFXpsueioTDi39IUuuZ\nENFT+HVgYmKqQaWMwc5s0UJ+wfVWLrp7n5zUtZlOPkcEzPpZOFQW/+EWBnza\nxBbYN6wtF28UDpCYf31LWDo5A9M4j5tz8l/chs27XhtSx8ahkRvghmZDdQJH\niJbKVn9Pv4GJ6CYQO/+S29pMriRQci7/2wdgatS3iHbcxSD6P/dAwMTHW5S3\nDf0Vge3/uZvyr/nWFEEXd8KCJu1dL/n3npnV2mayCD8g+7nWiTL5OOwUgrjK\n0Fe3PewuBEV4XfoCZbHS9eqrXxLHnABVVGw8ss0l3eVO8+DGcwTt48ToQKYq\nO6CShVtNKcTjN69yvNTCoLIOuWAHqIDpo4Tf1u1VYXkw78r+tRKCIy9XqqSj\nxub2diyyaZYhnvhYauDCQgLCXHhVqh2J5f+hTi/D+MK3csk18YhteIj5zh9n\nJsA+TNxKGHqm10HCUKx/WNW8qcmHsxqXpP5PnMBzvD5nLLyD6ZwDjSpA2c9N\nr0hVgiYA70Y3kJRHMHWNuQqV0kBzUvXimioPBdU1/AkRWqCp4Ia9IFApIG8M\nzjmf\r\n=lP71\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.1.5.tgz","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"1.2.1","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.1.5_1542109870241_0.588955024132211","host":"s3://npm-registry-packages"}},"2.0.0-swagger-v2-preview.5f3d96.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-swagger-v2-preview.5f3d96.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.5f3d96.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"35f0a440960b2b04156b2e533eeec22d2029e80e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-swagger-v2-preview.5f3d96.0.tgz","fileCount":21,"integrity":"sha512-PaCe54QWPLnMv/F/OA/yYW4xPeOEOk9l3N5g7y9Uh/NuGznAOBYBGMCXiV4nU4OuFZjaMN5JaGzte5vG3fMYQw==","signatures":[{"sig":"MEUCIEAtwMvZGFaz6p0pCqV5ysMONZUkkCyHYAQ33LaOt0DgAiEAtRfwrk7tgHQbATzCBQmFFH6G4IYE5459Rd37JHMQY+8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":44749,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb7CWXCRA9TVsSAnZWagAAzHMP+gObq8WsCTA33R4ljFdk\nqhzjBwrl7qtAAy/XGCdl3/a9UjLltvKKCJnO8Vm96+jMwINPcTkaqk4PxyBv\nhYZXKLXr3XZ5x3inVE0sNUszkSPDIOS7cM1yXlH97PX3EuSIMvPwZKJ9Zwtc\nBMnipsyJdjzVY8PYE3fcGde57DkW5hGLVQrAm53ebzC/BsozTCtoHSKnLV6i\n5gHtq35c1mVpn80xhmfZtZY20iK6rLqqF0kIUTVy19Xb73CkBHHQua5APPrX\nytkBCSFY9XpaYwnTaJO7CCv8Wyvmd1pvmr9QNh2l3F1eI1mV3cBjZUYkd100\n170VWOl6n33CbAdSe3tPQMcFqq3iPqlFkJCnB4wmLb6SirAZfpNPM9dlPXP2\n+jRlTC2zGN3RHjLWegvZCKUpqWbVNCzbPUg54WWIwbgSWbT3vxgk0g2+h/VS\nWaqOexuNmeCPabeIkq/LplUkgyf+RWK7NGmPhV0zGAZi8J0pANWIb/3PkIfI\nXds4vZ/h/RQwJGO3x34TseElvvuhIKw0oGVPCoUYeI/bgPIf8rIDSvJj1uZ9\n/mH+luWCV+nLD89skdJ2aTY9OOILFmjVNS6cURjaC1XSxrqD5Amh8Q6V2E8q\nLXEOfplO7dNhQnD+JaSU6xGpydAE5bMuieTApjwg5MKXyvkxVZ6dqB/yvS9d\nmbay\r\n=3W/X\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.5f3d96.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Internal optimizations and replace superagent with request for http communication\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-swagger-v2-preview.5f3d96.0","nodehandler-utils":"4.0.0-swagger-v2-preview.5f3d96.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-swagger-v2-preview.5f3d96.0_1542202775272_0.4591224469628936","host":"s3://npm-registry-packages"}},"2.0.0-swagger-v2-preview.44b0ee.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-swagger-v2-preview.44b0ee.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.44b0ee.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"abbcd6076c7f58fc304c67c0b5d08181d226c727","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-swagger-v2-preview.44b0ee.0.tgz","fileCount":21,"integrity":"sha512-kJq+V/hZYFenECetJ22qSrpZ4SeTPaI+3nv3WDiiCotTZeWFZNDg9jlk9bNnVMq2BmlpypJt9yqpnz0W5/9jXg==","signatures":[{"sig":"MEQCIHP63XJroX8J85EeMtAIMJdYoYR777jI+8OPK2cm79mHAiAVAfwOs0SRsmDv0TFx/Kk4Hzpb3Ou2jTole1GwrFCNXw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":44786,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb7EX3CRA9TVsSAnZWagAAZa0P/0nDaRCrHPVwYGqS1YEH\nrADe1tACLSk25SM8rdOVPCjydvE+0BZqWbPsm91Fb/6ExOrt0sn8GvPOoIco\nSnPRzHMqXOUS4GfKYxW9Av0tOC0JPzSQ5bRtNa1YA8Nv31lq6grRsNsrSPkB\ntgS+HEb2tLxDi+hcd0caWGUXrhOgxy6YCmLSlwnGvuRg9oTkg4+6HVgngHuz\nsP89HoTaCE2pSG/HjbNq3gcQ9JP7sDKeDjhMAoHnsDhpaW+RYoQOuXmaZa2L\nF5avcmjAK3+GoxF1xHYrUa/5graDY28B4050LPqy4qMsqx6L8YKG0vkLYh0e\n+XCrWgcKcUQTO15EGHRwplO8GnuXTxCzjeXfBzpF8MzJlMUY3CYElzqiUIQn\ne55OPIXWJq8sQHFUdKiWnubDRddsxt6SuZHtifcSIA937B5I5LwvRzY4DrhB\nYu7XK9U+tZU/g8kYL+/s18xGhP2Wv2q0A6t3J8LSi4V8/vAG23GwBRUmff5m\n3JA5fXTLbzCFBHVYJC6AbcU3qO4WrZDJkCGxe4hkRN5ZjPlPS+8hSU9DBesG\nEZdL/UYuuxLptlS3OwZN6EKKRiQaE69EywnnaFGGK8dDWP40eQFzM4DvOIdl\nbMfdatIFAr394fgcZxdR93vFA7Lyia/Wyh5rgWUkzFvhB7EUPSOmN8VIETZO\ncHCD\r\n=JEov\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.44b0ee.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Internal optimizations.\n- #4919: Replacement of `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-swagger-v2-preview.44b0ee.0","nodehandler-utils":"4.0.0-swagger-v2-preview.44b0ee.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-swagger-v2-preview.44b0ee.0_1542211062400_0.41805562495833604","host":"s3://npm-registry-packages"}},"2.0.0-swagger-v2-preview.927944.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-swagger-v2-preview.927944.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.927944.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"5c1d8c1df5fb744c80a414032f31f6e61585398c","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-swagger-v2-preview.927944.0.tgz","fileCount":21,"integrity":"sha512-ED6jmnQA8eNO2qroqunXlvOhoWd9emKD5nDnZqMxvYOmRMVOonHBSdePRcNLsX5qieD+qJpL/+K1/y8c5aQd1A==","signatures":[{"sig":"MEUCIF1VjsYcsgOnENF+6T1Tbc9sQelDB269iI+rjugYzgJoAiEAi5ResRxiSCkXEdokhF+63Jfnn5P2MKrkiGRBBgMAXv0=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":44673,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb7EkxCRA9TVsSAnZWagAAERYP+wZy5Hxcz3fAxONnbUoX\noSC9RpMdGPdAzvD5PUx+tSIS969CIwkEsxFgoa6AH6g/eWdtnkjWVmPOULoi\n0CjpoRZ4LPuJPQnMzJ0lSHRxZZgX0UXhexJzqgWxVy6xN8yDKlb/64cO1aFf\nNl/hMHzHbCeNLjCFwjegFueuS+tMJbH6Br9JYDrgh/y7mDbhvJDaV7NCJjxd\ngmWID9fPa4w91stAV5AdfrSQmIZD5Fi+iTphqZ46xKJV/zDnvfx3HtKzV5Kr\niZKFZu68V2/cuBeLZ5QZWGLAMUdd5+VIlqLw/h7AuV7HKDUV0YXE7Ql5Mtt4\nHSKXrC8a7zlKxa63YH7PYCC0/B7JonRV6A9u8bcWEeB/MRpWCL8F335b7dqh\nZT+5b8mJSFO+mBAO/cfhsID+oMWeBrSau+GiajD3MzJXQdgSkDJDawp6eHL4\nfmYmvtvqB/gZIT3AQk5TIEWZzEIZb/DpBqM2LTtKS04vLDtpf3yBnBKJzb8+\nWjWsvziN3liAOsqHp35yJf2oD0kbjyhlZgZ/y7RXeIsYfJhaD4Ld/c7xZg9t\nOD+MfJVhkI9XmLayDC6WdjtmmiGs5DLTvxGek5+NbjsHYvyargsZWYV6T58F\njE1Y4oE0h2UBOErY+j4yldAead05ZmOX2z3FL3+TqPtGadvx09sQANCdpk5i\nKwaB\r\n=Ngwt\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.927944.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Internal optimizations.\n- #4919: Replacement of `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 81","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"unreleased version","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-swagger-v2-preview.927944.0","nodehandler-utils":"4.0.0-swagger-v2-preview.927944.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-swagger-v2-preview.927944.0_1542211889389_0.46940759799102416","host":"s3://npm-registry-packages"}},"2.0.0-swagger-v2-preview.d782ae.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-swagger-v2-preview.d782ae.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.d782ae.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"98d650327415b804de4387a30733d5fb5fb20506","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-swagger-v2-preview.d782ae.0.tgz","fileCount":20,"integrity":"sha512-X8iL6ycdWVyYIKtOqEw6PuiI7sDgksftw9ZEb8mICvNsGDsCe8KtkN3Sp/nce9E6NRa0cWTFPqauHOG/g6Q+ug==","signatures":[{"sig":"MEUCIQDLokpOEByKvn2TF/y9gXv1riT69NTkNFFPlclRXL9bTgIgRRFmXXuVQqhTNf6GC68lDwN6Kxd1yBr0ZyAorrTVeRA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":47700,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb9+KxCRA9TVsSAnZWagAA8o0P/ju/JRynD8pA2MC4JDLE\nUIh6edWNjHL0cHEPbgPK8U6ohHmMqRDyDpgvWEbCUF70djJOPrpeUfauGRre\n5TAELftr6HREYw+6bLSvtBodlzgIWFv5SRbUXSYOJ1AmHyQde0M0ujCyPdV2\nzbKzeECsz52TXUeNl5D8cMhgQHO0NT3wsTB6MmT8vxDTehvPz+Wf2pMg6ZMU\nRRg7ueRXpvhCSPddekGGBDjtPWHafwhQ2wjEmVoOrvY0nm3kSyDhHGDTX1Kl\n1NpqJqGmhR52gEoKad9l8+NjP8H/0wLOig85Ct3pn7ETVf8eQGAx2N/VdHE+\n2D45xu8bv8RwWbWkeqk57yA0RRPi1otdETbre6ZYmKRAYJ9Gf5mQ6li+kTC9\ni8PlnBgWq4uqz6ZvYJSXtnnAn6c6yZ3IA0neLew1ZSO5QyGDhwVvvsf8g9dM\n+0wZkO4OU0bGnDygAR+UM8e0mkRFux83lXPowUtQd/ZhB8RmOgFEH0hr3nwJ\n15vH3qZ9YMtnG8/eA5zR3HJvKKMZ8uGXpm0wsWu+2uCm05Mnp+XSZSwaoNHr\n/1rY04ZcBKrGnGoMF9ETJEEuEVxt9NFqLXwdlagJiUbvTIccY6t4lrOD+XMM\nI+2ibnQO2ZUaj5snLNpwggd+rVQQbUVCyoRQ+tYOO3FZL5JxrGzGz92n2+la\nOMNW\r\n=g9WE\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.d782ae.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Internal optimizations.\n- #4919: Replacement of `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is deprecated due to outdated version. Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-swagger-v2-preview.d782ae.0","nodehandler-utils":"4.0.0-swagger-v2-preview.d782ae.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-admin":"^1.4.9","@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-swagger-v2-preview.d782ae.0_1542972080957_0.14496261221301032","host":"s3://npm-registry-packages"}},"2.0.0-swagger-v2-preview.09c711.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-swagger-v2-preview.09c711.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.09c711.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"d4fc1391c7ff8012c47ef01cc00c15da8501c2e3","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-swagger-v2-preview.09c711.0.tgz","fileCount":20,"integrity":"sha512-Dy3QVoU+5H9OaTazjMWTEfHp8H8QgkgGCKMxR4v45R9BSisHeboYWK58kg6h9slQwM26+j6h89cjagyfsnmzJw==","signatures":[{"sig":"MEUCIQDoJdqJhKJpFJEUTj1ZfIMvnA9qnNgf8nk61Z7keYUYRgIgen7tz+XJLxhwtcG2rxW1BxBTOAbvLgLbxpwXBNzHBxc=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":47700,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb9/cmCRA9TVsSAnZWagAAuFUP+wS8O3RDXFf5QBK5ANxZ\nHCzuAxmehr4LTJ3qzIkGOgult7Q+TuHeqTqvT+gwEggH6vqhtSRRePfygiHM\nM3oKE1/RWof6+Ey9fKnazbZMyaDJYvD5hCtPg0YdbOqUbyNKVnBr/vLkvpB5\n5lh6194mqXNncNwuPYKOsSEnrSoSA0z3GykbMe0qW/o6iOn590kZdCM3AhCK\nf5Sq1+Wzmy7noNUNr8qN28bJ4G/Cjoo2bkB8B2wSrqvDpXoNpAsEFtod3eF3\nuMqJKipN9i/rg0+q3NNyFTMOtTf0CRUQmxYsFZMPuXZkbUAsSOfRQEvFTMJK\n3433J2HRlE3RJWJsPx81JKFjwzgdzvUBxh7J7NK9ymBzZ7Ri+K2wWLKVzhYV\n/BDKX8L0elcR91+ctaxUiIP5SkI+aev+0ZSwewdUEstXy5PWc8oUH8Umjs/S\n/oXovZ8xn6/J8yNTKZD5ywZYZS6lwPgeTBWI0t10+YHrvvwoo2CCWJP61BJa\n2dz8qQL39d4ak2DgtTdmRpW438z1eE4q9yRyqYJWxX8UiF3JgSML9HglCYaf\naTx3NqRAId2zUWcOU+ft5M4rPhmlgWR0xOmgBcpHwHp2TeuTQYCB5Fe4mOGI\n2OK44avv+S//ur5eb05H4iOZYqxKK/x67rgpguzIOLVWNo4allWQnXpoO4dm\nHpAg\r\n=8Q0g\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.09c711.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Internal optimizations.\n- #4919: Replacement of `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #4918: Breaking Change: Minimum supported version of API Builder is now 4.2.1, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is deprecated due to outdated version. Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-swagger-v2-preview.09c711.0","nodehandler-utils":"4.0.0-swagger-v2-preview.09c711.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-admin":"^1.4.9","@axway/api-builder-runtime":"^4.2.18"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-swagger-v2-preview.09c711.0_1542977317911_0.64780293158647","host":"s3://npm-registry-packages"}},"2.0.0-swagger-v2-preview.b8c6ff.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-swagger-v2-preview.b8c6ff.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.b8c6ff.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"15603bc11c388054c5fbcaf393ca6da3953a7305","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-swagger-v2-preview.b8c6ff.0.tgz","fileCount":20,"integrity":"sha512-ocQxy6lieKxV7ehdRgiKFliLbHoCssXEJvyi0rYAar56hMnA0UwZpfXabE3DAvDvkyPkAyrtUk4S02jWIWZ4Aw==","signatures":[{"sig":"MEQCIExerlK9NFl8Pw/tOFXUliVJyx6QEaEdQvIZMuMJsX4NAiBtzeM55DY6qTNCsqQ0xQkYN8stAUTX6GT/9MfUA7VMOQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":47718,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb+BebCRA9TVsSAnZWagAA4mQP/iEGgGGsQd3TIqTsx4Ro\nBUqTI9hpvu1MDA81imk0nRUnn530sldCyG7lanAZ9lvGfNnH8MMrY2BV7/Q5\nkhlZkhplMnCFIzJVd69Z0XUpHRuCxBimWTp/KF9D0CiZBCQEeIa9LhwDhCv6\ndqH4alypTcVtc4wRATdaG+2YaD70jzAxdP4zOlCuXAKhbbYhOhhOzRA0U3d2\nyen2QHg3uLRDlZ17w6aJAx+ZjzQNY9KqwoMwmv7jYg0jND99VG66DRi756Se\n+z0arFrxAXdUhIc+GVdz8e8v6BqmO9RLL6iFmVfRIdct/q6D1HyY0GvrETpE\ny9gGuZuzIyQGRNH1XXfCdpMVQimVmGZ8GDZaJ8fV5mfe/1KgV5hI6wVyfW0D\nZhibTTUjYOxFabm/3tFgPwIZao76UV6nnY8iWXKJximYi/6TsMK1/gsxOVdT\nVEEAotHo3EA1MNsZgRFwiTCLcmZcO8a7sG49AwqXagUPjw65GllrDO5LacWe\n1WByEUedn1OY29Z2tKuWbbbFtO0bh1L4EJbQV9dR2nITGSmzt8AjvSip6QvO\n8jkifya1/IW6JKvd/UNwURdqGZ6WY3VU9I6gqQxQpSHbWYhkSzb8OzPl26zd\nEE+5/W0WIh3Iz1Iu2vFhG5zaoK9nmqzeHJ1JYIRnWH/dpGLQGgkxB3SnwYmG\nOqwc\r\n=N/p4\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.b8c6ff.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0-swagger-v2-preview​​​​​​​\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Internal optimizations.\n- #4919: Replacement of `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #5242: Breaking Change: Minimum supported version of API Builder is now Istanbul, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","deprecated":"This version is deprecated due to outdated version. Please upgrade to the latest version.","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-swagger-v2-preview.b8c6ff.0","nodehandler-utils":"4.0.0-swagger-v2-preview.b8c6ff.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.4.20"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-swagger-v2-preview.b8c6ff.0_1542985626706_0.670163554288606","host":"s3://npm-registry-packages"}},"1.1.6":{"name":"@axway/api-builder-plugin-fn-swagger","version":"1.1.6","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@1.1.6","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"d056115982cef969bbfe9207c2ebd315533a6e76","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-1.1.6.tgz","fileCount":13,"integrity":"sha512-u/V3zgL/MQFdnHfP+CxV66X9GHQm+CQT4dWjC7uHrJnYy3ejtm6lbP0DJEC+kVWugCt0rgT8hTtJZ3ZWTNkADQ==","signatures":[{"sig":"MEUCIHUvG+4bFGM4U3dErKpxeW61DWzjBnT4Qtch5vUoqEQsAiEAofZM0B7/bgUvYNUFvYxYQLOdK7wPL74ySk66rxTB7U8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":38331,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb++p6CRA9TVsSAnZWagAAJdMP/19hez5bWE4mUgIWhZI4\n9W81foIXILbU2r962wAn9NKShgPB+PExToAiFM5g49AcZgUzWhpgOw/BagjB\njbvWfG00Mclawi4QHhlPqS5hKh+xr/BAwYv+ruhSVm3aPX0Oy2oxNeetosCS\nl2NA8tNe+J+JdrMhadl4SNkSTkJk0Lg+AwIiX2bqhPRYkzF2b90JsH1cPVFn\nhN5tyfJ/2gu9WVg/Yw+B7CCe7Mt3Gra0uSacGQXbNE3uTRiJEWlV7R16tjR6\nJC2scLVPSO6+lX0SOO08UQ80/XcT8RsXu8hGZXS2gvBnREdZEOW/mECYSTy9\nf91y6+2pRy9sYELv1OzZWNZ1MEc0yRqs7ffppa1td8RAbaplNtttTZXrHgWj\nXJ7HO/PUNXFWcnFFp9n+RXBOIdJT8y9XJGs7npRHXsXIXvJK/gbYSI2xeVlL\nQo4MHtB7d+x7oIG7G2KhV7pfNPEeqKsrF4tdxyPv2IWAUSmLBzhoM/AidAv0\ny/r6O6PILTul1i+q74eMk3ajDEmEX2aSZ6pAQ3Aet0LQ47XkS+GX4s/P33hw\ndBaaglHCIxRjXXTFEJils9i+7ZYCdGgBtp4bWHbNcvwrP9aWJRIwtuEXfUjX\nZqUi5kDlgXqH6EV2GVy6mRFAXzVKmXxvA+IyIc51l8YKbZvp+/l57rOumkud\nM7WT\r\n=tIsW\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@1.1.6.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## How to configure the plugin?\n\nCurrently the configuration is related with configuring the authentication and endpoint URI to successfully communicate with the service.\n\n### Configure Authentication\n\nDepending on the auth type we need different set of parameters to be specified.\n\n#### Basic Authentication\n\nFor basic authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-username'**_|basic authentication type requires to provide username|\n|_**'x-vendor-openapi-password'**_|basic authentication type requires to provide password|\n\n\n#### API Key Authentication\n\nFor api key authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-key'**_|apiKey authentication type requires to provide key|\n\n\n#### OAuth Authentication\n\nFor oAuth authentication the following parameters should be provided:\n\n| __Config params__    | __Description__|\n|-------------------|-------------------|\n|_**'x-vendor-openapi-token'**_|OAuth authentication type requires to provide token|\n\n\n##### Optional Parameters Related with Authentication\n\n_**'x-vendor-openapi-authtype'**_ - This parameter is optional and only needed when the authentication mechanism for the service is ambiguous. Possible values are - __basic__, __apiKey__ or __oauth2__.\n\nIf this parameter is omitted the application will detect your parameters provided to decide about the authentication strategy that must be applied. If you provide username and password basic authentication will be applied, if you provide apiKey - api key authentication will be applied, if you provide token - oauth2 authentication will be applied.\n\n\n### Configure Endpoint URI\n_**'x-vendor-openapi-uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table bellow:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'x-vendor-openapi-uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'x-vendor-openapi-uri.host'**_|server name|\n|_**'x-vendor-openapi-uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'x-vendor-openapi-uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* If the user does not configure authentication in accordance to what is described in the swagger file the service may fail to authenticate against the service.\n* Only one authentication mechanism can be used for all the paths described in the swagger file for the service\n* File upload and download are currently not supported\n* #5235: When an error occurs while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document.\n\n## Changes\n\n#### 1.1.4\n- #5297: @axway/requester indiscriminately adding body\n  Previously, an empty body was added to every request even if the request did not set a body. This caused issues with some third-party services which rejected the requests. Now, the body is only added to the request if it has been explicitly set.\n\n#### 1.1.1\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.1.0\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections.\nNow, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha --exit --colors ./test/*_test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 90 --functions 90 --statements 90 --branches 82","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.12.0","dependencies":{"chalk":"2.4.1","capitalize":"^1.0.0","@axway/requester":"1.2.1","nodehandler-utils":"^3.0.11"},"_hasShrinkwrap":false,"readmeFilename":"README.md","peerDependencies":{"@axway/api-builder-runtime":"^4.0.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_1.1.6_1543236218058_0.4007726633628954","host":"s3://npm-registry-packages"}},"2.0.0-swagger-v2-preview.7862b0.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0-swagger-v2-preview.7862b0.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.7862b0.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"a9524768e9712607e66bb3920cdf7aa927381e64","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0-swagger-v2-preview.7862b0.0.tgz","fileCount":20,"integrity":"sha512-9Xq04It+f2k4X73WWE64zW72IudF2MwSdnSOGecy5j5XYVPapegDudpUaKuETDZwnk3XlxAg0GqYog7uL3oo7g==","signatures":[{"sig":"MEYCIQC4Bdswo7nBLc70VuHPaXF8hyabkSuh+NrCPafiZx62wwIhAO+NtmvWNwkhsQWzHXoq/Vn/VN7tjL15gr2rKcMTRXfq","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":47815,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb/W8OCRA9TVsSAnZWagAAJKgQAKIqgowLwKs1Xxtp52r2\npFHQUOP2nMn9PJKH2CXF501ZWTRVDdIBaWE87dSGu1UDoho8BSSzSnrhBruU\nb3WIeKkv7JZetDkag52ehiNWe/GN8I9lvYJjKdMIreDBISqH/TWNe1kj6wnx\nhKDoSBMfGF/OU7vdrrNlc58qNjjn7thAEhF6KY34KlsAKpVsobUz4EYmv2/q\nzCjHJwoad05hPFMVLC6cWKBG5mkByDZyJmH1NnauT1pJfc0z0uXNBdRcQXqK\nF513pptim9EafF75Oq4L+nW84c+1R0XctPgN4bLBv34DSu7beFSeaukkS+mm\nE85AMPYco7IotaavzBGHHWHPxaeCQiG4VHSZ4hLrHa3UnkTSaXjvsjxYA0WH\nfDjEWDyBbjvcWxxHco/V0AULhJaLlUpcN7Lr+ptU/ugkJTPiVwcWFgSy7RKi\nchhBfr5LNVbaTFfKXxnXjHCdHMzKL2MRofDRMI3e7dlX2q6sehpIo6w/9GUM\nF5meQyYsNhEr90fKdWBueYn4BCqa5jGXASdG+9XSZYtGBPDZkBawSQW0NJDp\nbm16xq6LPOI+I6GbyjVMiJ4WX32Xchw07z3gNOIDdbr8A8ZsmvbyG0ZUgTRd\nJBzLvalb+OfWPBFZYdrsWdScImNknY3+zudL+/QnrBrvHiHWqjAZWW1zAZqD\nLQym\r\n=rguH\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0-swagger-v2-preview.7862b0.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* If there are invalid swaggers among your files in the `./swagger` folder the plugin will fail to load and no flow-nodes will be created\n* Paths that deals with file upload download are currently not supported\n* Global security schemes will be ignored when parameters are calculated when a request is performed.\n\n## Changes\n\n#### 2.0.0-swagger-v2-preview​​​​​​​\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Internal optimizations.\n- #4919: Replacement of `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n\n\n- #5242: Breaking Change: Minimum supported version of API Builder is now Istanbul, which supports flow-nodes that advertise authentication parameters. The `enableAuthorizationInFlows` flag must be enabled to make use of this feature.\n\n#### 1.1.1\n- #5177: Previously, swagger plugin was taking specific configurations for all the available services in swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.13.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0-swagger-v2-preview.7862b0.0","nodehandler-utils":"4.0.0-swagger-v2-preview.7862b0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.4.20"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0-swagger-v2-preview.7862b0.0_1543335693225_0.506932738270681","host":"s3://npm-registry-packages"}},"2.0.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"258baf3fec0b6039baa3485cc3a88396fad8e1a3","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.0.tgz","fileCount":20,"integrity":"sha512-RNG/wkr0PCmZgsHyKr25hUAKl72PJ1W/XVtbts1uyei8DDbvGMxGtELNgo8Np/YUFZc8R6A2+wrAYiQg3pG8eQ==","signatures":[{"sig":"MEQCICs0mWUOuW75+fydVUCPwGs3vnfkvhZWxrqqkvjo+sFiAiB8xau/O4zYnY/zLWKjUFSz1kRZiaM3xdO771gy5tnocg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":49246,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcClqbCRA9TVsSAnZWagAAeOsQAJd5jllGbLAfeCN++SCX\n1f5Xl+ZrUDP9BMKTKvKfBARYd4JO622L5SyMxmHJhQw72SSPD5Ki0fVVdKue\nmR+j2gRlG6tUnjwK/YDkzC2OQCMH4XmaCP4r/eYEXQ07bdEMgJBlUrBkIG9c\nJTSBdlKEyVsfqbgVrRc37siWrC3GFQAtuVWMn8yb2xmncN/SQdna3e9wyIcf\npC5iUF+AXvG2Ukd1mrs1ngqvoM/pbivnFjpnNlxGXnx4YSEN0U85fpqqlobn\n8vRaC8QCHBzBwu1pYExviwHZlNYVu2CM63ukufLv03skasNBNMzON9zvZFWt\n+BA/pgQAH/bLXyOhwnROR96FeSgHX2DNvu2B9Wgnlki4BKluNcIEI9koN3SY\ndG0Eih6dnANll1iSI5ZQAY6/+jBylvJ1ZR7KGgc52y8r6WeULoD+SVuHbQ8z\njuAWHazfvYZlG+PMHhNqolZny2MMLHE5oamDLcLfCI4seaFrHGIWKBFQKO0A\nYSY055TGTzPY4YGBXlya8/1wgw3WOFf5Yf7hZJr6gEZx7yY+3ul8CK12x63r\nBP1l41htiR/LNb0nxGT4l+jWxFdlq+dEpUyVbK5jwwh2hRn42HSlnn17kIbv\nu/Hi3LWnsrs/vtfE/qMOeswV86ORPI2j6pRLl0Utd6XOxvrPrTsi2+Nvn3Yd\nlO4w\r\n=+ba6\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.14.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.4.20"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.0_1544182427000_0.4094284452680155","host":"s3://npm-registry-packages"}},"2.0.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"58597f0b9472c18580ac754e0a616422242e64c5","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.1.tgz","fileCount":20,"integrity":"sha512-uOkLwZ7q7BUmC2uCGtZRwbMX5I0Jnp0+5SOHJHA6phHwywRCQXWFyUntvz5WwXRuTYX4z0vuUAzOKdrBYVUPPg==","signatures":[{"sig":"MEUCIAcXUyZOP4tvCztEk9F0ZujHqV0JKfxQm4KEvUEbv5giAiEA/9vWlzA5D9BsM8txJ4T4Euvy7EKNyARJLjaD49Ypf5w=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":49332,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcCncSCRA9TVsSAnZWagAADVIQAJD8EKjDaoiE+rI8Etss\nTpntGKRAcgzl39uVkCPPsLRWJwWFkEm0wZbCJucTTD4AUWpTrAAELMtn/MEJ\nLF5NMPMh/nrSR1iT6fnKN87Ax91ixSl4AcrZKBl6DJ/zwAsHT3PWUW0ZV/GZ\nroARk2FhGQDi73guEbIIS4g2rMVt0PX2PKnhlMVkPIn10qgxNSuHJRFaTshU\nwCljFUxk6W42HcQ157vhQaVV436qcOLB3TsdxmaFSubxLNofqVl/UzEDSJEt\nEvs7X/6notDXAx0cEdula/4ogz2yDg6BVKeXwgXaxNFomcQ34LTKeMFPakf+\nCX0OZq5O9tz9qR+X0oz/odnbG2HmCLkDZUVJrvntYUz4FtnPOHmNvac0EFp1\nkhUioFyhTIlouJ6lcAtgpsdbuvqZFVxuNcJf1e8jVyKT6FOl+9OCAV4VZVMk\n4ejGpTYQ12NRA2Qjh5thoxZINc4TWcRqmsVXnMWqvbDFsWBTOY2ApZngcAeZ\nK/g3IVCO2CzmylzCxf6xVNIZOD5RXGyLM29i8zt/IQwZb5CBZLTCQHu40yTT\nqLmDeuG+xC5DPPo9/QWShpzqd4W1d/fujbwwD1ddG3pHxlTQ+w4esBJZyFG7\n8Ak71rAIDLZQZaDVocSiD8a4fs5gTb2v0VAT3QimcuPezpVm+Gw64zdoqhkJ\n07il\r\n=f3pC\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.1.tgz","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.14.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.1"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.4.20"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.1_1544189713526_0.7253189627256984","host":"s3://npm-registry-packages"}},"2.0.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.2","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"d5e7d71f01ff12bcd553e2418fb1c71b055b3693","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.2.tgz","fileCount":20,"integrity":"sha512-uCTzPvUhHBLh4XP7Ao4uL0xVcdT3IOOYYugvZaacWjy73Q5z+GY7aGY0T2lmNY56reAwP/QBY+Jhd6BaRiRB5g==","signatures":[{"sig":"MEYCIQDai9i0uUtgVF/HPzuuD6sxxx1RFiAfotOHCap2vtMl7QIhAMSf6YFKQDSOhtZXmH2e7pexxY12yqZ2NS4MAJ4JaGSC","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":49368,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcD+/GCRA9TVsSAnZWagAAmy4P/1sgcJB6Q5ia7Fj6ZHs5\nh0PhdVhax4raISH68nwWSRkzlJ0J0Yj6qUKyqWPjYjP4xIiPXUSBJ8EUIDce\nIfVB8QPeGncizxBI3MhfCFIglv49jEK8nnSezs5B/bCtnRW6L88IYKllosv4\n4QIB9Em3U5ty2erD2U6gUeFH88fzG9SHt0fR5KUqIopkP0JIVn/sUmRyf4nT\nU31aDTM8mJrVAtHjplzqyTkS/p64qNZJ9F63t5Cl0np9eEniDsxCv1zKxbud\nDZ7odUoYiKR0miAGxq2WZytkaK9D28RaIEgxsEYkes8NTd2/Qlrp6ewpqj1v\n+4oHnlK5bhzlH2C2RpkNQthfZtIn1nBh+FvgAgIputl9ZEYnzdc+13biW4YP\nvfc4v4epaMvs7RWHEPsS0ev4Yk87QF+yrmX7bXhm2lTdsNtfEoEj1mA3jMm0\nN1f/TkXLi9vknGva1YebtNpPvQfgMdtdHnMMDM/pPuiZ8wIKhov2t9Yu20iM\nas5RJEomDpROMUw7pg9fBE4FW59uB2wIV4ZyV6aJ3tfslGLxjFaQ8F72arfP\nWqA7ZD4Q44Q25FyS4wq4aZTEOohZ7fF41jTd3HQIOsT1wePobGs74E38cuz5\nxU06erOPopssLtJ+nYQm+JT34GAKTbvOKoIY5AJx2h4utE1js9KbwVkc0Gah\nDZy4\r\n=D2sA\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.2.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload download are currently not supported\n\n## Changes\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.14.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.2_1544548293750_0.12371101747388424","host":"s3://npm-registry-packages"}},"2.0.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.3","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"7f991cf2d924c117cffc78b2a823e75e03adeb30","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.3.tgz","fileCount":20,"integrity":"sha512-fDIbuA2PqeC9csd5w1LDRHRqg5rAxLbuWN91bOIW9pekRHMXqfEsDZhAsF3V9XMjYkrjOg3CsDokjZos/iBQ4Q==","signatures":[{"sig":"MEUCIHSN2F2st3HwVa3knmZsmXigt4dY8aZofqZJkMFr4Ul8AiEA2pzxw08EvxwlbYIxujhk5eH2nhszu9wg/a7a3qnsAMA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":49578,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcEjqICRA9TVsSAnZWagAAvuYP/jd/F1m2lblUu3L2QBjv\nEi67MCMY8cl85CVe8UPhxCQzpA8BY4OsMZp0K347HvYefnPxrjSTpc9TuO8v\n8AzEnt5oZCEfSCajZ3+hs4q/3hH1c+5idnkK3ADTnLSU8mOsXOrZJQmuPjoo\niEZSJpOGAaXjoUwi3GgH+rrEdGMIxWZU/M2D57d9gsQOOyjXH/0IklzEIVGZ\ny+HrVnmXBlkA3yncaBDAFWryh9eztovxs+M7M1T1Rxkwfzl6cCn+FJFccr8x\nqbDugsjQzjeP7DjsWNnqIKKhJPrlAWwBcBxAAeYVPIDhcyREzxt6FRF6MLkU\nZ77ZNPT4DQP7fwcJt1tWeE7bs7d946qU2rgA5PLvR4d10tYp2Ar3LM80KdFX\nBfc7DUjtmVZAVChBUw0j8MmsO8QHSJ9hxTRRDCUiWnmC3WPs6ncpyrU/8dgY\njp8sJCtRSUl2i0UZdEMPVSlU/QbuGpQEaiHoZuUIF9hRVZSAfuyxG/feFBY9\nI8ipWBEkc4flJC2Cl4h9TdPrL7x8l1LNzb0TqhIFfEa3pbVHj7raOF9fKy+c\n2mNILpTUrtx0YIx/FVUKmPw+PNC+XnKyMWlj0Ze3liju4TD+RvEjrSmQcBw8\n6jpaC4eGQDOZiZ64lXJDUXqZDLDZnV4T42YDRnge0PEkGdAhR3vrem75hEHC\n5cYG\r\n=++KV\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.3.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.14.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.3_1544698503934_0.4398727227101471","host":"s3://npm-registry-packages"}},"2.0.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.4","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"69535631a1a1eaa6bae33fe8690a081314d24766","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.4.tgz","fileCount":20,"integrity":"sha512-H3260aungq9/PI4JbKHgFTOp5fmE5L0V4Zid8XvwFkI08AAfcUgp3kDB8u8xSeRULdeuyIfdoMqOrLPDYWi8Bw==","signatures":[{"sig":"MEQCIB5wIwmlMentaiWxp0o5W9gdwJi/Ouusk1RlRtRiopaMAiB4P127RBM1TjNYYAg8PFtCVGeNc34oPQxrBBJGUtxvrA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":49978,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcE8IlCRA9TVsSAnZWagAA6dkQAKLbwmGVNRtmnTIHn0bm\nnxhPXvuTkeZ2QgDAN8BJaYxPZ3rsvdarVZKhATrFs2jgDgC50pt4CEct4upZ\nJn7svPH47t+dPKK2IQrbYUXfQyNLbSorxF8K62WERvgy/FQddE+75DzCERox\n2sGyFW2wsdcpy1+2rl7cnI+gpggl/eEQVqr6kRQLkou5o15sLShWpO/feS6+\n5fqCjjm9ljFsTPU0qbRblMJtSFVaXCWcYVOPWnj5JKcvcOFC37kEHUQ0Zh+7\nznRV4Vt5t7ew/cItObYEGc5o3AT3EDiV+L6gwL63rogELq0DhUd5ZHL+W2Om\nta7pOrGozbo7SZoEZX5jmQIt8aa0JO3WZpTsY2ZBJDVlv4My4rqG7HjQbZLU\nyNxbJ0nTsVpLmEr1zV+JvqrSQyII1ptt9/h0lGObajhiNfnDO/AZBWTW7mVF\n5RICRpxKwSx+wZhWjHSOJGPgui2RIJXGEQ/fCT4Zvvi2Zj0BCorcd1As3RMn\ny8qHlY+7fxZgcOTS1JfP87rYqPEnE3nwTPxm0UekgAalNinfm5LPK9/CsqDb\nhZZoSfLsSenW/Yr2xBjrmGwtyPrcSnZ1KhgjIN2Gcka4QWfrChK7I55hPhz/\nTc993T4hYspRwmpaQ9MD+VY5zdCFteQ3wJ/m8cYRzGgPNKsgSl8CBUhdQ0ZD\nGejN\r\n=ttgV\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.4.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe service configuration is handled in a configuration file generated by the plugin on install, using the parameters below.\n\n### Configure Endpoint URI\n_**'uri'**_ - if this parameter is set the module takes it into account to override the predefined endpoint url. One could specify either the port, host, protocol, or base path as descibed in the table below:\n\n| __Config params__            | __Description__|\n|------------------------------|-------------------|\n|_**'uri.protocol'**_|application protocol to use, e.g. either http, or https|\n|_**'uri.host'**_|server name|\n|_**'uri.port'**_|specifies the port on which the host system listens for requests. This parameter is optional. The default one will be set, depends on the protocol.|\n|_**'uri.basePath'**_|basePath is the path to the API|\n\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.14.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.4_1544798756795_0.9734455299686429","host":"s3://npm-registry-packages"}},"2.0.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.0.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.0.5","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"8b986d5fa792824c89dce9c7dccf48aea0febe01","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.0.5.tgz","fileCount":20,"integrity":"sha512-+sWZm/6P+imyGfTQRoQQtRNURfvHezpN9TOXjSysAWcypkcaXJ15zlSuTmrkIn24tdeal99XB0JqiUleN3Gfpg==","signatures":[{"sig":"MEUCIQC1q6NqHB9cCJFeYp4c4SzC0QrUQfhMUUG+VWxsHyr/3QIgYVgvCmnMRAGXj6dGMUXVOOWp5BJMhU6teYyTnLPzYHk=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50720,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcE+MaCRA9TVsSAnZWagAAfqEQAJWKikX77jvEvnE7qg7A\n+KMvaQVSvd4qJjTxtKsZy7xp2OmOAD50ERlQegX3ai3/oJiY1ThoEroecj33\nEIOyY1kTG3keeY+LPjEJZuxAhbd8SYEqpZSML4WFXErDFyMLbXpJAxX/bWwo\nnr6Jr8epXRPjohCnvOhSqxZnogk+foMRfx23t3LfaUNScd2sQmx1ntkVnacN\nHBXl68v80/fHUWoib/87LV3jcS4hkBzKX9zC1nseOQhkorhCP3GHCUfm6OVH\nEUBM7EXzUmAjq/CKpFEjGT4GZBlbyHNoZJO7rBK4GQkFf2XigIBo+j7HsMrS\nyhRcHT/mJj5qU8XoQmeNdNJmgmjWhk9Lv4MdipVnYQ+I1kPMt+5cqJu7VzLp\nK5mpkGOmAPVuqfQfdD9tehjSrX0Mkk9vx8v6UvVpJeJLcNKuXM8Aude5eotg\nBc2mjTLGdSnVNeDGcHXHWynOJo75YO0xlUqmaglckdRnvEP7fOZxcVZeB7h9\nlW4/zu+LOvoMUkX2XAqUYpShlUPsNAWEjWTf4zcE+zJgCU629kiGVoPz/zp5\n10dJO5ENK5VCV5NGWgzyIbbhQA1Q7SbDbDRULQH5nVzvyQXU7+W4rQ6CXbjh\n48dXruxEeFfGiK5KuzC2nUCFgi/RqqGsnfYT9iHubUSfX2fUnHLgjdPp0Xi4\nWfFs\r\n=hqFa\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.0.5.tgz","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.14.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.1"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.0.5_1544807193269_0.3528446600144257","host":"s3://npm-registry-packages"}},"2.1.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.1.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.1.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"6e74028461adb29237e90f6a8beb24bb385632f0","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.1.1.tgz","fileCount":20,"integrity":"sha512-gJ9ZKM8FjaXKK59DTmyiWSNHEewjYhP1+HOkgsH7DEUY8ThkHWGOiBH6IEUmp/HMXG4Etw9VbVOCxS4fx6ubXA==","signatures":[{"sig":"MEYCIQDjZL9DFV7cTcPuCFusKUYqoeVcpIK6PlrpTA56dhaonAIhAKZDQABa6psd0f6BLAKzEifwdE/w3Vb/c1OQqZOBGhh7","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":51348,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcKix+CRA9TVsSAnZWagAAyq4QAIjn9cZBnmNmdokLELmF\ntpHbePFbw09kvBCefSB9PTOCh0UqvHiYuAIrPBu1AYZAnGNdcPEcb6dH/AbN\nHpDewXdvss+t+H1X5u8xTFrG65Zjn3DGPfdtfHIAUOhT1p+0v6+R+pLI7lZL\nwnQSzKMmRUTG8qnBBanOzVjuAOSYrd1PDMTADVyjLlySqQ9STX8VXJgiJzG/\nfh6fdUkOH6cWmBVkWLwYj1gUGiPwaS4TqMkVGIVRdw3CjNKwNWd2e4VU3AII\nr7F2yxKUPgvs1gFBnIkiwMm7+/+OnZiuZ55qj/PF25LhPYeyKOvShbKgZAd0\nxLi7wA4yK/Oh6pnK2vwrFPv969n2ljdail1V7aTCmHAYzYHsd6L9YZBc9QgM\nqRM28se5NsDPezGbT1MQzQH/E2J6hqBhCbGXIC/NoJioFwqfi3OZReVP2Dea\nDvoFc7jrZqYQ+nbhzuV/Li6Jr3SH/F7bviH63ai0MnJ3Org7KK8JIljNvzKf\ngTwrNplAeQGZNDMcWwrIWwisXzku6I9BfuqTBgBwb4h88+gH02c9mdBHDKGg\nL4KlIlrLgf3qPgymLQDGytPbAL5zI1bvfQufcAoIMUz7WknG913B/6MWhAqw\ncPhuQFy7yj4K/E2i+MsOmBKPOFfojhEPj8muo1EfQjPekiW1II+60DzkMUxX\nOj2J\r\n=P+gT\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.1.1.tgz","engines":{"node":">= 8.9"},"scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.1"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.1.1_1546267773790_0.8535009657116372","host":"s3://npm-registry-packages"}},"2.1.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.1.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.1.2","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"cb30f402ea81f844c2b673552cd839476c007ded","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.1.2.tgz","fileCount":20,"integrity":"sha512-npglsqUvtxK8GoYZcE6ueG5WZ4XXc9Q9ExCjTT5XEZc79ipDSMHKvHCB7MJRmFdEO8I1Miw5+6Tnxbg7gDCIWw==","signatures":[{"sig":"MEQCICAfwd5+XSIgy0xxlqbJ5G3HyU+H0TAjolUM4phhGC5xAiBNKKen7gzRVbsPAfRqIibJ8YEsrtAV45Tgycx/GswEpg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":51378,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcSyowCRA9TVsSAnZWagAA3PkP/2Z+Xs/CpKZ/+RQfVAeY\n9oyUlguIjocbqcYWHN0q1lL0qojxzw5xgnb5YDD40b6JGQzs9r5eb0qIgNFs\n6XUQmxaxAA0wm7H9pGH9OxUfRSg0msW3lXRIaVGyVgRWkxfg7u3+A5mBtgXz\nFX3QbQQ9xJvZjIlco8evrKANZfE8caqPxtstIkreriE/o5IVWGmVc8q0EQgW\nQUNti7aTDI9w7Ki/CHDssvjnfV5OGOjKQ5F94QPxSIOjLfyNwO9/2GRj6IcJ\ndNSpUR/aemfDzi1j7GYnOuDA8W1tc9qmHPNfTMUzptza+J+y9LjI1YNEPQUh\nc3Wul6QEkvDpmtGQYZTzIKZyzxX0QlwF692N/NrmFBzOPabQ1N3c0s/bpWht\nzAX5iv0cAoRz5sItqt1ExWW2X6kgo6Tff1hq0oWgSmHCmCsC6wZFNkoq99dE\nbPzX0pJm0CRAjtviObCA14QlR8vGxpbBV3oIbBNsICfj0C393wffsBMlp5zV\nDDMXZSieEV32BgWIMZgP3k6MMsnCnRO7YGBQbFr1OcQmjPvl06IhDcn6IoBM\nvrHbBOhko1rAzGYP98dyl5mOA5mpV2d5EarP0LpKoubYtnQ4L2GajXuHAeyX\nnqD4lcKAqi6PIBhvE5EN1NsOR3n20M4SyhZh4rHO18Qj3cmRh1YGhdmWIKHo\nvsAZ\r\n=50Uv\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.1.2.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"0606cfaa67a01249e643baa202faeab60e2d3f99","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.1.2_1548429871879_0.001128500945582589","host":"s3://npm-registry-packages"}},"2.1.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.1.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.1.3","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"11445caac540c77a9e2178a44578d425af9a0bc1","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.1.3.tgz","fileCount":20,"integrity":"sha512-qQk2RHiU7lBAX1NQNhxoiqpddOkJWTQYaTonFROGHSECxCQNpBLAHIo0ra+Y+Q9wsrGTxDs2y7nMLMfR5q7Hcg==","signatures":[{"sig":"MEYCIQC+5VFjl5Y0+9tXh7GtGu+rtWDXdjgcnQ/X1ZudRL+MLQIhAP8o+4uuRt/PRArAP8GvsRPupx4QJlmdQUiDgE2duub9","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":51378,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcSzgxCRA9TVsSAnZWagAAx3oQAIlrssiFFzgvG+SwrtFF\nCEnQY+0llNiVpd1cenYea1iFR6YXIJe73NY0L08dn/4vO6cbprGpnPVySc8u\niWMD+dxflQgxTb/D6K0yy/Lg/tdjAeg0Wj49R7h2gmJUoCp3Gkpdj3vsfExP\nhrzwqHvTOtAUItMTvoN76kjPtY4SE1+fZPn8k8lO2Z04OKfz5VegMJE92L71\nXUqPYKsnwBdkJ+D538uck9dbpWy2qCC06Yu9c4wVPVWCEF7A7VaSp48Ip1q1\n3P2Kvh1GY8YKeeXKgi/pu665cRfh0tmwHzCDmCLDguKzWpKi97+IfH2JDK+D\nNEbCxbcK+PcMhENTLQe/wa+y2ZkiXBjyUJCmGnsRFxjAC2axQ8sFED3bI5po\nt7p2cKawa2pX5tI41NswP7RmEdPY5/YKHV+OKtOAdeHK3TdDmEHRPWS1eEFN\nRNi499W25f53KakW082Mol7wXdx7oh5kPTqv9Q3QPQ1Cis6frPrw77CYLNW/\n0XA3Gd3t/tn2EkRyJp9wCKMU5RYWdvwoBYDGJsnP+kVw+HG4FZ6iX2DsIudV\nsn72BfU0+dxKj3rO9R/N/mCc+ezxuc/b6R8otPjjRRFmJhV0+55aumANkzOl\njVdmUPYL8usET7jVOYFuzdIhTvZyU01xgchC1mqryMp2O0iZDffZ/9ZQmHlU\nU2pj\r\n=Gx7s\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.1.3.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"4acfad047f2c6a2274d7ab9192764a4f6ccc5581","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 95 --functions 95 --statements 95 --branches 95","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.0","dependencies":{"ajv":"^5.3.0","dot":"^1.1.2","chalk":"^2.4.1","swagger-tools":"^0.10.2","swagger-parser":"^4.0.0","@axway/requester":"2.0.0","nodehandler-utils":"4.0.3"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.1.3_1548433457035_0.7923667846175821","host":"s3://npm-registry-packages"}},"2.1.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.1.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.1.4","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"13115ee87029200665a4fc5d5775e1e5119f7612","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.1.4.tgz","fileCount":18,"integrity":"sha512-jvyJVTY5DN4C+1u4qwcbk1uQYrwV6SuLTaluwywJ46PTXrFG75+nGR2SWCQTiENOQO3xVleVWHJ6vM000kbNxQ==","signatures":[{"sig":"MEQCICB4jr/NRYvs0LK3K4NA5nHzwtJO4U/xDZOSoVzoSCjVAiB2l3l5LDKtQ6dNZe31e+3r7hcVhWB8Dp9n9sHctWPqyA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":48263,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcS0BwCRA9TVsSAnZWagAAo8AP/ivU87NQoT3Yf0U5EFKs\nnTSO8uZZMZ2I3tJFLfz4Rpgattg1XJB4aIOhCw9jyJqs8LdNWL9YSyjyEqLn\nn6Zk1TF+1h7MnHaBhsk4RMafDDHK2UklMizINF9lPC+Fot5yRS9PBLFm27By\nfj82oJ051ySbuZZX5tXce771VHJ/OGV2VgdZv+Ph9QsUVd8juga3xV0dEWk7\nezqfv6M1w8J3DdY4JDSTpoEZtxJhHk21UB/GbuDN1/FTnvKxvY/4eSRFdBr2\nXH/s2TRVuqtM4ZQafWNYeHoBusuYsJdzyOlSqBczmeehijzjBspjUs6Sqi61\nSf9Cwcf/TN2L8V2+5fdQ0TI5GkbM5C5Squ1zb9wtDzde4Hjm07LSU7MvYtnd\nlcRhoF0CRzEAhz4AP3DCUrVhj5gh75wmGRmRJywemCjqvh/b+9OZu65QdttU\n++EbpHcG0TMzMdE9557IUWnms4h+mnXPOtcBWz0LqjBP4+PrzJ+sVCnzASI4\nUV8HEiGffXKP3dcPqv+z6+8KlXQG87VesHNahnXzq4TfI4h/94zhWO1LO7jb\ngKUxhWZI59q5AAVaWhAT3IOc2mBQLDou91fS/BwcJmaoo9dksrxuaBxtv748\nJ9QCEdop68nYUHsu0JOC46wsH4lNFD50Z0CXw/jXp/a2wSV6e+Lmz0e7e82u\nACe2\r\n=Yws0\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.1.4.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"43325c9eb1b6cbc2caac51108bc5dca7597b8261","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 96","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.0","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","@axway/requester":"2.0.0","nodehandler-utils":"4.0.3","@axway/openapi-utils":"1.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.1.4_1548435568281_0.23914676781428623","host":"s3://npm-registry-packages"}},"2.1.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.1.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.1.5","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"5e4855a51ad978b10f683de6a2972ed7694272ec","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.1.5.tgz","fileCount":18,"integrity":"sha512-exdJs20xxWIDxwPvScrfHMJ+haMOZ4iNiYvnH0K52QfTiH+zhbefYbO5EvTfhPosoNHyfqffz/yezMbdX8H9Ww==","signatures":[{"sig":"MEYCIQCvTqMyGUkS/OcpMpbeKEa0zWr72X0vrkZWPovULqOmYQIhAIH8vW04NQb0CsQVLj9RaXRvJ0f42+724gRrGmUJPVzs","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":48365,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcVGEQCRA9TVsSAnZWagAARKYP/1rNACjXdiJBLt5++yK/\nRpLXUztSoB5XAg67ZaxqfZEz+LMVCq/tEMDf5d+shDQEQXXWlJmLYKr6yB0g\nSh5rJWrHtvABzphQfOqc1t4/UohAMVAHHKFPqS1PNoZP4SUhSOVCmI26eMdD\nBS9gRdcX0u3lVUd26U1nradXsvM5SF5+8Dtua/CnHVmwJsYhaeiN9GjYjeh2\ny0kgloKtuoAMsMKjascf+Ufth8g5P/qqRRMPP45jbqOPdPHBsE0oNo56AvUx\nHWJYsv2FRoy6CpBofd/kfccFptbbT+HFUIc8fSxcs0m53wMMnCrlxaBe5T35\nBaPspFMY/18pl9qgxsxoH4vBUMvl5I18ny91PTpPeTlwhkc1Zq/pHoZLijL8\nUgphwcgy2W/Q58Ic7ETl79R4E7yEG0KDXBr8pnMK3A+/wBupccJ4xV84V5Pq\n4wBeU7QonCi3lNYMlt9eBoNzQNAFy/iYSlr7Q6PqZ4xdP/79U2VOJQxpE4if\nPbOc6kriopHIEyW6oHVjLOs8vBKSlD7PHTLUFyU2+mFAZHuc7uMWeNwCwa8i\n99RURd8+fp/Itl0us0TtoJDOubS7CY09kXNVCKkvJ8/w7cowCDOCD4cLQ0Lj\nEe1BenvnrK8361NvpbR9RgXGJzuLpVUzQbecXUQaddoB0VnvDT94YnfAaxlm\nEpEy\r\n=wgye\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.1.5.tgz","engines":{"node":">= 8.9"},"gitHead":"05aeb2f144d36ff807c3884b0d3f496a6928e09a","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 96","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.0","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","@axway/requester":"2.0.0","nodehandler-utils":"4.0.3","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.1.5_1549033743602_0.016605255875926206","host":"s3://npm-registry-packages"}},"2.2.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.2.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.2.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"ad1096a7d2d542383887b52b591cc2facd605bfa","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.2.0.tgz","fileCount":18,"integrity":"sha512-lt8rQrPWJaH1zAdoraaF6cCntctr9pUF5O2ftwodcucky93aEM4P2pjqKjDVEhuBaTat6JynnZgSuMPFPxeeFQ==","signatures":[{"sig":"MEYCIQCBde5jC/sGWwJsA2i6xQNBPPLe67lETCekbmKnlNfhZAIhAOr6HXoqcgiWaBWx9Y6rNBWzB+84YrlPSFRE0gqiB/eV","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50646,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcYW96CRA9TVsSAnZWagAAdo8P/0RZg5O603XDfnY1rRMS\nGk9Bwgdyk7hgKziJ0tveeXfyIrEA4vUC7WE0C7nwVOPpFSEwVa+GuaQoHnEV\nyChtnzQeJ2FgAiEedRoZJS0o+pJdoDMxuxlGXbUY54YrJibDP7n7VTLswsWQ\nPYTz6V2tpVTtxi5tnxngQNz+kKwArC9J15HV2pIHl5PRnNhUT+ne61I8xo6L\nx946z1svcJ5mmn/32Jx6Lk7KOwPq8n69tYdmyK2iOdfdfkoBNOGFlK9DKwL1\nweiDTOjgrkDPMEUH3C3VKC/2tdzr9XXlOGnZgOd50PXDIvBZJ8YpV1frwAIN\nMqATYOwpDvuAJB3B4iMC+A4dzC/wDJD+AkCj0dGlHurxN3gTfonNn4zKpKSA\nObw77oF4raYsYTBMTXF9TwkQeFolUgrUPu5KzAnUv4QVzpd3pzqfHoPKVTAx\nwlcPNNnvk8jIUitc934hJ34rpr8hiVvx52RG45PeFfHnKQwmWVNt+98GqikY\n9k2GRUVCXUa2Yog3ck7AgUgVM5PSyOLS3jFTV2VIr01o5k5ICBkGwe3xVmX+\nS5skDl0Bem28xL+iG1bYJKnzHoKx9qoCULDJariiA6hI/LRAdCwonJjO5eob\nF+WXzmZUFhc8/m5CcMzj6JNoJ+HeK96OUWvlSUOsYQ6f8UcQkJWkRedS7vbm\nE6v+\r\n=0NZ8\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.2.0.tgz","engines":{"node":">= 8.9"},"gitHead":"2d23f3e18533f32fb6e1c94dd0368717933f800e","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 96","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.0","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"2.0.0","nodehandler-utils":"4.0.3","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.2.0_1549889401628_0.2837552594102155","host":"s3://npm-registry-packages"}},"2.2.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.2.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.2.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"7b397220b9fdfd2674f965a834a1e40cc8f2e4c0","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.2.1.tgz","fileCount":18,"integrity":"sha512-oaa8y79CAVBpj6A79sDvGlLhBURGM1oN3XWnoD8KiZD/LquFG1NsXX/DeOdO/ax7zZn08bi0Ob9rUgcZliLbGg==","signatures":[{"sig":"MEUCIQDlZuP7KskiOG0EAXzs0R3yXKHNq+7GSBeduCzhE5pDbAIgbkElWEKpgDKjKa4HlCslhlK3wubpiRdqtsmv8lx1ias=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":50646,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJceRPBCRA9TVsSAnZWagAAX6oP/2zGN41b1aocwtgl/gQ9\nqKGQJzs5KCb7RMwyR8raZhvc2hwg1JeRAZNHuBzIzi3GJY5GeT7JQw4fPcFQ\ng76kvjgwBMlV2zelhslROGssXT7OL5/yO/vX8vRLXWVi7pg3t49u2zFv9tvi\nyyiWE3K2ALA4IQKiclspr05QAm7Z5GNd1NiEudrtCR9eRzS7ZNUkWnmUaTyc\ni1lK+zCcqLX7Xg09qLNwMRQVzyOcPn8n76aoXXBQD7dNGh74fdjFV/KEOeth\nGgMgM4cs0ZuDtMER/K26xW1ti28GtqRwtceyW1mxcSpNyfF1TB2zCEfolFKJ\nW6dWYIEL6F3+nCZu4KOWAgNU5vpKxUzH8qA3DB3n6FsGkaPj1/8hVVc+i9iC\nqzHZc2AvNzcjfEhLV9QyJ8ZZ7y1cxngzWWsHx2hdmJ/m06+MORvoHZaceo++\ny/r+DlFHY4sTmfc0S/k7knQaRmya7neAeNIsl/zYgXLla3M208ffHKm7hzbJ\n7m6OCB9MapYqQWrnNPdK08Q96K1CF8QLlrLNyuMHLYFQ2wdU+7mijQya9WRw\nzDZOF+JcAwNFAQrG/GI2M9lJQBjjkLkHQ4BFM7kFJ3onmSnSmDfgEWN1GVj/\nsOZcMO3DBW00GqQCX7/q9sFYhBqdl7eKOkzK8KadtmNTnzo2VKsP8YnKPeLN\nPEcm\r\n=rQwW\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.2.1.tgz","engines":{"node":">= 8.9"},"gitHead":"dba9c8ea72f903ddd4db18b645a87c1c3491804e","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 96","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.1","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"2.1.2","nodehandler-utils":"4.0.3","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.2.1_1551438784534_0.4702821094532541","host":"s3://npm-registry-packages"}},"2.3.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.3.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.3.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"2890794a1cdc00bafc73d4f446efa4bb17024000","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.3.0.tgz","fileCount":18,"integrity":"sha512-88JtqFLBur6q046I7n+yGKp69GUIAxqohczSjppXOAUmMfbc8QhTgj6boeWIviy/FoWPMZGPIS+SJCME8xOGpg==","signatures":[{"sig":"MEQCIGTrtCU/u0q4iXDuWmqKseM+c45V1RqD7PVM783sKuHNAiBg8fdv3EbfoBxp9LF9O4dGx4lfSP+Jm3R2BOc6OTO5Uw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":51707,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJciPH8CRA9TVsSAnZWagAAZDQP/2QBvzHQyIFqW3bDxENR\nFT8EMnS1eUoJ1YZy8yT9HBDnNDRFlIE3j/7tbEaB1y8/M8DHUK+2lSeYcfPU\nEGNwOrMp3NaS60P+I8hMcQYboNLdkHAu3NyGCOLPbCHUnzR7WHrlyEO5q43H\n6Gpd50PzYC+b5TNd2UZO8zXNS680itJImOKfzrza66TqdcxcLsU21AA8XtOX\n4Mm3kuv9D8ZlRw0Pt2xCBJu8d/9HcwAoMYMXLCX8Ot7ndfQxVWoCJG0ZkPN1\nVeVBN1yihdaX8Z5LuWohIcDnAcXkxVRxH/Qf0/vzj0k1H27/kcWatuPs7+2+\nbUugrjPeoqh33mZURuSR7Z4raO21ywi9MndOn04q2EtUbZBSgRNpvlzESSru\nY9OZa/Sykw/0NUhwtyncBfsi5HOhB3qb0NubiPt7+44nCTHaSmZO5nCpiIfl\nARxPHZUErbnqdzJuvQWbwgFwpCvMLZVx7uhhkdi6lVDDpYd9vV43c+EQ2BXZ\nve9zH5mWg42/SnzDwkGRx4CHzBR/zTV5G8xYI+ewpddYw2d4A0L4ClxMkxv2\nBAqP+efgTuaDfdkmI/RaXAPc2N8URezgRrT+dKPhsisCwrqz8M1YIfDG6GWg\n8wDAm4D1l0ARtQgtvQ4VqO83LAsXSZuw7YBlaVCniFDA49/Yt8VJBoBcQG/Z\n3Q3k\r\n=Rd8J\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.3.0.tgz","engines":{"node":">= 8.9"},"gitHead":"a081a7234a36cee162d99fafaa23415de60a934a","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 96","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.1","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.0.0","nodehandler-utils":"4.1.0","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.3.0_1552478715960_0.356470740479337","host":"s3://npm-registry-packages"}},"2.4.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.4.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.4.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"5e8e52f4ccef6f735cb42c9f89a608b20bef6054","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.4.0.tgz","fileCount":18,"integrity":"sha512-Jy6RqHLuH6/j+SO0SQOqoAqVsznvZC9/G2kIsknZAaxmMTjm0l/+egFKjjo6wC5X5TGZrGmvnkuzWFK9h0pdsg==","signatures":[{"sig":"MEQCIBvRpP2PCEDSLfs07ou4uC5YN2BUvH85+110HKcOD+D8AiAZewAXX3vMhWFWIoLM8ckLyQmjAO6yfBhRJHZbhpKb7Q==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":52615,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcmNw6CRA9TVsSAnZWagAAm74P/3KV+k/PeY+GIMBFbMt+\nY2D1uMvWf1s2WXQK9ZOls3GaQHxG8ciOeMz5ZG6HCKb+uayVmD++e/z2r8HL\nxeNRl3cGspco5SaB419DRBWL5ME2f8A9Wj3IstiK62+Rv1MMKRhBjsiFG6e9\n9B3bbNQfcrX0VAWNdBsY7vIjFwkMIVHRLBedrT2TL2LMT2h82TkKCShz109I\nrpTEzzbf/qBMaefMB6hlhK9IXoFPuzuxNQ0UFFMH1e8rWUKMZGPWdvjjTQn+\nMgQAe7QRRQznIz2W4SuqBWFnvXJMH0Sg/LNSjKirckOWhmsYsQfwPwjRh/CF\nTWgmB45LScBcL2JWrJcIpaOKI5ynWaLLaErASFCJjvIOqeSx8W8TRuPFvtW5\n74UMMIqyd5PPR9hJKvSUJCTYmci4Kg8SdBM+ELFo1DMewIEuVlJEF1POJLDI\n2XRCNNq+l0hBM3Rn5xvBZ9jsEWqMFpGvxSgTRrIvctjf3E41zkYWUmiSgU14\neflgas3sXBLs6zf5GZ4vU9jZmzW6TqdM+OdYOwX9QyZVY90VpCf7Dro8teOC\n9LXo2R7NV/XkKPhs4ISn/tVQqeZ1yXT0h2k69KtL/W4Tq3MqiXzzJI+2yQrI\nsqY5X1LLQ3gDY7oMKL5fVluNzIfuBleekHBq6dUp/aQSzdixvihMD3Bxo1En\n0eUP\r\n=QLZD\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.4.0.tgz","engines":{"node":">= 8.9"},"gitHead":"2ff1e13945f64c8d899bbc018b3660d8ac1f21e1","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 97","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.1","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.1.0","nodehandler-utils":"4.2.0","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.4.0_1553521721558_0.8885952612972099","host":"s3://npm-registry-packages"}},"2.4.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.4.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.4.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"e609a2eb74286e500ef799023755f9c28f29eeda","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.4.1.tgz","fileCount":18,"integrity":"sha512-96vLTvmYc3jYk+z1gwfFevsE/GDoXDBjbTeCSRIo2NccNQYPWZPo8o8hKMiNVNfaM41dPaRh+zgBSD+wXhFEQA==","signatures":[{"sig":"MEUCIQCvW9eWRNFvJ6IA3ghAYBv4PmIO8YNt/x2GZRU10EPpMAIgI2dOTzGDNkPPZPspODLWvEPWETHUeGq36hO3JjxyMVY=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":52615,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcojcTCRA9TVsSAnZWagAAHMYP/iGHnbfZxVa10/xaN//G\nSTk/0g0JBd1JS1rUt28maOULWvGc7wxjLAJvtB2gPo+R22FHsH67/XzJizJZ\nrKFvGVyC8xVYhE8tQ7Ajnuq00vhv/zjTxV6H3vRt7WeCy4Qr2oDSJDlnSL1w\nt08mYy5zsYjnkgm9P11BtIi+R36IIwC4Hyc7XtAbx9Luhmai1QRCquI88nvQ\nB5KH19RCfAvBkZ2Tm3g/gwkbLzaKIwnfbkl60x4TyI++BEj0EHvldwd6vogL\nT2KVqIL6O8SOcvHyqYSCZ2Nx9oMkKlCFqeDt079V1l7zsO295yQM89BgRoKW\ntnk8sRJpE+qJfXPETZZe72yOnwmK1tm+QyRjtgY0r2Od0FgWM8PJ60fmBBBq\nV41mh7LFJXpVOCDjSPQnBy7RICWZbWo/CFKQXnBXKdoSy5ZhqVPbRHPqhGmX\niOEVtw6X5G3F+s+hcEuvGDVFJxA/XaEYOddbEOY9aB3XJq8ZSJjKeSDNaLhY\niLvA6OI7EzdJEIAp1WSopKtTFlg+VQZRDTYuuCNxCGyxtz678Oqi2rmC7GgE\n6lJ4/4nzDN9+ff1j6HUJ3QKM1QwfafzBi5gyLCFiC2egCHS1efQyGSr4ZGhe\niMpzCcOFWk01klGporW2KivlxjybOd3CAdiO7nRXGQsRo6/DXhqP2v7qqW70\nQPrS\r\n=Os6k\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.4.1.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"ba2345a530118a123f34bc5a5be0b983fe6f8913","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 97","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.1","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.1.1","nodehandler-utils":"4.2.0","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.4.1_1554134802454_0.014724847348088543","host":"s3://npm-registry-packages"}},"2.4.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.4.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.4.2","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"1d7b248db9ab5ffed7e1759598f2b99093447c66","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.4.2.tgz","fileCount":18,"integrity":"sha512-dBB9NpqDWaMU2L103yltRkNa/R2en0MTsHucdNu2x3ICNV1XbL1roqfh+18+4++JATHnrFeny6G/eSjjOxTMVw==","signatures":[{"sig":"MEQCIFabYmpHuH+5KmvTepcAkrQ370UrrryS4TN2xmxVENSJAiAcxUMCoX7JrdEzfV2VOplqaLYkpCubnJUgwVujICBsYw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":52615,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcp4hPCRA9TVsSAnZWagAA1LwP/0UaSHWjE0i+6SavgI3P\nVPUmfwSFd+Kp3RxA1P7Y2pCdjbmLNDraEPnkVc6+JGxHAvQz4dyevOViLLgZ\n/avVkzWZ4oncPo5qWqJ5D6JT6REftuBV0PF/9hBvUFPSHZSRFPhUgVKsBdzK\nbQgoWVQrUk07rWtyiXrxlPtV8NiJahQAqYYsZAsLP1Zs6uPt1QtX72vk9zI1\nrPV+sgfXJcANOTdu78Z2m3lMyuqy3O5qZ6OyyKOxHt/9D+wAezTNGPit0qEM\nsRrzPUrwKi9U4BuTxFLJl5SvN+dnoeWY7wEXGJ+t0gwwBr94hlm5ca5XX5HP\ncO+30MXGqdoJHaO9YN/G6xQVavFrKTwTBEHlGDm1VkPyW+HApC2DkMouNgOo\nOjtE1t/oE7lZaOUuzKd5Bb0map0upYd3fhLIWTCtBVkJmyoCbgvpwtNjX7B5\nFega8aNisi2baLo666I/s4gYIvhxRxDdzutdcb0DILfMw712iMyrznFWS6TE\njRcCwE1B/84dAEmMEpJq2GXMwybfC08aWtIzIVwNfqKiKQTgZ2WhsSYK+MEd\nGFXqDyPzTn8ChC0SsuK/g/ES7gGLlv9/Ch4MbB1Xf7n82O1T8BAA5373LcLd\nJLUcA0DRU+hrALTFajFPfO3T6eJ9TEr8wD4mpDHRLEMRtVrgxF+X+49841Pm\nvlE+\r\n=pVzy\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.4.2.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"1956b0304c04c69471a9ca76fe452df48f18da48","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 97","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.1","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.1.1","nodehandler-utils":"4.2.1","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.4.2_1554483278750_0.14799612682400243","host":"s3://npm-registry-packages"}},"2.5.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.5.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.5.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"9689f381bba47a4a613b5340b2addbf3da033ec9","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.5.0.tgz","fileCount":18,"integrity":"sha512-HSLXjfD967DQq3Ty+JczKnatKhivVRMcUwRbHb9lh/6tdqR4aX+uvulhj+598lbVlSPKyX2OHhuI07Npb+BnWg==","signatures":[{"sig":"MEYCIQCFV0jdqQbOUKqzCNzjjvkQJoVndxmMxD1tu94AtUwI3QIhAJpkcsb7/ed/I6N354Lr3g7DGAoYqysM6l5Tv0CjH1oh","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":53558,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcrioCCRA9TVsSAnZWagAAOYwP/Rh2nx2oH9rU2Op+67D9\ntSaqibMJrgW27/Fd9shzFhca9+iQ8rRikxpjnr1+KZ/w1iz25JPxccxSfrgA\n/T/Na4xVF7QVde5tIsATVBO9NRf7v5NlaRJMGOqq4y/IvSHR1xv/yhVwTSgt\niN68EIKmKhCI04J2j0S8JAyG8XNHDUsz7xaH1/BgQ4GNSnCdugTYcdq6JpaL\nzPGurSB5SGie+0VKG+0GV7h0tzBhQd5p3SXXNAkEsZ1CMCzy/R27v8jthP1R\nPg0fDP7tQ0bJKjI5NrR0DLmE+GXpO/Pq1N+yw8kAe5NS/4upOvxR/uKveIkd\nPX4QrjIvTEmFDBSegckzqH2jAvfeSbMtGoVLzITV38qIvIyqndynRxv6mpMO\nJkrC05lII+JfBjNhnmhFSF5HvEinPIrCkdFvHxv34xzfavJoxtaVyqFVjb3c\nfP8EaEvoeJIJ1c9DG/ZXW29U84eGyi8uf073SUkIRiG0ILDFPXIxV+hwaW8q\nBMNM5pkSLQ1z3Iq70xNTUl1mInoOqw4hykoOfqbtaiaWdYDpvHMiEVx+3Uzm\nNHd4mU/YnrXO1428JhppBIgYWJJv+Tvu6QXPFVVTPpq1kwimy9Q3AsBkuFoU\nyHMkHUKtfAF5srSqCHuXLl5E5kkBWev6CbFWmll10nyMvSHYYhvXv17PXQ0E\nEe0h\r\n=hKz7\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.5.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"0059e24ed14028f8ca26ba39eb122e12f2362987","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 97","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.1","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.0","nodehandler-utils":"4.3.0","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.5.0_1554917889208_0.297383705157245","host":"s3://npm-registry-packages"}},"2.5.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.5.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.5.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"f4641c712d018e3e493c71b43e7e43b4d1cc43f7","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.5.1.tgz","fileCount":18,"integrity":"sha512-5WBnzCnYpVX4jOLFccwh7Mw2q2ypR6DNike3OqA6F3Mqbxq573dLDe0sjRh7baSLyYks1+lrRwYxP4qL2a9ekQ==","signatures":[{"sig":"MEUCIGwqYQ1FwJzozOWhxcCtwSQozcXRH0JBP7LyZSN8tm98AiEAqx8fsWaU8md/6/6GWEYenp42HVfbTemguUL/wluZCrI=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":54090,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcr3YbCRA9TVsSAnZWagAA4ZIP/1+zL+IEiMsQ8e4cWl+w\ndI1vY8sLijr84ParGXSmvI7J+nBoirwIfBYn8ZnDvaWj+8ORd9kcGmAsM39e\nHJxv1M/xcowBzdJff6XoXSrzZU22A4sPG+oBZz9qupUVU84QEfjgx+jO57OI\nu3sp5On0A7AAf4tpH2cp7E8bnKmr4VWQw9UGVill8AB+PP+D+hjLD5emhmx8\nfb+j81PN0vwGBsKp/1WLZUHuYySceDJdnB7EccgqN2onHL/wEvMdJ5RsoI8f\nFYCcPxh9mN8uE/nm4KJNqWOzXvLr6xA8gSVPUdNK1HRqExvErZCTMlsFPXJM\nmE9kYGg2hRB5D9D79y9T7zOeJaz5/oouo2UNDDq87YZ6fshHrrdwO3zBW0nY\n0BE1AjAoiU3KY9KjrakDWUA+385ru8FgTKH9BQfeSyo6apk9tgarmrMpC8FS\nMCMjhJysPTl7PWeM6g8gKQ1NX17ZjB02qWBYpqP/hETQLKiNtCpjuzCaw0pT\nXQaw3PtUysv2EVebyK8gUrFhfdf4SjJT3pOVsfvDR6ipPzVRfGW0vUvOYqwj\n3o5+wTjreu1k77xi/h/rrKjXYvN1rZe0wOKL8ZWEp8HodsQCxuIKZMhsysFm\nonzpIAaqZN35n5hbkRnwqJvNEfUCe7YBKEiiDw/A3kyPJF8LTBXT21GdV3C0\nkQpc\r\n=7qD+\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.5.1.tgz","engines":{"node":">= 8.9"},"gitHead":"36ece3fb354ba5e372edcf5cea866635745d6b45","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 97","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.15.1","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.1","nodehandler-utils":"4.3.1","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.5.1_1555002906875_0.9542218428021398","host":"s3://npm-registry-packages"}},"2.6.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"757dab19af075a68a763e1bff85d302bba60177f","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.0.tgz","fileCount":18,"integrity":"sha512-GfA6KEmf33p0GvVECwfcdCVyrtxuXjt9RGnrjtFkVx/oNi+RgEiQs+MTXSbYGRIMovbN5Q0taAo17FyHEkYVEg==","signatures":[{"sig":"MEQCID7H+u4+isXEo77wvelmFbxl0o47k5KFvqg/ztfGy3+OAiAUfJbDdiygPsvNjap6J8I9SM+ct60kpkZk4R9jFxXn2A==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":54227,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcwJ/xCRA9TVsSAnZWagAAmVMP/2oOWFPSyum4wu0v5Op4\naISaUHSMSTtP2a3ZHyJq+g7hK9nFdvBvFYZQdvfQffZahTWYhD1DDlMSuoAU\npvDsVZAly8KZUhXzdeE7HtbMhN3xCNP8wktRsiYwijrVA5nGAVPxjPxjIq6+\nd0KXO5GrZdz0k7JwiFLNrfs1ENAqQ5dOJ0Bg3vAuj8QOYXNjTvb4iBEsz/ZH\nGrQfJURTa+I+RBOTzzBj9uFcqX7+VNKBn1BDMFVFpH2oET3PQBw4+sM0TLpm\n65YaeO2SVSqt46bsVp7UGIdQFen5qRXZNxOOsZjOym0uY7Scsi57E3GKw87f\nUipxgpN/tSfntoWaDa03efQPpl13ZscyRRAtP9nVCJJh2XOT5ItMQiHv0QKe\nsk7zk2tAEsL9z8D3U4Y4Zxn+64p1XY7KUVlgLKE+0Mu2dgJASPpZ+A3511eO\nS5NnNAhURxZGEqqMse3ty7y3p0+NK6rwwaBI6LCVGyRRh8f0wlANpeWTcpLI\nM2cA+GH88PGtNWQOZFGbLqMOUiUNBXCirUKuhXPn1NSpqMqlHyJxQ4WdBZT5\nIplVP2pSvzM2qN1JupcbiKWUZeFV4IpIwQiAiD2o050BftXMUWoriPrNwCcw\nKQtppWsbkEp34EkAYgn7Z2bQHdmbne2AFpoI/eI6lQTL1kAPApDWhXgYH/9i\nv4iu\r\n=p50M\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"bc0eddaeb3bdeb6d4250b6742b727b059b716cd4","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 97","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.1","nodehandler-utils":"4.3.2","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.0_1556127728265_0.7068755486177782","host":"s3://npm-registry-packages"}},"2.6.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"c27de87c060c837a098f2036b7079c1d13677b77","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.1.tgz","fileCount":18,"integrity":"sha512-8zwCZsl4RDGj8STXsY0uBLcLewflMGxli6rW6d+PoX/EkRF+4xhwaBCUtwbvy6f5QaNzrtHAeL+pqJRa8GxnZA==","signatures":[{"sig":"MEYCIQDYG5oosZBOpt4TAp2K407C11isw5Rhp2+stjrnGZtJewIhAJUUMTJbBitNROYXU00gcp1KYgWDUYiSKHiLwYxBAUGN","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56400,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcwWhHCRA9TVsSAnZWagAA1EAP/3WlHBDFObbP6mqOXquF\nu3t2j16UkZjXyiTS7TzqYh+X0/43qC7oMDT4C9WlCE/0uc/q4D3Nkp0QbfPd\nu6//B1yOT++1qSCuzlfcUK3qn+nirqBGSesTULLd471FmTHTO+7ggqKdyphn\n3DOsxG39U/zP/padYUYyznzcXwu6iX8G2229ckOOJmBFlxxOQimtQg40JvWl\n5soba5S+ZjrLFh7Wk/HgV5gpS1m4dB0VfkjjZyZxXnUJYT9KKxykczcrS/KL\nBJ5b74DCqYwqlW13zDKFwboM2OUu1dPKPWwyDgJHcvLf/LYNJP9En793VCjc\n3Abh7aDdNUQAgmiGgQ2Z3KDClTo8XWvQGYUYay9ExYHZUmmc+akQaH2Ax2gk\nZ4y8zl2EAwR2RIiZPFoaAHPzsYDX0u1HjoNr/vKldmRjvtdYg5VqOozA4O7e\nRADZdM5Q7vhAkNq4GTSmS4vfzzr6g0VRHFgz4+XS9YAzjdR/Q0cU4/GhjYM6\nt+tLxoB338UjgEA6KcHxP59wQp+WuacgL9yn4cMMXTgxlfw0zmffIqesvz4m\nXb1jRwY4MeoBW/I4Alkkz8neHnP3tab0Xg1piHfFMNcGjKmPJymlHu7zPOpa\nZgcWEge9lMpO/8BDqbtCyurZQbr0CXggmkHYVJklqv7LoC6w7kQ2kynuVMwR\nmP5q\r\n=8TNi\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.1.tgz","engines":{"node":">= 8.9"},"gitHead":"877c5299b5977f5bf77e3eceee049b1cd72008a8","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js ./test/utils/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 97","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"dot":"^1.1.2","chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.1","nodehandler-utils":"4.3.3","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.1_1556179015131_0.1998480951684687","host":"s3://npm-registry-packages"}},"2.6.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.2","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"dist":{"shasum":"a90336773de14fa225d66cedbc4c38d4a3393009","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.2.tgz","fileCount":18,"integrity":"sha512-k3+J7y24D/H9c1z9n8RS5z/cM25n1urdHVe2GkuICYmME4vnLPtrFpeO/gGyu4tDbfQu99MOMrGLlNOZPRem8g==","signatures":[{"sig":"MEUCIBif98O8rvhuF+aLEVQsWfpmk+aLpkw2i/KpEiW2jTVgAiEApP4WGpg5PaZQc28edT8bluhjfSsUbRKvkqhWtTbrZR0=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56350,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJczCi8CRA9TVsSAnZWagAA+ucQAIQzriGWOar9rtwaYfU0\nwyo8DLWtAHrXZ3cQnjeLR75Sm47kkB5te5dMVAcX+u1ViPQw3Dpi+jYPAksW\nj8kMt9UHLJ5CyzzdgbyJUj2d1cmz2yZ2HzsgS0nMHj0IX7upwyxpl6J1mTH1\nf2tvoeN22aqjFtW/DsBL6hh40rNk0LpDnYuvVeG+WRsCIt3BEG0kU/qXekxj\n8xlu1mbSWUCQSiEX3w6IupV1REEjpOJf8TTiEOssW+AtpZHmHwWzJoRxt96a\nBowijRwrY43SoDzJbUWZmH+a67WQ2+2xm9uQ7dKrCoqki5kjNfKnktHfivG8\n7vGsO2Drq6NPXMvw0T9quJTUb40ZgxzQpEYqNAsQJel186oQcaLvT5p3ar2M\n0WnXAXLr4n7a/unDwCPrHSs2E6smGdwcf0S7vhCR9YUlEFcY/UvHjYTzgQ9u\nnV3kamCp7BM5vWXXeSH6/pa99yQVBkbNUYJWU+B8VwdFGcrUd487w5VEXb91\nOLx+MHd8qTmzq2Qxz/iPT2oa3fircWLob3t1Pnz5jaiOvNrvIWZQWm95xTjn\nBKQ1Iu+NzuX8TR47l5bKmKklkLsmzwqvezzySzU2gPoN0dbRf1ODFkDL2vUo\ns2e8rISk2xsUAUOlh3fzCy7HbmIUeiyx8veqP+NOhzlG77VPoNp+LVDAlrr/\n7wN7\r\n=b15C\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.2.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"464b406181a2399aeec80b0fc35bff5cd156773e","scripts":{"test":"shx rm -rf coverage .nyc-output && cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text-summary mocha  --colors ./test/*.test.js ./test/utils/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","posttest":"nyc check-coverage --lines 100 --functions 100 --statements 100 --branches 97","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.1","nodehandler-utils":"4.3.3","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.2_1556883643260_0.42520283759001143","host":"s3://npm-registry-packages"}},"2.6.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.3","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"061f131fd03244736efa81de54f70c6d6fab3f8a","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.3.tgz","fileCount":18,"integrity":"sha512-am3dcs+QtUe94RhwnJ09h+H8wCqL8rtx3wC1OV5e/x0mlbaJB71Lquu8mnnbsMrOV6pV/imLXbzZcbJIhV/v7w==","signatures":[{"sig":"MEUCIQDx80Gm7yDh1fwhYB6z3mMedPNBDlVUKyCWbPL/zqZR8QIgTE2ZKcWxp9sfDbAExW2lqYUQeYE1eAfgUKDIq193O9k=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56292,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJc1cZHCRA9TVsSAnZWagAAReIP/3PnpHdLfnlhPVgjuxkG\n5bjw/TYmxT3i2XTRscr30xQ40nbfkRrbv/CfTjAEqJAevAb0OorZeVoVJzSq\n145FQpqEMXOKcCHyhzfyD5EEIw3wizHFjC2eW17J0z9CDW15UXwtfoHbNrg9\nwZWzQoaJEqar1Il3VB2QAWksdk6oS74L+8fX0S6cSTh5HV8WTwFcRdGgDyHF\nj6LLMPimrnuUME8vbQZaR0124NbP86g0HH/0BWXd6ZwhHOVm+6sf9WWtR39R\n15i3T/9Cr/yfvYNBrtEVWLGcR/qeD9Ue99x2w1Vi1wNmaJPOn7643k0J4/D2\nCwstlrpGs0ovRTIb9EDl0iuxHWmlUiB4jpsh8t8wt76kA9hORKYB4+gK8I63\nK2n70jO1tV4FMYJkWQwWrtRNt8pueNEjOBtQ2bGVGZ/KAwr+aA+51gd+QkrZ\n6wnz5cXU3C4CxKIh5uZSrlenbTRbXJoSz+wqx1cm7gZiwz4W8mgVNvoipMW+\nqAlFJHiSp1GbmXrPRIZtxtqVx9svfgMyaLm34D1ocmGQvG8nn6yUAjWWTvOW\n1eDLYxV8rfLoPPUNp8HyALOnCI6Oz17zjHyyPYcAykEyckRDYD/rVSOb9zuN\n38/uZYcMiGQoIXx91ICya5jWbFYo31aH/uX/82EEGritAe5zD/FeW+EbKK5J\njfBW\r\n=KGYG\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.3.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"1ab8dbf479681b58af7d05ab55f9550686cf7ab2","scripts":{"test":"nyc mocha --colors ./test/*.test.js ./test/utils/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.2","nodehandler-utils":"4.3.4","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.3_1557513798369_0.31956649568899453","host":"s3://npm-registry-packages"}},"2.6.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.4","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"6ab676ba39201648634d0836607fea41f78b7736","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.4.tgz","fileCount":18,"integrity":"sha512-AS4mrqCjIpR41BbPWA4rwtVT0rMksX3W7X5lITkCLIWvJJ4NivuGwXUN4aAnPVoqQkPjaMwW6UCGre+2EbtidQ==","signatures":[{"sig":"MEUCIQCkSvcDLP9dhRVhFHC1W8jUHls/L+HkiAyGZ8qPlLkN5gIgOi7EW8pHDfI+WjE7n9kcYsgA2vVmgQFq0u0wDD5azow=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56552,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJc2ZEtCRA9TVsSAnZWagAASvQP+QCNayj6eGhY/sLrzQop\nyRYveemsb2l8XPzCAIGKnfNodjlapL237k+6pnR4eZe12QXnNEjuZ9uWpE3C\nPNxxkQX2RyRuLVagse5r2c7RgD5A0yPVXjSlc5BGIR+un0YnRfhpDNrNfvnz\nkpi2OOr6CmLVgVk6UBxLnqe2WaxPK9DLnVop+iTAi7BJZOB0INyWipu7oa1e\nIZWDOU6TukoHESC2DogLSjalnAg6mnCR1Hpmlginm8SX/9s2b3E1I2xfkf9r\nwRVmCB0p2Zsq8HLA6Rk/R5jEQrNhHjWLfYHliztTo01eeKprzVrecorUMWA/\ny7vrC8VS2sy7k2giwbaPSXQE/0kGvp4LbF8cPjuH+ngakeNTYIe1Q8WSOdPt\nWd97/9NrEqQ6/Ohv0GaexaYMaFbz9moltWAtx6hkNLXFv2ZfYNx/zOGprrPV\n0JO10avPEb4GywcVPbTeWb18CppWtNTCgilOekWys3ExmJedNYfbLQ3jTjPP\nHf+/HHT5VXCdz+7WTZaHABJ8/cHSYJJHhNyLYGOnwTK8h97jzVPAKZROykmo\n//5sLUymY1kYPmZU7OTWDEfyVpoM+tx/ALRYwny/GULLAtxeKmr6hEVAxVgh\nEcUt1y0/vxzmcC2j3VIXYnB6HBaVDBB+0pHvVax+9blHCxMJ/sxzX7+Rv3CW\n1xAZ\r\n=7BRY\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.4.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"c62cb1347c50bc90ae0361829d5a6b3973e15044","scripts":{"test":"nyc mocha --colors ./test/*.test.js ./test/utils/*.test.js --recursive -R spec --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.2","nodehandler-utils":"4.3.4","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.4_1557762349131_0.5715754012449212","host":"s3://npm-registry-packages"}},"2.6.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.5","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"3636bb7475ecf797187ce301106a43c5ac897149","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.5.tgz","fileCount":18,"integrity":"sha512-iayOwiCmhFFshKr8nEXAMtzPbTfhE+PvwyqKtrwe4HOnt16qfB1vSHcrGSl70aGXS4FCk8HbSNKJ+pbdtrEmPQ==","signatures":[{"sig":"MEQCIEOP1Xn3fhLZqtmogSnbk1h/lQWDGyHn3T0wWUr25YlqAiA9RPf98QD4aQvF7NxsVtEJngr/0p88cpVlLXhGv5gSKg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56591,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJc3BI8CRA9TVsSAnZWagAAVXYP/A5REHavu1aMDNG2Jj0u\nZteH6YCfpaopP/kNvvCMUT118rtX6GkEzRPNnP7H1TNTK/VMem3neoMXXn0m\nYioYIjI2L6sXjo/zfGhGFg5Ammmbw8KT6GRPNqJUlBZ5P7+LPR78Agnee4jk\nyN/JybosEPI6X+dwjadnbOY6NEZ/7f/DtkYWeZ3kvqloxwRqBZzJvTjGGxQB\nALx6L1LIKbtSp+6O1QgFDhJ+vrgovpVG1P5I9e+O5p+7B9YxtPmsE7UbLFeH\nytXASIazX1ixqFs9GxL0DdSDiNMwKbOxkgvSwgDfSvImMBbruV761Pkw3ola\nXxQ43Tjp/6JF9WvT02Gnn6pAZVfr3BmXmkqzBF3Ebc9s51HiQgLo82KDEXbj\nInmuXI7RcucAwbCxy3Qp6dZ/31HutEQi9czQlqJcwCDY6IQub3qqqXOa6WDO\nkXVYYmn+GCXPCEIzwwZ26Z72pOZoqCTY0REUjjihMBEpgyjNFOTSvH8b/LhW\nUN1aXIduaE9jF0D43TFCFYw/A+q4WS39LSHxA2uOu2d1NiEVfeVP1YxGJVL/\nk2DSRrceNO05phJxTPwOGhFSYFrzlRsoXKgW7QWPm6MZjcDsGuxJ+QNJPbpY\n9VCCM7NbusKVx+DDZwI4wbAmoqo1KZlgncGiTm8nEmQXzJxPAHLPw1E0N08u\nyN1X\r\n=FP9I\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.5.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"04ab4f59b25e7b734fef0c63ee6e9b5508ba7ce9","scripts":{"test":"nyc mocha ./test/*.test.js ./test/utils/*.test.js --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.3","nodehandler-utils":"4.3.5","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.5_1557926459610_0.5641295683766869","host":"s3://npm-registry-packages"}},"2.6.6":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.6","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.6","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"2f0430374b30e202fc76200ed518c1b244d3f92c","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.6.tgz","fileCount":18,"integrity":"sha512-CyzGSCMis5ccHDJ/OvCkpcwQtPwVDZj87XDQSWu5v2HJPDO1y2IIeY6jbG9TUxjQet4htqCw3PQ3fDG1mqwRsA==","signatures":[{"sig":"MEMCHyuNjd/Rq/QFMzKgovZm+XnG2aARWbjqAu+M/G0nOhICIGWTYityKrQ+5PahWD/4UguYkNBoLTvza5OfnNrUrtcz","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56591,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJc3CBZCRA9TVsSAnZWagAANo4P/2Ewb5TTPxDNfMC/tfqA\neirbs+EeGh3uBhAzSpvOGBvyXLLKxSul//iJDr77Jzh/rQmWbASr1KV6jCiR\n54KCNiPlobPmTrtBX7JgtF+iGBYP0+8czo+4uuMbsuaqmt0PLM/tpHjjtksS\no9mB3cAVsf7B/CU7wKS/rY/0M0Btk8veBX2mC93Ho8TvpYGgOpgkuzmNImRU\n33nK27WV+r8teWlgsqsF3WK/XozhntOdKFoMn5PW+ehH8l6FlqPg10zRnTym\nha+C7VZXU6jmFlv2Oi/5XJu+3Km6pPV4H81MLOe1M/tqzhyl6ZV0eyldWCPm\nVrasWj77XFL0G/AOx7fvzSl1aqNG00WQVwDY+VxM3ESwdfJFgBECJyoXQZE0\nRgOMJ+gNMXvCzuwmGW0qPNOCjnzsJx2JRmCTzK+IUQRwz8ApXRvACXJTkcUR\ne50Wd7iNt1Gz6jPQRMQ0EgxiO4FdGx3iBL6nqAbkT6Nevtua876IDhKLWd+R\nKhtBQPnx9cYe1vEhYRUXmvIF2mIZBZXKnZcs8Kd8TLf8MxjVcihWCe5RyCg/\nt3CX//7QTbl/Jlz74zg9EcUCvLQLgJlh09n+GQOdbsyWCEyvSJy7W0IMZCgK\nVndY6DUQ49BzIveqfFljdjMTs3QbRN4Tr5g+BImYpvL06faj6EjzYupx6L1k\npOoD\r\n=K+Lm\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.6.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"6e926ec9eeedefb580722a7f7d862d8e95d8903d","scripts":{"test":"nyc mocha ./test/*.test.js ./test/utils/*.test.js --exit","build":"npm run clean && npm run build:dev && npm run check:dependencies","clean":"shx rm -rf coverage .nyc_output","test:fix":"eslint . --fix && npm test","build:dev":"npm run build:lint && npm run test","build:lint":"eslint .","check:used":"dependency-check ./package.json -i @axway/api-builder-admin","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","check:unused":"dependency-check ./package.json --unused --no-dev -i deep-equal -i @axway/api-builder-runtime -i chalk","build:lint:fix":"eslint . --fix","check:dependencies":"npm run check:used && npm run check:unused"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.3","nodehandler-utils":"4.3.6","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.6_1557930073126_0.8990463549315608","host":"s3://npm-registry-packages"}},"2.6.7":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.7","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.7","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"baa06e894f06ca1c4b28978711b25a42590e6c85","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.7.tgz","fileCount":18,"integrity":"sha512-EdcwPiSwrmxfSpqL/qp0HyqNjlGs+er4iV4U6BzDvEK+8KnIIZGXfD4PPzMA2x6shnF/x8aBDIeZN10Y1BgpwQ==","signatures":[{"sig":"MEUCIQD6FTBXEfn2j73E+A9Qt2/F1k+gIPwSrt44zMLgOLUgPQIgUGdqz3VTT+dN1iRaSaLVpK/88alVKRkMIVjrRnbBvmg=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56386,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJc5Vt6CRA9TVsSAnZWagAALPoQAIjgQVnsjvAtQXGfeQkK\nJZmeie9Tud+4JzgrxAJZQ1u9JyzrYdLhmdIUuT//hmfQODRw0g6FkE1QTnSh\nKeYfqtg116vwxlqKokZJrYsHjIsDrlVAhix+i4qQcofrduGUYqDanp8TUwGv\n/G3LWGu3YTpUFZohyrmzO6XHmasI57Cz66a+c0UmbNdm/5YgnqNSkfiG5bV5\nuE7B2lONLTSRoJI8wzAW/q1Sw3AidcYaClBi4ZRyyBs/p5DizFdmchrPhlft\nx8WoJ36TsrUpfFZc9O6t/uIFsjmP3jyqv4owMTWvjtQUt6Me8G18BGtLoBxA\nZqVTb1RCYR/3Nx27Is4/iFOXVkUaRFUM/r+ajILQ/ibrmOETb8yIeAHGY8Dd\noDHw3PzNR6x7TgWFM9UyYHI3fBDpGxEgTqEi/KaqVIfZpsJ9w9L5y5TDS/nk\n7vU1diUYzOrybDOZzXTbRLM/xDJbuoTcqDmTqcJiB3bOPRpyVLNc7l8+3gOO\n2q6vsmVj7aShD9viM3niy/abUppDM+R411KpxsItr2snlIWyOgJtACs3ume/\nVxkowqsOBXDQCUyTgClD+s5CCaSKEpR/Vtkpu8adPwI9XTzL6h62Z7JOEjop\nDH9rP9qalZRx91snUmKv7DjLZYOSrO42VxFZff9ALIehFNAVXXesHYlMS4co\nIumg\r\n=rbrZ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.7.tgz","engines":{"node":">= 8.9"},"gitHead":"efa6ee2c3beae11da58794c25cf0a8e7b32c87ee","scripts":{"test":"nyc mocha ./test/*.test.js ./test/utils/*.test.js --exit","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check -i chai -i chai-as-promised -i @axway/api-builder-admin -i simple-mock -i request"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"3.2.4","nodehandler-utils":"4.3.7","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.7_1558535033881_0.7211595244625753","host":"s3://npm-registry-packages"}},"2.6.8":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.8","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.8","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"9fea46fba9c8ffb3d5b756977a8c094f7af28204","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.8.tgz","fileCount":18,"integrity":"sha512-dPPhWzfQLHWR+uLVVXM9Nn51RlAhSUo2cgBtR4n2erfewbbEP03Vc+03PzQaGFkaStuNkY+wvGeBi9oMUp7IBw==","signatures":[{"sig":"MEYCIQCcaYX3wxQlhNCPUzsk3KyqPsfFL36dR5ZgALib+EcbEgIhANoZRKTLOGyfFcDi66ap9gekl01y2UKZE3bJx+kb5qG/","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56737,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJc+VagCRA9TVsSAnZWagAA2kAP/1u9Xb1CSLfOJgycNFpH\nUTU5nQfCzYxvZJtA8NrGRGLh8xo5P2/1bZ2TXSiraJ1YthLgyFQTeNHgy+xM\nU/8vhHRhXhcSn6lOS0Mg+aNteBc9CRqg0/eFez3kugqMyfuiaHfQ98CKeFXb\nQhXrtumlkvJWVCBQOObd9JWiuuQf4jGG9as9hYJSaQQHT9QltmzboSYzu5if\nvJ4vKThoaAOfa/JImKgdxcbav5sXefsEjgi0wPquOeSPzmhiYKDHJVGrMbl0\nISWYHOz+kVMafNhxpFhLoK7Al8E0PTCct/M3F/OarlFqYksYWDGSlPMy7/gX\nMCcQOqgam8wG8BJZWAc/MgIXlxptp/Xjv7yMbddg7Mq2P6XT1nbZpCOuPn7L\nE7B8JWMZiihwtwJIA/Z7KuumGjq3P0MejnchQT0C7sk1JElFg6CmNAXubyJh\nM+qzSJ+krWcgFvpYtGNEBtIyBWpswSos7UtiNP0/tAwo9zCsROZv4fMiVPkx\nb4SUwkX8mw25HqsYyT5wS9jtQE6T8o8gzxy04CNnBzjzHAL2o7IuhkwyQvxY\n4AynVuGL3Fic+yLARN08DV8VnvB7WOsR88CVyaaUEtza5gpdnAavn89fLZAi\ngFeyajDkvMkq37gOgSfMMsajsXGy8AZOoO93Vgs3cJpVQZRDy/DFi7vq1iiS\nYuBI\r\n=E3lo\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.8.tgz","engines":{"node":">= 8.9"},"gitHead":"4692116cf5dc0573df66c1431fde52a67b295721","scripts":{"test":"nyc mocha ./test/*.test.js ./test/utils/*.test.js --exit","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check -i chai -i chai-as-promised -i @axway/api-builder-admin -i simple-mock -i request"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.0","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"4.0.0","nodehandler-utils":"4.3.7","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.8_1559844511037_0.724536224148989","host":"s3://npm-registry-packages"}},"2.6.9":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.9","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.9","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"ivivanov-axway","email":"ivivanov@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"a27d09df212bb6d294032ce4274214cc1e0d9bd1","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.9.tgz","fileCount":18,"integrity":"sha512-YwIiYLlipf9VUeKpxmud0z1UE37WpNe+nNjeCm60Vs7HB23sWFJilC1bMPuNkFSucJv8CtLccoIpVyKqge0cOw==","signatures":[{"sig":"MEUCIQDx7jqLoUksnRt3yhou3EBR2Q1tjh8qbuqCO2LGLSUGMAIgctmzl+jhq6vUU2i2uF9o32n5Gl3Q4SJ5KYAx8Rt+BEs=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56776,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdjfj8CRA9TVsSAnZWagAALt0QAILHoUk+y0ABq4vlMEjG\nzP+RWP6wc2GkkJ0FsdlkosoTovQw1y+TLZJCly+VX2kKM297CD/rGDLPnRf4\npTV4deHc9sFZ5DmjU0TKqzWanbJXn3vj7c5yaU+niVyXKYWwYxaEYZVL+9/x\nLBWEly/drQQSg+nOEd32pkgV4ByeCm0C1+sU2lKF1TpmiX/0JDdKsiA1sZSG\n8vdSlfYFKu/WUVeo/g315V9A07rW0EeMZIKconPc+t6yWQKBzva7xkVkCWcb\n8FSJtxSCq6TYame38fUHWU1+BPrwHA2X51QDXAPPfN/lqHLwtUDAO8RIiSw3\nRRmZ9qeZPy8lHqM6NOvH8ufMQEmL0VMg8lHsAnwdIEUlYCcjOOu7U1tEnnrR\nFpMJ8uYxGwis635weSfQfZzt3tMWJn9g4GLXnZ74xolwWdm3siVNv5R9U6rY\nkdvBxYxURp0kampwQNjFUy8dreW7ELB9bvmfBfznRWbKbG1h+pHpZzGHDnlX\nGRmdcE0kAithULtRTzo7q7OZC8x32B9IBY4yUzRjhK1XecBEAh045pJD/Gof\nOUo4JuhBqLEJ9+nMAbcYUrij7POtPTrl822Nmn7mNdPdqx/jfdPxyRP8wPuP\nojnEgZcuDHsXYdVhe9Uxx6cyn3SJe/XzyR1l4+ujIZE+eF1woo61JSertwQh\nekXM\r\n=nSK5\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.9.tgz","engines":{"node":">= 8.9"},"gitHead":"743a4baacaf10fe8ba868ff98cf6a2d99dab4854","scripts":{"test":"nyc mocha ./test/*.test.js ./test/utils/*.test.js --exit","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check -i chai -i chai-as-promised -i @axway/api-builder-admin -i simple-mock -i request"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.1","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"4.0.1","nodehandler-utils":"4.3.8","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.9_1569585403987_0.6725768626748467","host":"s3://npm-registry-packages"}},"2.6.10":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.10","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.10","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"c3b53725ae5b39fb0999489943a65dc404c8b5d8","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.10.tgz","fileCount":18,"integrity":"sha512-TiB/L471J42zcRjHcgetLT0s9HhiM4TVl88YPe3HWQXKtQlcTOFYZzAAJvaDvFiktRMNDDtXi6/5dXFwMmEdlQ==","signatures":[{"sig":"MEUCIEi27zYoryeBDzHnD1fEOfCdLC/tcmf4Akqiz7ZtzTiUAiEAlCQnuXBlXssnmD2O8PluIiUaYtaqP3QxI0UOwrYjWlA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56890,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd3PoWCRA9TVsSAnZWagAAxwYQAKH+jqWHZ3w22umDXrOq\n7tsEoqwHjCDHBA1NgQ4CUg91C3PtPaPvA7KaBF80FuISv6H+vW5876N1OqLl\ngnYvyfR2dpWzW2X1nYbcg6928reIPEEY5TBgr088l5LdE7swO9Jjlp+sSsgt\niLBVLhLy/ISKy0mFv34RuReGRLLIiFLOZfwuenE+2/YLkSpRwY0Wi3V4K0w3\nt6GqWRONczoAMc9w20n5UWXlH+9UfgsdpyF+r3JPuaEU41LS25B5r1lG9AZA\neuOQVte4j2v2U9xoGhkZ6aWEmgPvR8bUN7UnOIsryinZH+vpejcIHb1eVS4O\n6ePfTokI2ZuvxXT6Zoxm3RT+QESrVx2h/XXpPZuPs7Yvfy1AAeno8SBrwG1m\n6x3HRQ8l08oxAsxH8XLtAwIgE8MbRD4CcEln4ql2pbqJn08e7MJ1DYGs+FDa\nnYFvHpuMMO75M5n0s/vnIegblDo8BNnSMAP/nx+gjbr44Rsu6w3VRKgXcKfL\n+GhUACW064zCpSuHpTv9lHPCWUTyWRnBW3ZMhDrUyDjK549qIycSdA9Kxd4b\ncaHa6SGqdDsn/L4IMe/ZrCcKjVA2x314XyzS9gqiQy8hd90j2yxBSKonQhkr\nzRX5E1OxZQaNRtDqBMohOl/+semiOBDe6Z6NTzikE6nKeO0AAzU9IezzU+cK\npsnW\r\n=wXqQ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.10.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"b7aaf85e2382f16ea1b736b7206f695864cb3784","scripts":{"test":"nyc mocha ./test/*.test.js ./test/utils/*.test.js --exit","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check -i chai -i chai-as-promised -i @axway/api-builder-admin -i simple-mock -i request"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.2","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"4.0.1","nodehandler-utils":"4.3.8","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.10_1574763029874_0.9043740328963858","host":"s3://npm-registry-packages"}},"2.6.11":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.11","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.11","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97,"per-file":false},"dist":{"shasum":"256c557f95e7da6612e31dffb8cd229c3125afa8","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.11.tgz","fileCount":18,"integrity":"sha512-DfwEGH9bsPQ0UAL2pMtDnlZ1m5+YGSVSEi/u154+cStthxnjy1FApboDtP4gBiy53WiTxM9t1KYcSP5RILwoxA==","signatures":[{"sig":"MEQCIFjwnm36Udhtlhf3SCU9B+0L7UWhgTWDeXOB1edJQleVAiB8l0Zm3vLo9K+uE9OZgFVcw+lpTCMPUmkoxBjdMnegzA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":56880,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd4PkKCRA9TVsSAnZWagAA3BQP/RofA5cTJiBg42vgifjO\nzf7RPGFDWDjK6b8fq+M1rX/8xchYputa5rBr3BPItPFBNbXm4EAG6ZK2V7AQ\nb4GU4+zDEhgGafXqEPwdjSHocBvWk1XyUkTXAX73mUSkbseGLKJj37t2bHLs\n5I7pKjEdlxQsmkyppZFiVQIszObog4by4rEv6Rf4ytT8f+QSpuSia8MT1uf8\nnBtq5KKZKyB4n+9KO6O0C10Pu4uD4AsZaZwJm3xDwIL1qNHtH9ORAahTS87V\nerY+rh1fhyAyy+yQZjeFma2N0bPlr82dOR3V9DN8bqGgjIfxYXesUCC60ePO\niBbdDNDUxlXfNVFVSSlsMs/AOz+KAEyzJWFV8h6hCt5f5SWF6XrdPAhP8DpP\nnGZkBEk/b1o0ATQBagxyfsXaubciu5TLI8xt+DRcUA78JXV2sk7yNrV0Vvlg\nSdwM5mSxZpYlPc4I2vStS9RrlOs6iBIwHNk0CirxD2X/T6cl1YTDtv0t+0Ba\n13aNjtW6YFtyRXc5YzbxFRqfawZml8/li90ZxNZQk4uEWTT6Lgi88J4/2Wha\noZUUd+LSWrWluXeNYGdMOYsnLdT3+YOjEbh+00/YpmFebEh47eu7NGFx1dwh\nYv4/bKfi24pyzjo2SrmbroRSTJVO8j/TWap/4RLCXc6ihPxiLJLeEWdKJCw6\n6Hbc\r\n=eyc7\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.11.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"98687f704ce46524c8ac2130a300e74148f33b5c","scripts":{"test":"nyc mocha ./test/*.test.js ./test/utils/*.test.js --exit","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check -i chai -i chai-as-promised -i @axway/api-builder-admin -i simple-mock -i request"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.2","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"4.0.2","nodehandler-utils":"4.3.9","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.11_1575024906045_0.32518230799582093","host":"s3://npm-registry-packages"}},"2.6.12":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.6.12","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.6.12","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"branches":97.33,"per-file":false},"dist":{"shasum":"bbc3f9af5d9819c64233bbcb05731537a8495182","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.6.12.tgz","fileCount":18,"integrity":"sha512-MOnH/a7A4ptst3d2Dd0sKoeUqzDjPTO/65FzCVsCUmi4MZHxOS83u3kMGJ/eOYycxekPyd7r6aSB98c9LX4cTQ==","signatures":[{"sig":"MEUCIBwGp2HT+7JTJf9wOEQqFUCb9kPJm7zvlM7fUdb2wUblAiEAqKOmcC32bWcwKp9PuPuGQwCIoPR4MpGgO7t2H54zao4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":57103,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd4RccCRA9TVsSAnZWagAA6IoQAJbZ/P2ym+YE+rwFlyxf\nynLQLOm4URfw8k5rdxq3cQvEm9OuN8/mOuyqyBEHbCGLa7XIcN4DX6JQgYDr\naOTAn/EChQ8yAdEguFLmJDkoRecm8dwvJKEDdENRps02eLNat4+j41pJ70UG\n5V+kVyTgtHAWaq5Tf3vdZO1/7+VURk7J8yIa/+W3EueNLfPNNxSFwwcsJ3Sz\nUdl8DU8TfKpXuqWV9nqWxIC1COQqsF4DDFdz9ZqflD8u9URQNYnOkycyqhIt\n6PQx2Y5YlLKwQKPTEMQHfB4jlpVHXBlXwvfaCDV31D/gKNz/EiDQetloyui8\nr5YPMeYTJHrOOsdCGe6BgwDiK9NtPVpQSbiXu0yDwi50Dh/qNBf8HsYIOsSv\nEfgRgM0qr77raYl0zl6tYUY4kmIKf35UlulwACaNXuLY87HxqN31fijIhamp\n/w6vPBG/0kBpcTpRvvxJPbMkNInDBWpM3D6mVgpIydAR0TjmvbkcogdupQ5w\nf8UHrNG/fHyOncNW7Gwvgkf28H5CQuc51tYQ0veHvSEvM6z/O2Dmt8/dJOc0\nOjCuXOIom2DPRpsWxOwO9ZHj2xWDS8slNpeoremPGbZ1RhgMG7lpDXiTwty3\nBpZq5YrALdUE7ZOtTlAbwV9Q5N7EMMnhlxm/mXDAIljusBDfEm3F7UanjLBg\nX3iK\r\n=XqQC\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.6.12.tgz","engines":{"node":">= 8.9"},"gitHead":"84d1d4a46f11909e17dfc654438ea869024b921c","scripts":{"test":"nyc mocha ./test/*.test.js ./test/utils/*.test.js --exit","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk --colors ./test/*.test.js ./test/utils/*.test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check -i chai -i chai-as-promised -i @axway/api-builder-admin -i simple-mock -i request"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.4.1","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.16.2","dependencies":{"chalk":"^2.4.1","js-yaml":"^3.12.1","@axway/requester":"4.0.3","nodehandler-utils":"4.3.10","@axway/openapi-utils":"^1.0.2"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1","mock-require":"^3.0.2"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.6.12_1575032603952_0.9704208149268978","host":"s3://npm-registry-packages"}},"2.7.0-rdpp-6187.528e39.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.0-rdpp-6187.528e39.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.0-rdpp-6187.528e39.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"e8109d31949be438129d39f767405f7c0bae2e09","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.0-rdpp-6187.528e39.0.tgz","fileCount":5,"integrity":"sha512-pmpXRYlQBRuCOyJDkk7O3+JzuyHjHIOetVbjMOIPs5W5ErVJPF/mHyN8lUuQpXDNbIWoSWJNrFtsMAFXVqh/Yw==","signatures":[{"sig":"MEQCIF9Y8RfdpA3V3XVwIHu97OpRLPOkd2y8ZNOTaXwkDN99AiBJDI4w8KSclSu8JlPVk4f+RMzciXZgA/Rbi3ZJC+lCDQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":18675,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeRuE5CRA9TVsSAnZWagAAGjMP/1uITClo6VADe3qP1Ihq\nizSDl932uojpIz2MYXYSHSq7yrsZEmLzbG7qOvsspq7L4E4jrrVnrZeMal0O\nNjLU9rHVb9p/cThFK60DyR6VSiQZI5T78BjKfQHh9hUVpmBrLfXs3Hq3u1S2\netfZdlqYDx9jAi1Q5B7Ln0Xo44tdqcSE6Ei5RfpMMB6VH80j/ubyA8Xg3knm\nh3vv0YMT8yNXq386lY4vFLWpQryEuCMonWQEDj7HXcSFhYrfi2dG0+YXnQkq\nVAgFIRBHVVS0XY5cOm6ZRS1ZiKTHYjZoIuoxcZMfvJqnITlnijE1aj4Kf9vF\nsRicCLfKHureMIT3GyzQxxL2dEVPwUPfhmsy3owFwMAEW3TLT0BYWSv+x1UI\npBfrSToPWI2bZQc8cB4YKJHodaf4Ql4KTfQqgi2MCc0gB/iV7ylPBDfnibni\nqPH34X9wVzRHc26a668Ywq5Tl8lJJv/0y+U+2QBFAZu16/U3wKA44BO0fDhB\nHZ2Xw1B07H2InJNJRLm4hcjFIJFi1GGRSdgcP+uqI1uSyBx47e8+s4++n0KZ\n/lLXM8cX2nA4IzG5cB83CgE/NvHlWsdcgZBIyM6Z4CzSjSjAq4VpdwmBO+pK\nlUDPlKvGTd+fJwwT77WU1gpiwJODAp0E+2u5Cyyp8lJF42iFvywtZEfxd++m\nn3je\r\n=ayIZ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:api-builder-plugin-fn-swagger-2.7.0-rdpp-6187.528e39.0.tgz","engines":{"node":">= 8.9"},"gitHead":"528e3923aaa372b456af0fbf9526cf03cc62c18d","scripts":{"test":"mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.12.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"12.13.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"0.0.1-rdpp-6187.528e39.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.0-rdpp-6187.528e39.0_1581703480640_0.08825588533212203","host":"s3://npm-registry-packages"}},"2.7.0-rdpp-6228.8dbc60.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.0-rdpp-6228.8dbc60.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.0-rdpp-6228.8dbc60.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"1686f30110657df1712872259afbd2f97ad15bb0","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.0-rdpp-6228.8dbc60.0.tgz","fileCount":5,"integrity":"sha512-q5eZ/uFKEEFHWJVPdhnxNwtXqprNvzplSr7pUiHhVUuHwf51PUNkpXj6EBI1bqYU1PIQ34XBQjroHhBhufaKEw==","signatures":[{"sig":"MEQCIGO8zmkdEHJbs+OOoc0f0LnxLhLt8OnUdK7yjCMxX310AiB6PX24x62v51S2nKP9xFaQvGQnwFZXk2a+omUYgvg93w==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":19871,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeWSWBCRA9TVsSAnZWagAAgXUP/i1D2IBKrAsCjORMpfXt\nHKmZj7UOvjQKQq0ByeKPnMFneq8x0g+8Z/mt0ORuYYyDbEJbzPKLsC7xtLY1\nUUKUKvF1bzTrBWfmwU+y8bSFanr28dASSshaiH1Z/sCoeNcWTDDWdn/sRUC5\n9o+rMSrBRyBnbuUXJNZFY7wR5Pw//vv+mynTeV5FTb9IrmoTByJbkn6TxFve\nhxFpm/AyP0/dVu7AM5uDRex6mCn9TJL9eW/FFp2BWQvrnMks1ziy1Rtmlhlw\nTchVksxt+4aOw24YOy5hPDGCFcI1FCRlV0ydWYGGFWjAwXO3ta7LYP6aMiZG\nMQuttP4h8DfVYwgwEmW8TQi+KEBZRgxq1zYfxEBwHKlpOtswyobqPBMpzY3Y\ncweb6oP4sw0lm5Y8LS7WRVAMIBSRmyCNd5S8J/2BLHCaRk7mA9fbTm3jcYpn\nE4/Vjuy2D6lcq6aRqGwow+JFjaQ/7I9hT23ZhYKSbli7WyFhClqykYe25ixw\nS7PxM2+IWZhPjthDXLueiLx30WSzoJkNGFZeH5ZGxjRBIgSXEC+84yCBzmKx\nVPoC0Tp91pFrZQfELv3y8QWeVGq3F714CHbgYFxLrfTRAkNguC7WTYJwUgZR\nTCIXspIMhsDLQlho8WFvmAQfPqnCMRVh2ZiSRzQ3TDyQNs2tJpgZ5sFjC9A7\n1DpL\r\n=OSLG\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:C:/Users/omega/Downloads/New folder/api-builder-plugin-fn-swagger-2.7.0-rdpp-6228.8dbc60.0.tgz","engines":{"node":">= 8.9"},"gitHead":"8dbc60e176e6ef75a89e4c83fc59749c23abad99","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.12.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"12.13.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"0.0.1-rdpp-6228.8dbc60.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.0-rdpp-6228.8dbc60.0_1582900608622_0.2849273805696739","host":"s3://npm-registry-packages"}},"2.7.0-rdpp-6269.fcdbdf.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.0-rdpp-6269.fcdbdf.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.0-rdpp-6269.fcdbdf.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"674531071403ff370785f0166c8258665a5820ae","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.0-rdpp-6269.fcdbdf.0.tgz","fileCount":5,"integrity":"sha512-GxQeF6UXtIbjjqqr6Qgwqg0poJrCR2JMVRs+0a5aDJO2f3xnwhnTyckzxV9Pz2TNZV+42hcMb40s4KWVU5mwDg==","signatures":[{"sig":"MEUCIQCDYzhVTTCKC0rz+scMtw3AqbsR2RdAswkgImGTDxsbpQIgdZLq72wZodMR8+GuB/wlsRlwfU1daJ6yeEwB+HM4Dd8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":20648,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJea72bCRA9TVsSAnZWagAAICUP/Rue5bcF3GYlM73irc+9\noxYrs40hpFl1MjwyLAEwNpYuw2ZUv8Wfdup6QBc0QsFi691zsB4PxSx93DKI\nZKcoEE4ya16SupovmVR6tbVUf7cEWXHlLCO/EP+MBZcYUFVbrPfr5Z6rX83+\n67vds8S6yzeQ4vxSjonkYLYxTeJYepmPCgskBKKfe0XoxpOWLowLNh7ZDriJ\nuj6uuDuiIRH8eAHxWLTXDk2fIYnydnPMri5zTHDWzBPv8KmT4sl3D9mhIE8C\nN4wGVhywWG3L4/NLoVXP4vLJ/G8ZRr49+qj3GdDxzdzs59c/a7Y25s/8KYOd\nixwZ166Vj7WzNG6oHpx7MdgNqIX67ksw5LygdtHcgh90SIh9YAgjCO/ANMDM\nc5hBmsAibsF26jCe98yu1qxmG/tXoE+xJAcwXz4CG0XivbUwEeJ28PagzRdp\n7Bjw4mhs55waoaDqA4ypCKuTqS/JQcfRUgPl6RQVwF8VjjEzyEzn5CL5JwB/\nu78JbFtmp/ZSXefxwyZPJENbY1+0BBK9Ci/gC+mqsJZDk+jcngoSsEFb3zTX\n1LePlKbE0+6YrpL7FeTTOTGWaBdyrHAJswSL8FZPwritKm4UOo7+q8jLS81O\nE5KbqvaAGUn8vUAQ9sDFfp6325kzjYbqePwKdDHuKU6r5pMJJ2Zwc/27MNLK\ntkwu\r\n=GSbY\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"http://registry.ecd.axway.int:8081/artifactory/api/npm/registry-npm/@axway/api-builder-plugin-fn-swagger/-/@axway/api-builder-plugin-fn-swagger-2.7.0-rdpp-6269.fcdbdf.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6817: Does not support OAS3 validation on startup\n- #6817: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6817: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6817: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6817: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6817: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6817: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6817: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6817: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6817: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6256: Supports loading external OAS definitions from file or URL.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"fcdbdf06c14e82841d73eb92a346989af0bdc983","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.12.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"12.13.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.0-rdpp-6269.fcdbdf.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.0-rdpp-6269.fcdbdf.0_1584119195436_0.7451340935614816","host":"s3://npm-registry-packages"}},"2.7.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.0","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"897d3b098503c4a00fb29fc3576cce59618f7ca1","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.0.tgz","fileCount":5,"integrity":"sha512-P7QbJEHDqv7OwwvttEI307Gvs7TV5mKapddW+uvLGnf3RD2AlzoPPLdnBUhXtZC/kxfWdcyqfLgbwalRoUAx0A==","signatures":[{"sig":"MEQCIAYlverhfLTs/OmSxgHa/2eB6ERCfM0d3IwLBFKZKz1sAiAxUDwn8E4lw/HKn0bxJwqMJ/grppA3tpxOt6GbATjUyQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21146,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJefR4PCRA9TVsSAnZWagAAG0kP/R7qL0Yu8hAM1TqnNxcn\nYpRV1FDhWHxjgIEqfZS4d9VM3qvTKiqjo+09O9SefpqWnI+bmrsheqBByh1B\nX7WPg6CP06XgjeVm7NNDT9R20CP76erifgbVb8WWKseCQn2ZTGblY2hH0Opd\nsgMK6AycnzH0+tby0SuPOu9mVGOBZ5ls8criKBJbqr757qWvcQUPOUOiiEyE\ni+gPvVoJ/CfbUj3+xKvhjuf1rI8qq7WgIvBCFMBA7ltf+FYVKQrQL2hKPG5Z\nNyi4cmvtd5ERA8/7HITrvJs3mkUdgZznVgm5kUNNMUQfreDAzpWTUX8qLuVC\nMzSBZ8kIJG5hmzmZLLcNhCG7S+EHH1ZxDoBM3ag/KxBkhqd7ODm9dSr+ZPRv\ntGUkBk1WS91Vmt9FpQYDxfBHLXLDekAUeQUNzQrHQG25yeqcn4gFVQOUzYBb\nzw3B8sUMmclMswAlZ3lL+b2pRCWTLKoizVWHeQMQW+Qp1IXF9JHec35WTp6Z\nN+iGGqLAC22UTVIWyMWkoMTz0mcuc91Y/e/oii8LJZE4H3oX8wbFSwQSaFue\nsKkG14RdTED5Vq96DbqFygiowtcMX8lQSh0V9SzX8xJRnKuqdgvVV3TRibUi\nHldPQd7uTMAGBOHpHWwqLlIEt3TV2QSTlztsCmDybHde7NPEnueFg+t+RPNV\nN9fm\r\n=gQMK\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.0.tgz","engines":{"node":">= 8.9"},"gitHead":"4b5376d91fcb93f2e52a50555dc7cf9178a58b83","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.0_1585257998614_0.2270170900061934","host":"s3://npm-registry-packages"}},"2.7.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.1","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"2c84b60de30180d7c6dbd09c87114c011ecebdae","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.1.tgz","fileCount":5,"integrity":"sha512-lNRtn+dGK7wO/mWtDfCNarQSQd8V8/oP2eCeSt1a34ra6S/6AXIfUpHXyG3/GwDjte0fcKmPM4i1XcEieFROOg==","signatures":[{"sig":"MEUCIEuqXAbylABk08tKefexNvRJIU4R/EEOFAMSrto3Onr2AiEA2xp5oSTEO4hxU2UWZ3dbbNlozeddhR7L3cGnzi9MM8U=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21239,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJehwQyCRA9TVsSAnZWagAAt5IP/3Mfo2PgsjYcJskH2NpM\nVT1yFrMXkTiqneqlFB6SevuMBTWnxxN2uliJmjdYte8Zp5Pb9aMlha7dfEIR\nchqYOsg+JKpZKaA+e+ri1NcEA3Z9O+IcJ8e9t1C0sWp5Qnr1yGkqWaQUSwPx\nqazxY9OkbD/HJs02gHUPc34qHT8YbA52+5sNx8malzClQ9GVOkyPf5nXZY0z\nFkRdPhysa2vTZnPqiFCAGk3nuA0e/AIq6KjJuEdPd8hHoVT+vYHcuoCMFLrE\nkt2ilquA+/Q52IIxOtvDEpROwhY38tQyjgfYvJo0MEVbHZq/4eXZMtR9SdWt\n4G8lFxrrgK4cbTMMYnIlxumcb4oM5A6ps8cPFYkb8XxZPKxaecyU3jAfQW0I\nXUC5KgSiw4UTjqQhAj3XwNPqAmCAofGyshnWm7zyvQH8jcKCn2/fFrtkiOH8\nl7Vg3e2d9dzIiuhTQ+UCPhz8+40sO//pcezG6XkstvJWnK2QgSM5/MZcKQmv\n15kPVau1nZ/sQcW7PyGMKsJM4UG1LQa+uImPwUBGlV333VduFcozAn/akNsb\ngETVqbdnOc0o9xzdrZa0K9TYbw55qhvzYXxGCXXvUtlVVe9lqHWME8kwQfNp\nJvXuvS3CmJYghl4yiFQrR5pxtZiN0J5Nbsb9nZpGja+s6ZuTB9xaNb9EfDpj\nSdZ7\r\n=Wy8K\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.1.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"60c5183bf817f943a3bbbc7cf20432af50bac7f3","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.1_1585906737923_0.994502521182596","host":"s3://npm-registry-packages"}},"2.7.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.2","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"d48d8d03889d7f4b2ca62c855b0e7b0e7aa11149","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.2.tgz","fileCount":5,"integrity":"sha512-VPqg1LvdXkOHt60kdQStOQibAGFI52lIooB5GBA8QB4qCb1hPD9xpR1CU2oD5t65O+ftfkUYmcHisuOzzPK4GQ==","signatures":[{"sig":"MEUCIQCNjQ4f+O6nz2GWKJBlenilSSL2IrcRmWcqd97igUwUxwIgGV8PIdpXC8Khiw0K23f161whp6nQ+DObbwr291pmS2M=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21317,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJejYJWCRA9TVsSAnZWagAAyQkP/A79Jwhexx01yZxbPZ4J\nvIH3wjQKKfEZqk+HjB3Jq+rQWDLf1KsmWlURmqIGNC7S5ctnZVV84oPE+XgG\nOjATb+DbrW0FPTsntmSHgCCB04pFhxFduusZWq0udwarwJxeg2qMr98nhmHh\nYffm+PrWCZTZgtMGOU9K9hjgDVqnA1/bgbn8hL7vbhsSL0izRU9GQCmVAVzk\nO9NgCX4SuVQykB0HVh7Bx65IAg3MVFyyz3dDJ2l3b9mW2qSL2fVR/Z3wbGnq\ni2Fq0itz/4nRaeR5KmPXKq70giN+faGTN30pIZiC7HeKBphJJdlToiuUAkHE\nOMVqzS+TAavr8+VvI1ZkVa5WjAsddzVh85XxxHEQDEujgz4jxXdEmT2VmX9V\nc53imBHyeV7wf2WO9tTNrrUmqrEXuYY4ttaFxy45PTyiAO7OhiRd8rGqR+Mm\n21DlQVgVxdOaZ87E7uemHliDHwD4XFdSGMJDo3dDWZst8/tR9ekrdrjPTytb\nINRZo1fEPnfPbcPzA8MuHCe52iGaT3cYTOruMIXUU/D+4qjIX7mVZMUgYRPE\n07YXPf72/JmA8nq3I/x/8oZH92UCECCbn91DEHEYMkMYmdvIKB+MwFc33N1e\nsNbBtF2rkRm9vn79tmvp5X1AyiRg2QPkzrCsSsMZBa5NcSdDTnybsKYv/S4L\njo6p\r\n=SziY\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.2.tgz","engines":{"node":">= 8.9"},"gitHead":"e2a495c05f8daf8ceb6a13a6b51e8392c726b88b","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.1"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.2_1586332246488_0.13986358297322843","host":"s3://npm-registry-packages"}},"2.7.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.3","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"1e60590226a1cf5c5345d932e464defc872753e0","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.3.tgz","fileCount":5,"integrity":"sha512-2xQheQD/RoaIflh6MmNz92jf5BGALUGlsLiNCwVVNpqcSC35qHhc4pfc4oSP2aX1X5VfgwplcI7mdOz++bC+Ew==","signatures":[{"sig":"MEUCIEUoW7VQCDE97xRzU4uMv2dnELSNzOpnIWwfpcVRga1jAiEA5i0YiC+kYgOJVpZ4znf4LQbAxXyXoEf5tfelGXOx48Y=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21497,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeoAYNCRA9TVsSAnZWagAAe84P/jT27HJ6ZAZIplXXcsRS\nEuR2R8I90ktwTz0czR8C7e7ZIJw6ASZVQMI8jBHh6HhSLaANP5V5ELOYkiDN\n/BeqflOvW0zwGdPL9jpjlGdIrzC0swjcpXOdPM/Oy0BuVyNDzurAhLGWdMkl\nngMuxKirtNU52guJerYCwhKVZ577lCj5IJ/nAsNKS4JzzAmCKl/SZ2cwLydk\nRcHBVjUtrjt5S65r8mZJ13Or0KQ4O/gjBfiS5Gri9W0ipetoFREQMD247zMH\ndOksN3gO+uyH9/bfU6XehzR4qCZXKI05456LGm0id7tAXMz8+5AhX/VOy9kQ\nyqdxmxCVi31bqvfuF6QwWXAvlStMM4SefUxF67Kxx9RqwbqRKgI47xP7X9lr\nw0X5Q5vS8iZ4s+BUfUkO+xS40k3lVjyNefkxoGlS11U5huNI4e4VGl92y/ui\nGWYtped06J/Dtk2TUPjnLdT+1gnGmlBz5E2gB0feE51EDfS9MO6w/fPQflu5\n5QXz2L1lkT8I3ueS8gAfIPfgy7u038rQOZQtg5n37FoFpuUmub1qce1GbyhC\npDP/4eEOFdjsGbOyn8DLBCKzdmOaDFjPp8V2tSR5fHpcu8EVJp88TtY0IWee\ndyrvpQOkbHO1lu8+Rlh14WJQq4JGQYz22P5GkyteFy84svUUzb0h3qv4LGlw\nuTGE\r\n=WoCe\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.3.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"6d443c7e8d778d7867d6cfaeab106e91b783943a","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.2"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.3_1587545612488_0.20531489773370248","host":"s3://npm-registry-packages"}},"2.7.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.4","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"5b95413ae9209ec91f258f8d570ed15042cb2e04","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.4.tgz","fileCount":5,"integrity":"sha512-+zf/t1evKLIMYWZnQwGhpF/bjCgp9vtV86Bfc9YnEs36yn1RoZ6VCNhweBX+qxINHJ33H1jvx8DO5I3nV+jjLQ==","signatures":[{"sig":"MEYCIQDc/mwgBnfRJWmFTal9CWG7JHySA6SAyezX+/kSbQVj2QIhANjCIo2UEOOBYVqYEHz/0/I/36rQS8dls37E8LuLSRXD","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21863,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeoDcuCRA9TVsSAnZWagAA55EP/jSAJLgz0YQ7BTf9REL1\nHdvvume/C+tS5UScG/w6p4Hwus7u4ACrJIh7lA+1xIVk8JpgLHeSRxm6fkgN\nSbGMM2q+HIbmSa8CjyWmmAypjMdXM30oyk3FBbkqrJ8AJN9DjzekZMVBK4Ya\nbfVixjN0gowwylhOsvMyRk8AUxHxrsK0lQYNJuNGxPS8ULCWnxM9RovMjsoS\nONNfesghi+cnpn0k/v0GZR54MvLp3tSzZw2T9BGUMFWkv9qQzIwYSOl60spD\nz2JnxdoRet0v2HGUlPf4DeKfJhwOZ/BXBEkzosEqh//jRSUg9rbyrdP5auM+\ncsKyQue8/JDMpJoIQRVJ4qSkd/acy0QjOQTptT988Oh6c6Xg8+L2GY3RK4K6\n0iO4PCu7oovhw53Qxiyhq0oL1iTE21EiL+i47ThvHfuGoDLOxImpGS1yG9yc\niCD7fnh9yY5RbGTqiG7ASXisCYXrWFHG8YUip6FR3kRepFYbkwWpb1kXWK7e\nJ/aBuP3gGlQp7d/1Qene+w5REhDyvjIsakfIMYaOShaSi8377UoGmS87uXi5\nxgAd3gVzkild4jgLx4RHOv/2KK68qiohAILZeSFo5U4ScCVS8g1QgjCZvY3A\nAjF8d/3/B4j522lhsuSdb+q2+EPcJJ4ZZrAdBgYl1B2raS1pzf9ZDFnJ6ZIS\nXAH0\r\n=VtBB\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.4.tgz","engines":{"node":">= 8.9"},"gitHead":"fa6bf9b9e5586c8fe06aa4750737dab46d43712a","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.3"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.4_1587558190121_0.3094932997576343","host":"s3://npm-registry-packages"}},"2.7.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.5","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"04cbf414831833d9dc7f2739cc0543604a006455","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.5.tgz","fileCount":5,"integrity":"sha512-oJ7CDndLkRdUYoKTU0JPHl7v1VCadnt6pOKWALtm2FDJJlsOx+eV2r1iy7SJ9He6cJwBQRh5nhQZ2pqPV2ATEQ==","signatures":[{"sig":"MEYCIQC80UvkD2EIV1c+yQyyKn1VoQetzVVR6Xqzup20ZdITwwIhAJARr0JCBUPgivgXGUAeIltqra9VMTaGkEarfx1Q7GZF","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21950,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe2gb5CRA9TVsSAnZWagAAk7MP/0G5MDIFcKlqh/cnrsmg\ng9bAlpRzlMl6ZuoICeXcP0o1prprEvoyafL+9ilXDga1qXUaAAiBkP9DZi8a\n0G1jp6ePg2WuzSYV6pDB2dyyFO+32H365tKxmri1/IaT3sXE9D3xX7VBt7v8\niJqbNKu2eb9FwpciCMPSUNDtN9SeVJXfyaj0PmDHtqg/WIwc/QtRWupBzFg1\nZ+IPSikfH38IlnLDmy5tUkQqFaZOnqlzCrnUdNFPEuFJFPZlaV2Qn64UM9MY\nhSJP9FiWMcrC2zNq18hAquQnBVaEEf0HphnMv9TzagnixeK5ZUTn1tLrz/26\ndcy+jTFP6WOMk717m7Zk7s82OHhcUryiDRrqqka8Auxbxod1RHzrUp4D7ctg\nE5eIsiJay1bUytcWt2gdapZxIjwRt1Fl3NxXqBchVzzUNm6e71qWSVfujVYD\nYmRAPn2wzpMCcHRPv+Jqw6uzKTWMCw+50q1NJmFqdwLB4WKFKC3kEz+Kbe75\ngxqCUOnvbwCc1Fu5dHqji5Zo/88JqzoPpDYYTCRURm9PSYgKndZYMAghDNjJ\nYqkWXF90tVEkhY7tLWYqTjGZLXBJ3u6lQuJokAiw0675eDdv7ytmeg0gSyzE\nAkaK70LZQKBD+qwITV2V6cie7N3y8Wk4QKBx4ULfc+6E76OYBmimSdLIB7hh\nWuPA\r\n=MwFC\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.5.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.7.5\n- #6412: Using the new version of oas flow-node that works with SDK 1.0.0.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"9256b0ac9edfb7878bed2c4c52c284ce3d52ca5c","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.4"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.5_1591346937000_0.8182406980695278","host":"s3://npm-registry-packages"}},"2.7.6":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.6","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.6","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"ad9d5256cc3c08264b9a95a1b58dba9ba6ab873e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.6.tgz","fileCount":5,"integrity":"sha512-+bl8gTAI6nIg8b8ypHgRnNo9nIm69gHsUcIAMTM+SY3DJ1g0CmNNS9fhRDUQYphV5KM9x3yXGBjiU7KyQpb20g==","signatures":[{"sig":"MEUCIQDQDTJP1XJ/RBJ3WILb4VaDzQ8cgBxaXGIFgBc+SH7hcQIga+9UR6mQwOMawxX4KjkoqOmnN6OklbV4923xrt8kmIs=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21997,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe2hyvCRA9TVsSAnZWagAAgpMP/1tNpdohL3/OL2TB2cbq\no+AIhWSyaEIkVJp0pnVET2L24acxR5rdLdFPzpnYGcmu8Rw8/GBLSFK82wMZ\np9XZS1Id5PePwORxBA7rPj3SzTHfrjdcdyNyX6/d8sXW5/+vT76cJsaq1c0+\nE5yJ9R+DJp80VIx3ASgVuJTYfEob3dZajmCyZVIw4CEI6zzYPvSZORMwQcJo\n+dYVQo7/REuJMHAUYSaAnf86ysLIzlRlhdtgJfQa7DJd13Zo56FGsZ2jb/bt\nQH/6o1QoOrMTuYfqgOV0MetsTZLZgKng3uuyaswy5pLCZ6vXWOxQGFZlA2Du\n1qyJYY0vTr84cf7nxJBJaARAzZZz5GZRhiscLGT96/gW+wF2W7NsMO2N/gdE\nDnt8tMYTFrcEGMaAVKeFIghmWzCpb+I5u6nM+Nrq+5Bg13khIPJ5CGjWGNkP\nbSQljvnUtFTlDz1skoR+G1UwdOMco9GdDNqkA6NcftGKSzBeltz3fqmbMNbn\nCXqfxr1VhaJVkBRaR2ideQYflMdpXCaobxFkV8iRHnPZz5AAtTgwy/H3sI/U\n+lNRbmWbSuPpI3HlKIJJXsdDYp+7Auz6ugRkhK8RwdewXgkceZdx8Nw+OgAg\n18D1BbzVF8VOFJFLyov+g8O/u0JZdUw/KJCLA/q+1xl/qu5M+70dbW2wcB+V\nGiUU\r\n=4nPN\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.6.tgz","engines":{"node":">= 8.9"},"gitHead":"18342f4fbaff7ad3256f5923dba7fedbae481859","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.4"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.6_1591352494954_0.8252865342212035","host":"s3://npm-registry-packages"}},"2.7.7":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.7","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.7","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"7d74870eea821e7b011be7023852352e1aa93bed","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.7.tgz","fileCount":5,"integrity":"sha512-q+xcEfdjyAvYd0Ih78RblTspuejGR1NtR7v+HP4h4Ds1cppHGHO8e0D+n5/vE8NLL/FP/F5VhvwfX6wvWihR9w==","signatures":[{"sig":"MEUCICT7XUpkkz+iUDpuSnJJnIUMNPr8iT1jrNAMvFUKaDwCAiEAo5y+dnpkwKp6hXSlf91mUUrQsGA8GBB/bkYaX7SgHVA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22183,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe6K51CRA9TVsSAnZWagAAPIkQAJPP5V4HvPWmsA8Yn/kO\nHR3ogKXNL+Q4mNtHUChmWgbS1q8YruhX4r060k77l2MCNERkPeYYQtZL3+4z\nteIjiDZcjE9jY21M0pVX1GwgKja7TlxUQ8hmy9Z79/hPCkUBeejsheXGeqqR\nRIDZnACPUeXlwE4q4qce53JYGBneqAGN4W3Ol4N1SnUkEZ0D0vzxXrQJ0b1V\nCu3jrBdgMGMWAFAMEcjsibr7XfSgfFAkhErJ7Bwlr0/ZRD8YrLEnAtja7PPh\nnSHvJTz418qorZb66TRG49HtsANP0T9SuaRMi/ibs1WrW0Wv+QNIvpQrTVL+\nN0NHXckZLi6mgauekNlDEcjg4qEHqxqOHTqGFBnnQpmttFn+Q2j1ETUsOZ9k\n7RDm2OLrhzi6nnbkJRHDASUTwdBv/OhfShGV38eox8AHX2zMLFO6CEuDP2be\nFx+QfHOyIrl0aOLDGX8HiwFaP0eeg2X563ufqp1v15rNRsuhuvdA69g2+1qq\nv+ydJXjxaRrfIovvcw9N+3T8GkPbOMUKI8XcTO0fFErw10X1Xt6hqJ0QMp/t\n79sJc7db+Yr3v8SIzKQRJdlY+FgvjnVHzogLeBRSvw+0Mo91PV1zEAU2eRDi\nzmmKaadHqy0IOSucR1CHM8kwVJ+nRdAm/NwfctEdfLIkw/qSTF8587qjOgPJ\ni+ZS\r\n=9bYn\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.7.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option            | Type    | Required   | Description                                |\n|-------------------|---------|------------|--------------------------------------------|\n| **'proxy'**       | String  | _optional_ | The URL to use for outbound proxy requests |\n| **'insecureSSL'** | Boolean | _optional_ | Enables insecure SSL on outbound requests  |\n| **'uri'**         | Object  | _optional_ | Overrides the predefined endpoint URL.     |\n|_**'uri.protocol'**| String  | _optional_ | Overrides the endpoint's HTTP protocol, one of: http, or https|\n|_**'uri.host'**    | String  | _optional_ | Overrides the endpoint's hostname|\n|_**'uri.port'**    | Number  | _optional_ | Overrides the endpoint's port (default depends on uri.protocol)|\n|_**'uri.basePath'**| String  | _optional_ | Overrides the Swagger basePath|\n\n## Known Limitations\n\nThe plugin has the following known limitations:\n\n* Paths that deals with file upload/download are currently not supported\n\n## Changes\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" paramter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritised as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be ouput as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"14c0336a86ec27dad70517f78710ef4999b88b83","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"node scripts/plugin-init.js","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.4"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.7_1592307317079_0.7273534204970862","host":"s3://npm-registry-packages"}},"2.7.8":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.7.8","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.7.8","maintainers":[{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"vchauhan","email":"vchauhan@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"81699efe8ec672355f17abb44c8866e6078a98fb","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.7.8.tgz","fileCount":4,"integrity":"sha512-h2gfq94ivlk9AxL4V+JDltmGB+mUcbQouRSdO38yA1Pnb257VbDbtsiyuplhoO4UNTLv/OjyKcT2430uphNf2w==","signatures":[{"sig":"MEYCIQCPJKUg1dWoISGfdG/VJ3+5Wx4UrrmAnGabt6BFC5fIbAIhAP6EPsEEmTEPD/Tp2hpjfDKWsRdJIK9rnpuUI+eyvQQS","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":20863,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe6a1pCRA9TVsSAnZWagAAOU4P/3ZJBAAVPTI1zhAJC8it\nLJ7mBLaQrP55K4qBLrzIi1BgskheM0rOPUGYPaR/UqSWR2qb+s1lFNeS8ixu\npAbhivxON7x5CTVle+v2l/YSSAEAvuWPTwfAPxJlUPq9DB1kuiuEks+kLMzx\n3iPpCVm8OdOb23sYgeGgxWcQDnZrXOUcN1TspZf/qVWoKzXKPfXLS764nEuW\njQyIYI//EJQv4PXdgsEL2y66R0qYOJFI9RZKx4pIWM6Wo24by5oZBQUfPiW6\n1kuBrGRLvZTvYtUMcjd6hAMlqD9mV+3B5FJFGV/nzKKmqXJSTIPu8T87wn7U\nU6kbz0BLmmSxcm9RJeBAcODf8HQ/zGzG7aMuukRnJBrhBIhtPCAtQVR08WT4\n5dQsBO0IxqsxtZzpy6MBZfmd24X/UsOPzPXrOoh96b/SBk+3iSF1IjYYmUim\nXJ7HDi2doAyvAsBTEmc5oxqW/ubUQs4oP8odO/Rro8yOmK7RiF+/lVEgExJ7\nlBCWgmcZ0bLQneyQDJlSymlM6VuETY9uUKmxXqOE2P67Y+KHJkOnmnDHDtC7\nV6MDoz0J1wHxC7cGjW0Z1SUhQeJgRb67Z7EbaSF2HlBS6ifCpuq1jTIsoz4a\nV8C9fWz81/Sm/J5/cQ0BFbs0mmBHtAbJclwqEGGdMy6SRGsjoo7HFzywAd0V\nOkYt\r\n=mkKS\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.7.8.tgz","engines":{"node":">= 8.9"},"gitHead":"9c177b2534111044c356853d60241fbd93ec9e54","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.0.4","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.7.8_1592372584919_0.5915174291726519","host":"s3://npm-registry-packages"}},"2.8.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.8.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.8.0","maintainers":[{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"1fb14bc3664a4076a4ab7a9aa90246197619e544","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.8.0.tgz","fileCount":4,"integrity":"sha512-4u9thBluSg70ewg5WakLYLQdCDiQ9HKCOZo0hIWPwnkVO4npXrGxclP3azOs1oOal9YEdO3LC/01zmsT2THBCg==","signatures":[{"sig":"MEYCIQCcNDxKX8xlDLDXwKtJl4on0huIX+DrukYJVAxw0oUxXgIhAOMv774PxejkiqqHMv0NHJ50bUCrYr5aBpA5yxc0rcup","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21224,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJfWe4cCRA9TVsSAnZWagAAUzYP/R99qnqKEBFjilb+J0Ak\nPegKkT5BL/A/zsgj+AkveUXb55DZubbkO2FhXLCW/gflkeeYLazrDJ7MvTHA\n222UWKIkwSzg2G6kkg4/zQRCfY8D/jOU9PPK1gdEhPi1YoZKIPsD/KYlr2OO\nOJywWoSUEw5iYggZ1CHb4SJ4+iY4eJ/za+ZegWaV/6lEYvuEL9F6kt/500CB\n5AnmQ5qYpUjmuLzyXSFXFYv7DQtOXp79dt+1C7cmMj374t4pwSv5MYrbCCCf\nZLXdHBw+mPVc4GeWt7FYqQC3o/JpeD30iLDdJNF0cKS0E46EtjGxxxPM6aiG\n1YAoQD0+mFxX5SMKmO4mWMQ725TKWgs3kZQaX+Bd7Dcl7AzjszVuiRwG5zW4\nUfz4uwIyKrXU2f9oc/kzPZSuP1YBcIQJDRWoDTuwEB+7euQnC3290wdEF+6Q\nDMLepm2yiV9IYZ3pPxZLmW+qmGimkoSg/OA+SHJr3MjVjt91kJChqtNAmZRH\nt7BXz9fac5gQeT451NRiQL2JCfXDv8Mv3C11IXgCG8wqox37aSe5ubhnVbBJ\nxhDW/3ZVCql0PpfPypVT12nZo8y0on96cNaZiKI57YpCVyrnQgSvD7ZOlijp\n+01W+X6kQMKZ7R2U69glLAjXcAUOMv4a+7/7KdWFVVL/KQMPjRKzXg/IAabX\nIKuN\r\n=TMdK\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.8.0.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"7983d68b810acab52a619ab981410c8c2daff107","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.1.0","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.8.0_1599729179647_0.8622339534155501","host":"s3://npm-registry-packages"}},"2.9.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.9.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.9.0","maintainers":[{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"9003f5ba0382510083ded89713c8d8a3f06721b3","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.9.0.tgz","fileCount":4,"integrity":"sha512-XOZsB4WHJjuHjYmrA2YrjidFuLfFkh6kIHvP1Ukj2LTH5JolPInRE3QR9UL7miipRYrRVxnzOKmZ256nZuAfPA==","signatures":[{"sig":"MEYCIQCqlXwFskNorHWSZV5Ej4SF2JxMEYj01+OCh2yl76HjNQIhAKnYFf7BzH96iqaSzSui5fIAXNOLxPKnrswJ3p2XRYDW","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21470,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJfW2BVCRA9TVsSAnZWagAAYjQP/0aKwLPT76w67wY444yV\nk0nqRQHJ64kPOGBOtn9/Z/xTUStbM/Hp17BGrSBV52WfqhnQuQjiiTJRkr+n\nm2LBj+AHYqO6+Ka9cc24wwlSdevMIPsB2u8j+xrJ2XH22ufAmgZLcn7AetK4\nbwCmOwL0ouZKRgyFO8kcEoWReWiadqrJUoDSVOo+YhL11ktE9zVyRaMy8vjk\nhJ3FnYtWyRXz3FStpOD0qX8diyYsWpiIDQ73auchYM4kHnAGSsQy8aIQ6TXF\nMdGPRE+duXhSFBm7HQJwNJqozj76mmp9jQID0jlDdKLjHvzXaewvBaVvJpNX\nQoVqvL/xdJt4prO/0pLR5/WQjF4+5bKtR+6uKYBq3sX40w4zqAjZo2ReB7Jq\ntkAdfdnyNtSpICEFAoGdft8UrMprHsS+FS5MXWDvb799hDg7OPmpFkSKXPZ9\ngtZE/Z0MLeAS61D5f3STKhSyl8gpIWlDVWR6T6xe8zEGMVxea/+dJepy+FJ6\nWB4wul9+lImymPiLkJKybSqYmSILti20rn0cP2AEzWNWT8MqhGalzTVhQ7Lb\nlq83YPTQbzmGyN9tPM9giLfsfzt6nghxGSzc8/0HZQgmdIoQtamQzDuIeyHM\n4ik7immTCKqHnJyVYGaxNnxqZrEus9hjuhLKs3uEeW8OXaGQiJYua53ouaQq\ns4Un\r\n=2e2G\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.9.0.tgz","engines":{"node":">= 8.9"},"gitHead":"82f3a742c3513173088f2838a538fddc0882df32","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.2.0","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.9.0_1599823957338_0.42021097601639434","host":"s3://npm-registry-packages"}},"2.9.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.9.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.9.1","maintainers":[{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"ccf059231f21b20562f090605b0495a6bcfee7d9","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.9.1.tgz","fileCount":4,"integrity":"sha512-FLnzJcSCRZ3JaC8nUIveZHuzGnrWF5ronESw+u5mwicVsefZsx2EIDMPlFFHh2NsKNrn8hdrr9s/Vf9HU3P8Ow==","signatures":[{"sig":"MEYCIQCOL7bkFC6jp0dLwDA8rj1jTDTMiKr7kgkFbjC9PH2/ggIhAO3qC5bx08IqQuraJWVvo6ap9IukP6aBk1jwORRk5mms","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21545,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJfkoluCRA9TVsSAnZWagAAJ8QP/1WrPJYRhcyY6jO44uo5\nVRmh8vEU1JNfwnaMNXPlRoJNCok1y6rLvbEQB6KqvceSYFSBiaY2xrkKIoYl\nXbvnTIy7rt2NqwA//GrJT/s1SVi1UT9d5Q5eC3UlOlhCmTXVbeWVNlNO+Jzl\nQ6GCWsr9hrml6xtS/2KBGA8DRTdz8Enyr+eTVqR1HB40kyimMi/mOo6MpzTs\nYK5FziSJQnyFWa22PTUQl3a690Mfsg/g3ZKAh4yjwCCK2p+yM6WR3YWJ/SCL\njD1ICQx6gIq35KnyWPtKcg9l2aFpr/0BiCcxauuPlpAfBIDm+xMRzxPvqf6F\nX+qPtxq5tn2WEJgK232JMcZvrapBhJnvMPbC4zCITCok6rvSwJumvfNRY1DP\n84zTKarbQWki4MM71V8auFV/pBJKk1/OPt+MgBfap3rq0c/qkvjLzjyy88/K\nXqpQIB0MaGLJWioO+Ae8D3t4Yj37uWg7ojCohOTwCBgJJj9BYcaIJGBtbMcz\nbFHW2akv8mtdp6lwU926OpOhlJn9awAF7EAwIfzxteJMmyIj2ZmTIgCfwaiE\nABV4vLfVqsHYFBCe+3yW35ws0/kRuWPC4KIzFSaOvOif8HRD7xUGM85tNLZN\nDhWj5srw1Vvp/9/vnAEH4pWrlT8/9fRmX0uKsC1RKAYBzgltn+jwtYHBK0mF\nQZzw\r\n=AYcI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.9.1.tgz","engines":{"node":">= 8.9"},"gitHead":"6a77bbcf2abc2701e3c39b011434530ca4e48ecb","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.2.1","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.9.1_1603438958472_0.3567174922891625","host":"s3://npm-registry-packages"}},"2.9.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.9.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.9.2","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"23ec306d210b98354a8181ac46bcca342760e683","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.9.2.tgz","fileCount":4,"integrity":"sha512-KhXP76pB2/MDXvxyVXhfmwuPxCUmZREUbEiWkz6mcZnaYZ7ztyfejFsEB9GPkKGKFHevXRSzwe0HZ574/bGogA==","signatures":[{"sig":"MEQCIGYX0sESzAn8U8C3GtxZVg+cm/x5Zv6A0UXoi24fO2MzAiA+9xpCFY5c6YJKqmfGjewQ176TYCU4abro/bPlgO0zPw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21697,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJgHTf+CRA9TVsSAnZWagAARJcQAIXz4dbVSiZdwBEGvHRJ\nBSbI4HfR6pskPtn3drWu6Rry9QeUoGq4LcCE4M9d6vVOAfb/GQJKQYe4uCtx\nBIdf2lRTBnWP7taEa4mMsvzO+zJU7Ye28AhrQShPp23NxCrvkHqe8aH5zClg\ndf9npixtKWLF4C5P2N7LxZ9Qf5Tii2vdhtT9rJHUn7iD1s+eVBtp4ykCgX7t\ntIbjBn5w6WCScpt5i5ZMNXxCDPhDoh5ruDU2ZVKuYwXim9Pb/wXpmX9IuxAa\nvDdvPbSiVt3YhQFNoU+Kq88sMq+WM+1au+mXoQsoFUNMeH6O9hhHT5sKowJ+\nglANpTYsBA90TKwRePypPAW+lAPwBNn5uPYQaeKdhoFWJ3GmZauTcpqVrkgb\n72WrQoYecj+i8h0mxYuWU5rqYR9vnHK4WtWLJ6DwdiE1eHb7F8T74KsWALUL\nU521vKrxvajBnSX/rMoHHWlRrPlh1oT7kpOLtBin4js7+iN52LlvI/tCa3Rn\nQEbF3YhM5GN0GOjV5plA8/0Sxx6z32dnjG6YaigLrM4QEyVynsOQeO6xEa/S\n6NrE87ayapQCimzvcoBfMg+LfhXCYZg5Kb8YD0EdcvVg/qICGcDduvDhkvZ0\nzx5C5FMEyh7/oHYEe0uBRqDpmzOQYa9VXXoIRAsv0Zkaixl2ZJWBquuXM00r\nFJON\r\n=0BjQ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.9.2.tgz","engines":{"node":">= 8.9"},"gitHead":"fba8a37ca7ec0545c3055b148c13a24cf2506b9e","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.2.2","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.9.2_1612527613867_0.2851313502249213","host":"s3://npm-registry-packages"}},"2.9.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.9.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.9.3","maintainers":[{"name":"cdobrica","email":"cdobrica@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"d8a492eefc8d70d1a9d5abd1c2c7070771f53510","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.9.3.tgz","fileCount":4,"integrity":"sha512-bqm/XtpGiM43IrioAW7StUSCpBV1llVYrrjzZ+QISjyoaS0grG4xnHxyr58ReTbGFGECEVwWIDr0rZZ0Bh8SMw==","signatures":[{"sig":"MEYCIQCtLMU2d/CP24i1mw1ZnxW3y5PspN4uRj2P5JSyjfC9ggIhAL4BTdwXZhTAtfJ7EaR0Yy+D1HxPc2JIwER60dr0wWOy","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21772,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJgkoiLCRA9TVsSAnZWagAAS5sP/0DIBwYO6i0Fu4aE/zld\nVIfvKbaBLxxeH0/5nDp8G4T3F+oeHRkGWo6RlM2HfNa1zg9ULqzKgp7vAklF\nfrowUMmBLuPE0OTn522Q8g4YKtrNg8zC+GG+yOIYEv9XaM/txQZFhhtnnmOf\nJeqlqBVZcTUKNUzWZRWGYo3EEZhY6i4QDc3n9sFkp+8IRuDrUukHGOIn9trD\n0ZMMQa2KO4hIkVQh7yIbiWSJNBLe48Z8hiERYj4yrNj7gqCPqHp0Q//8udlh\nC7UUWs3VP+lpMX1i5GfJHUyI7Y/pDTPx50TqihIHs5g5KCZxcKbIBrG5OVG+\nSizQU7UDDVT+EQo5xGsEsvtsi78YScfQB7LppZd6F3fbSQmY2+ODhRkqV3iU\nqO65etdAx4fgh36Vi5axEiVd9IGDauMSVJy4qbDksZXApf9gmEvKdqWkN1nn\nz73kOOGgdUtdkx7K93ZQSebCEaMR5rOtPTxhA+lmHF2BU1LmSqOrz9j1I+0V\nawdST5nLcOh5qxeogz4Ivvd4YY497ao5xkr0tPSkJUQzbPF+Af20UNGcxPCq\nE8AMGT8FvThLpKHCHSCgpNXMspbTn38f29dk2ZFMvkqp+jeTmzrE72xp5sGL\nu4Suebo7IN2868jQCZ60wKr5RB6ikmf2jmCJTgLwm1/t5qDoapRsRLqKVqqK\n4DCk\r\n=Ap2h\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.9.3.tgz","engines":{"node":">= 8.9"},"gitHead":"a2000653efd521994175ef5a3905e554f0664095","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.2.3","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.9.3_1620215946554_0.19700024120513748","host":"s3://npm-registry-packages"}},"2.9.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.9.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.9.4","maintainers":[{"name":"cdobrica","email":"cdobrica@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"88899c759756ecee114e782fc0810212ec533adf","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.9.4.tgz","fileCount":4,"integrity":"sha512-sKA4pv+IYGYS9sxts2n4UrJo0TJqSxoPSCoZLAHUmMzN0kf2lO34YYCNasqJwQqX3szbiX+nOLdfadBtaAstmw==","signatures":[{"sig":"MEUCIE4S5A/u/+u4gh50nOPsd9JXuCLZ1nGj6lIIPfhbLnNJAiEAsc5nTQtLORmsiCg+yslZiP1ix0d+U7d2+NXdCDd2Tao=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21887,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJg1fVgCRA9TVsSAnZWagAATWkQAKL5zlSXa1D4kcpX8FDG\nGf6yiVqNE/4Mx2l6qUqGhpBgxXO0uXZwlpi93NVyJlEg5ivz4Mt2X/Y3H0Lz\nMkLi8IWeOFRT1vEsBzrEiGcKI7aqXiYStu01AwBw3K2pO5pHAyl1Bhmr2SYg\n9kIwoIm1ho1oVk7fiH4uSRFji1ToDWLjda5ECfa/71dWXI1a30sJKPtZ1RvY\nEly/UTVIbPc1dUb1WUHgHkh6AdFNERMsiSdeGquNo83jh8PG5fqJiMpkTLTD\ntwwyS9UaN1m7/C4iIzioJqZvnYPoAmp/giC7pwMewZpe1U7rg8CFCi09MrTU\nTqZOnPbMxHBW0XsvPQCDfth4PnVBmE7cfG0S/Zcc+EzKw6EGLCMvR5KcgIL0\ntAYCIDK7wJN9bhUZQQQHx2yB03U6Wb9dSGjV7tFRziezqcCeOVhsjWQSBUCM\n+cASJXe10l/CsMVBlo+pHXMD1N95cmN7gQgL+CiRR2Z/Qus8KQa/VCbXEl2T\niA+nqGDxCqjS24VzETpwGVQ7L8ADJ+65ac73vdhgaD1gtwIE7qCzNjJMz2+D\nrRBN6l/nKXIePliPfNsSj+1eS74sHLl25gLEtrI1Jzkdhp3pYFcVXdSoTeMv\nF04g9rECITTTRzZ8qKlqGWGW/RK2yvgHvbWS+ywx21ATbIY5SfBQHxKU27cC\nq+7B\r\n=OxHM\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.9.4.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flownodes\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"9d6b55074b871be37ea108c6a0cf5871d5568025","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.2.4","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.9.4_1624634720134_0.5633829277507829","host":"s3://npm-registry-packages"}},"2.9.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.9.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.9.5","maintainers":[{"name":"cdobrica","email":"cdobrica@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"pboev-axway","email":"pboev@axway.com"},{"name":"jvos-axway","email":"jvos@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"83727c3bfb74d481335b0f8bf4acc2f12f3f6b98","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.9.5.tgz","fileCount":4,"integrity":"sha512-g/4dWUxno/rqot32mNMsNsODOTuOqlM9TyF5FeYXC9OkgBJ7LdSVPFxnqfAzfY8Sq3WMHcQji695Y+ECStzp2A==","signatures":[{"sig":"MEYCIQDRbJ25bkVafN9Ihw8tvZ9xFZmkGqP7V/kBgfSYvZcIDAIhANKv6NnCDrUXyKg4rHzTlWSCfxm5DPQPSy66l/Etofj5","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":21948,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJg3F1eCRA9TVsSAnZWagAAZe4P/1lak9YYdlxoP4GUYxU5\ncGHMkHGPFAIXBmBfvKkngCpLuSA3mYxwSqoH63QFcru8MS/xg5bgAQc89xuS\n6fdz8hWk8KdpI2TAKyPyDocCAIwlaCl6ndW7KCn2LeMU+5BbScmJajv/byg/\n6vp/PeLDQHNbQhSPTRqhEEYqo6VWZP/yRnyz6S3W5VuqIMmLAaaG5EID3Sly\nMa36sj9t05Ii9Ac5vaXxvBScB+m9TMPmMKcxfpm/M9F9WfyIx8o6lTZMMBQ4\nj12hsJiDKl26F85GrmfmUOL2aztAhVKdGs4SsQy146vedJduuy+WvkvTOhfH\n/KhcWhWrysHyLzSHDdhQ0l5R6tAG/UYR4OugVylg2CezngAjeMGcEOS9Ffz6\nxJGqY6URNsEeUchjf62fVCN1gQHTFihlM0him1iiPrIve9mp9Cj9X1ldpwIP\nlHVSZ6G4TPuyp2JozD5zr3XpfPtNtYO36Myq0N+LFWuQoywMqhCxocI8CVbR\nCnYaIrgh/9+uc0KE6sgETFW8Ncgl2NL1IUY8WQwgtMAKwqSXuWOiVsF14aUi\n32wYFMxYv5hwOllb40ueX8WQiZrD95CVF47xqVJvOo0v8ImEN3rIy0uGIJry\nI5bjYwmtGtFdsLAYJ9WtgIihQTO5QNVnQ70nCOQuTqvJE/viX//knokbMi3o\nrN76\r\n=h2t3\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.9.5.tgz","engines":{"node":">= 8.9"},"gitHead":"5da063a3e99ae764900279a1d45abfca9e11e6fe","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.2.5","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.9.5_1625054557998_0.8409081549811657","host":"s3://npm-registry-packages"}},"2.9.6":{"name":"@axway/api-builder-plugin-fn-swagger","version":"2.9.6","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@2.9.6","maintainers":[{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"626087326b79fdce0ca270d0e9bd487959cde960","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-2.9.6.tgz","fileCount":4,"integrity":"sha512-I7NES0eT8MILhxNlA3lSwRsbT0seU1caLfpBvBxPIt8ZRRswKb6BzapGVWrLahL+CLuZjH9dgOYPszEajG07YA==","signatures":[{"sig":"MEQCIESRY5/K/SfQZuY3ogw4l74AgwWrREpL+nvPDtg3wKE7AiBod75thasV3QhVWD7jBGg9hwStqmARZ45oQj4OcCO9GQ==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22139,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhJlStCRA9TVsSAnZWagAACoIP/3qXDfVQay/FdCEom0UE\nAIk4MtqOZvgJXA72CJPRqJ1B0Q+zmP/iTMb8Y5lKZGZc/fyVp8YjvDeeoNMc\nmU611CoZTRux8TxYQaiWIBRJZtiWvFvHELwfiW+YCokWyhkQRuDzqKf+bsm9\njjHZtCmIvfegej7ilog+RH7PWwukgB6Dx8spj3WO7P67Gbgo5N3bxXAScby0\nt5LU/zZsjDZb280nEzydY5ywWJN4r5WA7YFCcAlnCc15aiRSsvwjbRBi2QCE\nhWrnVnNlsPUuh1eSkoO6TZom1cnNbJhd/1Z37KgSkLoSQG1cNkRnOoDzPTJm\nH8wHdpIbjSgL/GoNeWdtdjOjPGVddqFMH0j807VeCWPYnEi7VD3xZOLlEK1C\n2rxm3VkAWQWu10g7JkRlJjUnGsq95HAKmSbH5i3uy0Fc4ORp8WkFS8nB2M1/\nJKB4wifeVmSLf0gs+5QlVbyPhOwZ7otxsMm5V5VQRkjXJNDVTbMGjVU1akXG\nuwGTASz0bagLxDVeWDqu4vtXflT35Tm0BPWdzDUQhuEvF0UCLqQbAXT7JSZf\nFOzrcO4ymhQQJCfsJzIiRnLaFXkkOOLcyEn+M5rpJwsyqiQr3wfVxb6WOwmD\nfvnAv5STCKBSd93MPYyHmBgNM3waDLMQX+yUnVBPIuwvC6Xz9HrGI0VsqeA8\nRvud\r\n=hG+n\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@2.9.6.tgz","readme":"# api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/API_Builder_allOS_en/page/api_builder_getting_started_guide.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flownodes\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behaviour would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"6065bdb22d167431797e356b5bb35dcd4b7857d7","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"1.2.6","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.5.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_2.9.6_1629901997670_0.06447646477466584","host":"s3://npm-registry-packages"}},"3.0.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.0","maintainers":[{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"f8977442a1f7a5fafd8d445717e96c5a06a0d0a1","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.0.tgz","fileCount":4,"integrity":"sha512-MwW6+SASIXRvW2dbAnZ8bFlww+wJky3mJJ7im9yJIV/7rMLnyKxd+R5eMt8yEWSpk5Otq+xyh0GyzQXsSvq11w==","signatures":[{"sig":"MEYCIQDDoCjUnRD60oL50gP1oAzA1pRKaHKrLpLAujFPlxpT7AIhAPscqGHBEXTq2vkQ+ToWeXB4oEW1+PajTUvf40tq7mLT","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22389,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhJ9bBCRA9TVsSAnZWagAA+ccP/R6dyryQEQzE4edYVzOd\nkQdFC98rhEq0sQ5H3KfpT14Bh0H9iDlTD9WNaqcRVpNe1gXLKZwwfCYO50t7\n3K7Hcg2bviB8vcSU0p9b1lZ63qhgrqepTaM9KdSP6CPZf+OdeLPmLjV02L2z\nkveRQxp0ZkYh322r8St//BcAjm94y1qrFIAOAgJZqGzzPIs3EcH4vE4/++bn\nOfRNuaq048r768pv2bHL0ZtiyVHY7EXdLB3qPZTgggUul5e+DC9b291uhrxF\nWaMKGZvorQpIYG1HETjKXwY2JaBrAK9eUoiXSh7KIl7MWs08hrzN2OYkx22u\nl1yjlmUBsrRmFYGVQCo4J3zvXZIk8lFEkJuITR0q298uRmw6vjef6v3HqhYK\nS2w6NGKkX4DxyllliRTBiPx/09Of7oTiuqiAy06Rw4v53AuY/tvpZ5//R3eV\nwb3UyHgwoYAqamPS9383B/IReSsLyyWNH2EWSEBDIRetB0iKXCb+v/Fhro3N\nHSXhtVxENOREvLOzyqbeJxuHTGM9p/CtMnaEvmUJRvWdMLgezpOaz3XTMriF\ndNCKC3UrIZ3slJ7L+iiRtanq3d6BOcEBJwpJvgRPcLZ6zBecFe1OpxWr+3/E\nGsxQnADsciuHqlOPswyOfNUQssNoa08Aho6kCPQIVZtCAbUFriIvIAIhFWYH\nFMzg\r\n=7yBX\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.0.tgz","engines":{"node":">= 8.9"},"gitHead":"48d5d7dd42eb07248fcff7cbd97d047ef196fc6f","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.0.0","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.0_1630000833333_0.6067990243843044","host":"s3://npm-registry-packages"}},"3.0.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.1","maintainers":[{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"a82a690be4848e5e56d8dc197cb06477d472f327","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.1.tgz","fileCount":4,"integrity":"sha512-5xNm/PF8oUkUaZd6OBsfrgr1SLkiqCv3++T1kXBB69ZbIbTISFNKFjo4/ELCGJb34yq7s4YuzwExowoWxBlf4A==","signatures":[{"sig":"MEYCIQDc5R3gAdzOawbFkzKGivaihx9stvCpZJZLsRGnDJEydAIhAMJa+YQeQO73VtJbVtZHX7XqHn+fZrAJt0dU+esBWBgj","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22487,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhN4X3CRA9TVsSAnZWagAA83YP/ivIuSqV/jYYbyIdv6k8\nG6N3vfU/hFqWj6z4B28O3Z4ZwwaCI8nDSQts6soiTUfdgkzR4gqQjpNEer4V\nOUpN0Eca5lHzbhmm78f6dafg0FbaXTcVV0r2VcDCAtmZJ/p0Qx1oLtlz5Me6\ng2zi6GOC72f2QlHnUt+tOanq5/ro7f+lXZYlX+ZXsQsCTdv5KCFLOJ2R4dQ7\nahJ9kOyGUK0DKrYN01mAc9gLBiFH2w7z8Ed3GyKkqCfdTrgXFzuInk83fO0Q\nlcjo9P0/rMXYhcZlOIGAiZyzBjwGWQqxmM92O7MD3fW9La04sDn1lvw7Ybnl\nlk7/0KZSsB8A2hlXGFugSLDE0KgAy1QMNcDDqXjKrSE8hKyqBKiiObIcx/tt\n5Q1otnIGPLGakGgGfaqQUWaoqjEt7l8wnGDTI47HYLkJzbrHI5rKx+Jcdwc+\nr7GPykzh3ct5j11QaJl5SqT0NJbrO+IUNrXQmOeF+0wFjJxwoqiYr9zJ2uuZ\nn+QOD635q0XEcmTslHbFVIDR2jVkmVbybxpSQNSk7waGT4+BGtC6sWujYdsZ\nfYN1wmwfRwfWvsebBPaYd8ADPqUR5KFiXRi61QH8qradIK4yeDh+RucY0TSo\nM4otOUjVmaQanFQwA5igesx3Ulh4TxuIM1x7CfubLutBMJhj0CNpeQ3II0dl\n9wGg\r\n=FxtD\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.1.tgz","engines":{"node":">= 8.9"},"gitHead":"bdfa9a4248c4113d07fafff9b4e365419bf0b3e7","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.0.1","@axway/api-builder-project-utils":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.1_1631028727124_0.7975745705794148","host":"s3://npm-registry-packages"}},"3.0.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.2","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"c63ceac992053e75c20fa90dc5675e7f6c2cca7c","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.2.tgz","fileCount":4,"integrity":"sha512-x/ADrAEoFykRgcFEswrbmHPudx949lCRDpQumMS1zPv/ir4T1Q+9VDbI9d3Y4sxADq1v0zpdmtiqd0n4eiWZVA==","signatures":[{"sig":"MEUCIDmTj2mfuGSUf3T5LjKqbPbjd8tCYWNyns9XZedVu4XvAiEA0Y12W42/EUtUB+1fECdpPMji6iXLWyESGegaNIbC39g=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22562},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.2.tgz","engines":{"node":">= 8.9"},"gitHead":"85bd4fbecef09e48652560f456095783c8090671","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.0.1","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.2_1632413588688_0.11361141940799668","host":"s3://npm-registry-packages"}},"3.0.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.3","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"0a012759f1382792ee02282df27f65590893f24a","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.3.tgz","fileCount":4,"integrity":"sha512-IksZp2jg9K0UcIoG7yA0FtFyx9JraT0BIDYDtw4S7jRANwlQilp/nl8+7kJmgGBuSjcmvWzPprqkDDNh//Zsvw==","signatures":[{"sig":"MEUCIQDk3DnDOoXS5VDFhlpml8tXlQGu2JxcyHIjsVQRyo9rlAIgK8qK+LZ1+eYZxAAiF3vbKKO2vA5XpTA9j6Z8D69F0DU=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22597},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.3.tgz","engines":{"node":">= 8.9"},"gitHead":"ec32935c81bc7c2a1e9ff313d401db14ad7116ce","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.0.2","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.3_1633700399951_0.5822171106330318","host":"s3://npm-registry-packages"}},"3.0.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.4","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"2488077bf2ae49e5f5fde3a0192a96e68fc88b21","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.4.tgz","fileCount":4,"integrity":"sha512-vUQKxcdwomQRJpo1sh5InbsRp1/mvPaS4jNWtSu7T+bALqO8cKHsBQtlIlGnlprVV2ktiUP8OWnBMppsTroxdA==","signatures":[{"sig":"MEQCIHNAzjrinQQObc/lwTaVMI599LLFnEWyPAlB34uArenvAiB0Rn3XGFSYGxWMhEdsy4f74FPmhszt10dfRdLgYmjmhg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22710},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.4.tgz","engines":{"node":">= 8.9"},"gitHead":"3b8ea317ac62759beed9c7f42e8a27e9bbdeb61a","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.0.3","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.4_1634741459287_0.3844513337317774","host":"s3://npm-registry-packages"}},"3.0.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.5","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"b5398edf4ee96fb38f66b1ae5838cd575c126f39","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.5.tgz","fileCount":4,"integrity":"sha512-JBfD2ppgo2uYJ5y2X0Iy/qbSRMi046hrXqj6YEnZWiN5CXdS47sO/Js3bje1shpkJDFgPqAQYwrcSi28Q7sydQ==","signatures":[{"sig":"MEQCIAIqPpCTOcnADFCoz8yfKDBcxZvpfdXXAe5fI46SJxxxAiB2TeuLWDiWPhKstAbT1eIl/834v2uM4VXXaQgZfCgHDA==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22829},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.5.tgz","engines":{"node":">= 8.9"},"gitHead":"a81d3499ca6afb2943675a3c71599756cb788ec8","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.0.4","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.5_1636031258188_0.2602016178718114","host":"s3://npm-registry-packages"}},"3.0.6":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.6","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.6","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"87d8af2a06bd1dce5ad7099c9f8eb6d7aba8c572","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.6.tgz","fileCount":4,"integrity":"sha512-Vg+nbmiIU43P0EBvdNM9E3vaUNax8J7P6ex6ty6Wpg1sJLP+c7w8pogE0VXHwGm8cNpqv88ap2oJE9K5vKcwcw==","signatures":[{"sig":"MEYCIQCArblgKUriiSfvZbN8E3jViPu5yu7TOGUmwN9Oy5PHKwIhAO4hG5UR467ysngGQYacMTuB2CpMZzUW0X9M3wfuHpCn","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22904,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhllh+CRA9TVsSAnZWagAAVhEP/iNSzWrltbNoDJGSdMu4\nCb6/5R7fB3G/i28nOGMziLOta045H2fxsUH2H/T58jYrNct7xNJKejrwOyZW\nL1uCIPFaJNHHSvHGXhAy7a+y7o9DPLF4Psj2XSKIFmR5qRrwN5Xb238Inp+V\nB/dB7d6U4eu59myjoevte1ErFagy1GfMfDlhhW0m/dRBO/lk/d4lyqmO5t+K\nHuQA5cZW/HFT7c8kFh2KgfLAAhTpVts9ha79+DPkcg7xMSb5T+MLZ9wq+RaD\nDEQ+5Qt5AyL0QPYzTVBM+zsLlRE7IswIVrML8joqYcgCvM+ATcfp4tGOxpXW\nYLJ08Vu92jhKWsHUy7wsH/3iRsuWS7mM5lEvoF/1cFmaYthwpl6rhNYlLYJc\n9BvakhplAwxWoOgx4MKQA8DR56d59nDYwkydA3wXXHdyIgnqW+Y3npRs7BHK\nYLNdhxiH/aWlIR/2Er+mNSOPGTVRSIZ0vADvoWHTU4dywn3uWr41Vi7oHrau\n9r24J/OgL5QbOIzS2LiGLjqxRZ4iCk7Wov5v9Nc+DYbZsZ6xj0mjUnEKYRZ1\npU6Hu5H4cRGE/HEGOKKJs0RsIkNgtb6X2ALrea4BxlUULV2oFQBKZevQfD31\nmOujEyAE07yEdQG7TMBOo3uPE6jxMBI/uPCQeAh0X9YsCSe4oQh4FhlNdIqY\nqh7g\r\n=PDAc\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.6.tgz","engines":{"node":">= 8.9"},"gitHead":"d3f96462a555a0fda6f68de780be7c75cffd2e21","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.1.0","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.6_1637243006725_0.09097485940595429","host":"s3://npm-registry-packages"}},"3.0.7":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.7","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.7","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"f9e474bb4cde1f1b5e4da6226697b3d7fbd17b32","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.7.tgz","fileCount":4,"integrity":"sha512-QDe8hsCyKG9Wd8D5EO31bXyU7vM8EoJmvMRCwW/A3riIMXFZBkzJZsxcKaUl6saZIbNX3lDwMAclGKxZT5thTw==","signatures":[{"sig":"MEUCIQDgQ+R/jABbmdogAHlxLMZvs9KbSGt4idy0yl/AyM6+tgIgHZ9PtQEccDRhIORFUQXWePuG5Rfjbvzh+tqB8E/L9Qc=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":22952,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhngO1CRA9TVsSAnZWagAAjkEP/R3IF8QYP2zUFCVBKMFa\nB2lI259JnE4bIFYLiXTIomqLU2dwh9VuhKVRaRTr1dyankuHjDPa/+mVWqYj\ntaIVL/9Qrc2/sHCGFkPRI81H2BAmDDxef1Ft7U0iefN2UbIN3lhz3YcDTqkB\n9J/68U2sAH1BhKpTC/wjhQSvDP3vPBg6KM6b4nWkNcDak7ZzZA4HGlI4IcCi\nfhI09n71lsYxd4bsfo/dqeQz/zEqFt7jSPob61S7Sord6Lg8IFa7lm/+bJwg\nmZ0iz0kSf+gM9AdDvHTXojGp7Xg6UHau3JR5i/wYXGa5c4VTQCaU282EKTXs\nDauDBgnR447src9kGXytsWkBuILJRYHYXyovhXHjm7LVctqyBDYahJYBOGtl\nvek/ws8262mXWmUDcWoKgZ2BKHErLgoS3Wo7JJ4zo0/f+1+a0p9/fhiUaupR\nvm42XULtT7gu/+Im+htc4qZ/EUQavfzM134LH6OJjfbcw0fF6HQiFqDNGEml\ncWAHicNWPWtV7BrzmJPQjk2lF8ojF94VPPYohjXCnH4u5Ph7qEW7GqiIhvR/\nNZLGSttf/+z3uvCE+dWFi2yNvcAT3pgcq1XUDYe+LOpZUKlat4pjN4Gwc+Jt\nJVPEOUTRe6gtqFVFKXujTiyAkHeEn799jcfpG42mwuQJgBDfEQEAsp1eQL5I\nAoJh\r\n=/e0R\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.7.tgz","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"103d4a2bda47fe50b46555032f8776fca4ef77f8","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.1.0","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.7_1637745589066_0.32372190684578417","host":"s3://npm-registry-packages"}},"3.0.8-rdpp-7123-5cfec9.0.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.8-rdpp-7123-5cfec9.0.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.8-rdpp-7123-5cfec9.0.0","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"bf0d695d3ea10f9f7e21c8c90c65be2821f621ef","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.8-rdpp-7123-5cfec9.0.0.tgz","fileCount":4,"integrity":"sha512-4q2/kD0RMB1a8y9DmIGD7LdtuSejpbQkp/98gIAY5cKWUqkovnL0hDLFEoTRa/0LBK/akQot1PuRTyNKolJIYQ==","signatures":[{"sig":"MEYCIQDlT7Ccf5uXqPtGHzzSLT23M8QNdyhL8yBAzTPmxOZT9wIhAPG3+uNBSimwJ3foJFagiGUMlIwr/taJyK+NLXs/ECQN","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23069,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhp3MGCRA9TVsSAnZWagAAFnwQAJd0ZTGWWvkf2++c/I1q\nuxUsyHhDf8C01vF1i3Gz/8D7yMKw515Kh1ZAjGP4fn5cRdhuVVEfElRbY3rk\nOb5r6OH1Iv9vn0+cY3ZbFmDHLrvNBTpvK7H7kGR9t02eUbf1BeiEhLnyEm/h\nHaZ0pGPseLwd2TqlJ3fcMedhoX3iOrgKf/xB0i9mMd0ysla4jpRXdcK6taYO\nmHwRj5TX5HQ6/U08cZA2KulMuWvlytRHyCmPhL/VRRy3e3KrhEVg3Gllbi8X\n3GzvVLDM2qRpfYUrEhOCqXXS0bXHNV5IjMR6AFWMtEf2m3EpUSRqz10hb+CO\n5oO9cfGHCNLhn6NFxDVIHHau36oygfF5HGjbsli0d1kyI5lbNYdzTbHT4dNU\n9pV+MN2+NInWjbqc3hwlN/sEw5KGbz6qt4Y+6k1qAS68mfD9EqL55WAxRRTW\naJHtlhiq6Rl/cENCKC94dqTwxPCYAAVg4SM8BhtnswjnLjUjT4chnhNYyMta\n8VtxNF0doS/z47JQa3/V/mHvT9vSILxM7QqcGqfih0bejOW5/5or27XukExq\nuHXyduOsVW5hc8DmgS+ZzQySozxT9ybpmafeu9bpAHQAyRe73kXViSeozO8A\nC51DcCBEk1cPJ5rBt8a6Wt2TY2ACxVWe8LFKU5l4iVBvQ6IDGCjJu7W3mxy1\nWK03\r\n=SEVI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.8-rdpp-7123-5cfec9.0.0.tgz","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.0.8\n- #7123: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"5cfec96bee23d4110d38044ee7821668adb21c88","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.1.1-rdpp-7123-5cfec9.0.0","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.8-rdpp-7123-5cfec9.0.0_1638363910658_0.26113269047306265","host":"s3://npm-registry-packages"}},"3.0.8":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.8","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.8","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"6695d38e27521f83324f0acec55ef6b93b55621b","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.8.tgz","fileCount":4,"integrity":"sha512-OR9kzmA6DdHX8VmbEWlMPT904pRtwoytjr0LbrPyj6+Aqosg9ac0urDW82Szy/DqASlP4v+2yzRsVyvARSHVeA==","signatures":[{"sig":"MEUCIQCD6kcAKZNvoyasi6+M/oNxPiC1xxP75b8Btsw7JeG/lAIgHyEuxUmPnDgXHxkRuMmnQXf9ffjLedd79voZRjmX/LA=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23027,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhp3MMCRA9TVsSAnZWagAAXRwQAISnvVzn1b+ypBDeumsT\n/vetDIO5FWDwsNKCGS6O5xTCy0gxl+dvyn2mP5klDknrOtLR4eBGfD4WndIY\nTOLAf/PVvRT9kFlK+N6TQvldfmEREITg0RA2eo+7w87LhOP9EerZSUYn7bZ6\n1xf/1JeNNLN56+62Y/Q403Ac820+YlDnin+oN7UMwp5LAV7g2zVWzl1XiwAb\nUh3cJ+NCtPBlaOOjsF6LISdVjb+w8OVJDBrqBxdNzILF/T4Incnbm7HEbvUZ\nC4SmieWanOoWpgw+LpQnyH7BwqHEBMn6L1KwJfPIrRjg9GF0YBlkBbxkqzqV\nRpaCtESt+4Bncf6W2gwpIS4srR4dB94WHKMA1+tIPX55Ldjh8FaPVzw01QFb\nVitfhv0fnPOv+2QWQAiY/8IYL4tXQmSQHqT8qBuvApNs3Geb4I1z70ExxEvG\n2/Dt7nAm1M61IdBEONLX/6hlFwAe4kJubsd1VqHLd8VnPhTpajZSpV/JfjRB\ngnj8E14hSTbVzw9IfO+mg8mt+AATzDpF8WfonOAaF0jZ3FsxVkl9M8pr6FJ5\nOu5ZwyNbGOWkXsppa4YwT+YpOq3YX+/5yoqiwg1VbQOlMDxCNXEXA10d/0Ez\nwnSHWJi1h+HIPo/vwGoVczZi/aByZa1cIflF/kkhKD7R3obYJHujSaQdyDZG\nXHO5\r\n=GP6t\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.8.tgz","engines":{"node":">= 8.9"},"gitHead":"698326d884f00b27d465847518201a470263ace4","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.1.1","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.8_1638363916408_0.8677401751435099","host":"s3://npm-registry-packages"}},"3.0.9":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.9","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.9","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"c5a05715fc52e9a20dd31659d39a29a100e702b6","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.9.tgz","fileCount":4,"integrity":"sha512-y80mNtvoGINd3dIJLN9NkS9HcEReW8Hde0t7dK8CdXRKwpsVDuMypPByUNk5k807uqtYkpGU2HTzBPHuockcnQ==","signatures":[{"sig":"MEQCIC0gem/wDp+c/BoadgnIPljiyxJ8rt/IudZ+7biuDdhWAiB/pHAPyXcozyksG2W2hXtXIaAAv/P9gTtBzqX/qBCnZg==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23379,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhu7RWCRA9TVsSAnZWagAACgcP/19RwOdAADCZXkr4ucsD\nz63ZqAyuuG3QmqezcJIu0QV6S6keaf/WFDDX8bK4DfRN2WXKZOs/IM+J2XlQ\nV1bQsWCOl/kGjMa8r26ma+2QxSkOfsKrj6fUjITiYa1tJSSUzDz6tyCLtZyk\nRgHyXA29wVtZcU3qODi3dR5IvJiwJ4UigEvlvKyo4mtJgWbs+K4ZWwmQpUgI\n+lxPfuoNOw2KsyOi01uvCVNMttRTG6scPolWV2XeCGvcrA/KshwHjbHlQzsY\nqnYccuJ3rehiqqHSRzVTeSiLLlN8uuGJ++igO+pPvjkft7cfRVn1eLZLLB9h\nnolW4qyofjsAVBZHaLmP3vnZdq2n9BI1fGT5wxNGsiFxEoMapPFgY+/9vUf1\nVh8qhxP1ZL8asMMbwaZYggERzlD9YOoXBdA5oJ1Ggjjnbr4qX20X133f9Ky/\nFfQYcq3ehkMHL3au07laMFN3e3EF72WLeqpsxyJUBWSVUYGmdCiLFr/r/kS1\nccg/1LMKe69eyIA41bg8AsfdtGB5Nw11JywyimvmOMbm792KAPjStPiH5FBm\n3Xs/4O9FqXw0Vi04nT6Jv7C0LU6XvRsAdMqHpgI8j3UujiRuufzgqJ4HZWjF\nkJqLkxuAM3MLiyGX+m3f7f3w7yhz2CVfqzN+f6fkHJ7VRgbm7IIidUl9p4bK\npbPn\r\n=WB7G\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.9.tgz","engines":{"node":">= 8.9"},"gitHead":"d51fc4c58de56fad7eca75f05eb0d938c654ead0","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.2.0","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.9_1639691349921_0.4389901174634887","host":"s3://npm-registry-packages"}},"3.0.10":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.0.10","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.0.10","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"8b747011f3122ffbaff636a45dec3e857553cb64","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.0.10.tgz","fileCount":4,"integrity":"sha512-Q7G76dSoc3BVG4LF5lxxV0X7i4CRVMYefL76i4MIzeSWeeaZBvy4H6096E4lwv7UdJy6MFv+iohquaFUtim7Tg==","signatures":[{"sig":"MEUCIGLb2/xwSqVX/XlsC1xJiyX6Xlv5xG/zrdGBe0zHWdS9AiEAvj9dp3g+nR+m5u0Tin6S+Ej6WsFhLQc3rIKNwvIHj1w=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23424,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJh3ZY0CRA9TVsSAnZWagAAl5wP/AllMScIAGasDPIj4uxe\ncWnFDfWsMS4eAOQzOc3mq7jYLqBq4wwBGQEA77OEa9U/wk6PTVcbhINSUvlQ\nHdw5QdH2nzg8nAnoc82ebJYpPT54tzQqMYLIpFDKbxbQ2DSGyEWp8Sp/KuLA\nl9LBa504nuGkcSlXFIjQaUCTtVi4LtTPSNCPr51bFx86eABUDFqjgapeNsd3\nqD40pf5mbQFXf4Af8UYCWCBjN2MKbHH0AZoIk3IYWmkrRzzJpjfsP6Wg1IvT\npqb0aX+sybN0Vsw0NgubS1vAGz8cEX+uLQIQNrsJwwdTpMS2pdwnQp7nXKYF\n+kGwqWAv0MG8DOsxdmc8kxoND2UmXKSXIxl99zk+9We+6S/Vn6HzZQNJu4SF\nmbjjcKWbkKvnE23nQCYy9b683VDb7Uz7rXHAj0TwP0GWujNw4zgSfQZFX2/B\nCKcJd6ynrIa4r/24Udj51hArsElYpYFKMIrUfx1B5oe8nvVjdi1UT1ES+7kg\noYj+BKuozbWbI66gNdnyxuQYjNbyjsYWXr77r+OgUnLhCdv44kqv5pZQi0GE\nX102K8BAKQOIAIJrImyBcPSqxNbX4T679vCjyDm8FUPvN4J2UqEXC45EycG9\n8+8OqF7vw8XpzJlLmZiWZ7Y704wSuWkqXBdBREDZNhICjcntrnrXubBmPiNE\n6W2a\r\n=zDRq\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.0.10.tgz","engines":{"node":">= 8.9"},"gitHead":"5577b63acbf5baad1d7c221292628b7522f0fd75","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.13.4","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"8.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.2.1","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.0.10_1641911860225_0.34932821363429456","host":"s3://npm-registry-packages"}},"3.1.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.1.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.1.0","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"f41f18dcb3f576ff55eaeb32b23c1298055d1b3e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.1.0.tgz","fileCount":4,"integrity":"sha512-8ZEtPA6l/NBVR4YV2n3nCHIoXt3oNK033ASUZ0itZiBmNmjp671tHEe9YjtMZbQOm5wWlm24WBjPq9o6Cu0NAQ==","signatures":[{"sig":"MEUCIFBaeP1IR2Ve6Q/NyKUmSIchP+yvSLhmHzRsYabW5GiYAiEA7WF2KgiX1yrrHjcSmdTh1XaNqy3TmUxudSMNt3niizw=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23498,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiD1b8ACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmrM6A//f8+BWJY3k9lBc4DBba03xehbx31h9KvuKSlTGU03Oa084U1X\r\ngL2ok0lD6y/UcVSokLawVthXJV2x3k3mjhmG2MFq/sKNTCUxT4bu0IbUcEV9\r\nfw90jLgNJQWf+C3/If3ZOHu9qo+YBwA+b1O8souwbhpWSEfUSEE0r/fwHVPd\r\nIbFFR8vFeMRZBrHO6s8AAVSK3lWrhT1TyFbM1W4RTdUletcZDiHM3/W+ENKD\r\nI8K73T3UzQx1fHakjljJ/9neeGzuqlinF8jyE8F1hxsWeuCwaGw99JVSnVa4\r\nUiSlHfznpnV4EmWdS/kBkNu6JrjaNxlPia1J3QIyvX1K/rb47bRSNPeAEHzr\r\nOLlkd08YwbrLdkIS5AvIhQLoQyXyWHaysftP05GDbQg9SH8u8AMXVIlFQuIx\r\nb5AsNCs2bD69h1Orki4cqF0vFmBgdejP6p7LSiJOQ4vki7bYnja0MU+1oK21\r\nNdKfPLoDB7WkHgGnoayvhnStt0LXJDFP7XVHM6g9u6nrEYr1oTyci+Y0MU42\r\nNDKlEzBP2ooC6aGAhbTy/dgAywQDI3Mx29sAGG8uNeQkB9HOLpaC1nv1veDd\r\n/xkPztkZhviaDK0YukH7B/V42RiSPr3N9CEZBGsx5AWY35FGGHEgPmLD/ccP\r\nfrThYz1FHASpnLaa57R7XkwQq/7NBwb9+9U=\r\n=dvL6\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.1.0.tgz","engines":{"node":">= 8.9"},"gitHead":"e15235c9f1bb9dde1a551c1fbf062179b555eaf1","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.14.16","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"14.19.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.3.0","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.1.0_1645172476447_0.3085566617445856","host":"s3://npm-registry-packages"}},"3.1.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.1.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.1.1","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"5abc9683fc77972b2f8de77304fa43a459ed2e31","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.1.1.tgz","fileCount":4,"integrity":"sha512-wuGInI6nmIbRVgmLGD5cHXw6nKyKRYbKapeMAuDMQ2XnBbyVXsoF6PmsfrUfdffXXWGXcLtNDzU/FACt2417iw==","signatures":[{"sig":"MEYCIQCaRVNAsC89k6gwiBCJMFdbUGMJVINAmyIvmNvYTuFKhAIhAJRHYv4kut9iOfMfG7Vq9RXFD1DDG96cUpNoiiuJ4qQu","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23573,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiIfTeACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmqD3A/+NrmHreOICaDXAu9NXwoR6V3zsC/k89cYIqboy5v3s1+a6RLB\r\nhoA5nLgnJ51iJl2ScadTiyG6p2C+Ql5gqRjfuDItfbrYdqSmhHIC2qT7x8zd\r\nmHBnv3Pp3Zi4l6JVQZhbk8CHFUlNUijVLFaIZXYInumJd0hJunAgsZojzNnT\r\nhehSsmjG+dH84bM52XAjumorQ5wW9BKjelmu/ZCHiJY4PjizWMsKa/gBojRd\r\nBOhqsAQXl8pc/vEbhX4jyqGRAXo5523SiqWWSOSvVOfi9m/ELPGS0flecGJH\r\ngR1c1ociDwzIAoKIy3rX4NJr9GYXEMtUcSasDr7c9iitzNvpiWGdXax6BBnc\r\nmWqipPvVGg5+0sXSrYHAku6b3jXQySp/yz5iadFdm/WwJJBGp8Dkgy3UbgBG\r\niKhfGFDA1DdEhBRNIU4UrTQV1mJDC6z2nW5NUZ/zOBWGpo1mvwI3alDCeV5I\r\nwB37okMdQoPVI7f3XQIUIOAdxGvDUQB25BgFxyNtgt7sAJBC6vMAsbu57BmU\r\nsXLr0Oz9SITm0VmZqSqicyl10hW4OIbzeR2YKQ0ejHwqH8zA/LXcm9yxcLmv\r\nfORdOB/p0QlNgAubVfineFF5ARHspjgbLi1g2a67M6BLMXkqtSxtOLT4DLHj\r\nefVvYcUqYdXVTgsLU4DQjXrPmYWR6JmZHc4=\r\n=9Vyg\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.1.1.tgz","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.1.1\n- #7303: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.0\n- #7282: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.10\n- #7111: Internal refactoring.\n\n#### 3.0.9\n- #7155: Update `@axway/api-builder-oas-flow-node` dependency.\n- #7155: Fixed issue with [CVE-2021-3918](https://nvd.nist.gov/vuln/detail/CVE-2021-3918) and removed the dependency on the `request` library.\n- #7155: Fixed an issue where the 'Authorization' header could not be unset (i.e. it was set to `null` in the Advanced HTTP Options).\n\n#### 3.0.8\n- #7123: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"0427806466358108d265ad0851105230271fcd80","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.14.16","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"14.19.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.4.0","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.1.1_1646392542305_0.8519476544901099","host":"s3://npm-registry-packages"}},"3.1.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.1.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.1.2","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"0afc46d2c07d0e1ef4ee2e7d25bd549f49978475","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.1.2.tgz","fileCount":4,"integrity":"sha512-EuLGRDZx0DZbJQbe8SJ1g/Gs0SifyMVKAlgCLbdPmj5F/uOHqw/ktSAiM9XAsjlKBp7gT6YyTjX54j2iQSf2Bg==","signatures":[{"sig":"MEUCIQDlkyTjFMW9wTUAA1lfektwAxHisFStje4ePtcmEDMOMAIgP2O17jO4Z6OKK2myaE36nlfRRCTBlEDDZFIhy19FfW4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23648,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiJd8wACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmrM9A//X2/DKCANP+T3d5lrf0XDi7JTpkXnsfWebLuyFK45MdJ35Mlc\r\nblqRZqht69lwFeyirrp94VWHsoDk/UoEv5F6pskPDdiZRj3c+jhESq+O1kxe\r\nVPCP0RdSCaXspj5Ou17Kl3SbOe2luzQbDue/CypTfB7EgbI3tnb+G8NrGPDW\r\nce4Z5n4L3GlZsTi47nN9prCuft1iDbicEKyFzU/y75vHHUqbTS0wm1I8r64W\r\nx+o4g2FL1iQTDd0Doc9NtcKy2BJjJQi6bj7/CEtiwrY5QlwWfWMok4M6QwOM\r\n/nb24DthK8bM1vsWt+A2tux51lJaDmL8mtXccnxwm/YXoZGAdqBIXqXP0rv0\r\n6iH3Zp+HYRAl80CdQUC5eIqeSj3KbyWDMx1u4W3VN44q+ayl1oQA77QL1UQt\r\n1XjY7yEDmgKJBx2BqyM1sBpNwRs4WfFf0H/QOCzeElGePp115ck5dOmDDTpd\r\nyJFGboqWkgSjHL/1fYYQ8570mUPwbnS28Q5OaePmcbGdPz3rGp9MONYcWoa0\r\nxUvhcoRy1XQmL8vn8d0Awk8L7fW1R+baDEwRtEjHyfndpbMMlP+HJSP3M+zH\r\nHz8tmggbypc7fdw73b5BDBAPlQ7zy4ukn2v/0ZGojU/wjG6hvUYxYM2rZCRl\r\ndJS6IXhYly2Uq8qb8HE/LCFgFlwwoAWBRdw=\r\n=+R0n\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.1.2.tgz","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.1.2\n- #7284: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.1\n- #7303: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.0\n- #7282: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.10\n- #7111: Internal refactoring.\n\n#### 3.0.9\n- #7155: Update `@axway/api-builder-oas-flow-node` dependency.\n- #7155: Fixed issue with [CVE-2021-3918](https://nvd.nist.gov/vuln/detail/CVE-2021-3918) and removed the dependency on the `request` library.\n- #7155: Fixed an issue where the 'Authorization' header could not be unset (i.e. it was set to `null` in the Advanced HTTP Options).\n\n#### 3.0.8\n- #7123: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9"},"gitHead":"825fac958f7940b12737f74a224ef98204edaa40","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.14.16","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"14.19.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.5.0","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.1.2_1646649136480_0.2648531962373586","host":"s3://npm-registry-packages"}},"3.1.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.1.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.1.3","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"c876545bc7268b926bc402238c49f2b21e1b0c0c","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.1.3.tgz","fileCount":4,"integrity":"sha512-aok+b0r9HfyAMqikZNXitt4WkSSIt+M5Ixq0yrX9t0NhDvE+Ty1VgVp4mI3MQ8Dj3faQk2dYPVhJdnoqxPwHKQ==","signatures":[{"sig":"MEYCIQC6ildfhLuaqOStZjzpcuuJWqoXRUiwcTJMSg/0YadgbQIhAPGPSfBH+DZa9bBRp2blstsZ4fai3FFbFd2ZRtkbggVs","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23723,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiKMf5ACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2Vmp7ahAAh/NMZJCmIU1gIkwwM+8WXrn6fTZg3ErCX4SQqHDRiRv/1xyw\r\nkFIoc4gEGyOpTLW/EcW25OYnYxdmOZvwfx31vZE4apWfbTOe6FtjJW7OOCGh\r\nuuitxADWsXNe3WUelcByw0hw7gMbxzeLz0kY0W6OAsR2+wED2MBLXcRqjyQ5\r\nlz/fFRJplf1S/OT5txgSm0lAa5C3ZAIq6jY2w3eQOSbmleRTACACtUAxan6q\r\nS+toswrT4Kl42XsArrt8hhRLh+NJJCUip2Jk/W8060+FZYJdCGWdHdUC3Zq9\r\n+tpGg6f6nqewfxHXm2YfQlz61HbIQB4p5cwP/wCVFr8WSnHLSsjv8IKsCV6z\r\nMDVNPAcaaLIt6D2++WXgheviwJK0VTD0XRE9K6+HXkCPsQSSmyjojYk+txlP\r\nAzSwyTkAUyCTEVCVtq1WnChDhYGic9+XSNSgp7gh6TcWJsQvIoVIiwhs7Nxe\r\nLp0rSwIEqWFUOFPO61I3YSy7Yns1TlQMJxBmXxpbDmgnRMe+ivXUXcYzlHHO\r\ntP9dIonwFLQSHPYeTXOOIRIn9uY9HnNiNX3XJgTf6YAHiaSbWS46E9vBCGxY\r\nFEGSSXy2YjAJYDmDQM3huXz5qC9N9aEfqyy9ZkGDHfG0WZ/Vufci2y01hOoq\r\nOk9O0/NKvJ+NyruPd7tbEQ0kCzSw+QTeIE8=\r\n=E5TM\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.1.3.tgz","engines":{"node":">= 8.9"},"gitHead":"6ebedead249f7572c87bb881538ed180b6d91f05","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.14.16","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"14.19.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.5.1","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"peerDependencies":{"@axway/api-builder-runtime":"^4.69.0"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.1.3_1646839801366_0.5944075627990588","host":"s3://npm-registry-packages"}},"3.2.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.0","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"066ab4a41012dd6e5e76a4c3d0dc8fe1fadea20d","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.0.tgz","fileCount":4,"integrity":"sha512-3AYbflJb/EPJY1XrVeknfvKAT6+U9jzH4QY4G66UmsXKmGxKPvlmKGKIgECCluf3FxyHUx0b/yfeA8giZ86vpw==","signatures":[{"sig":"MEUCIQDHbJm8PgMUkC5rBn1M4eGJatOImyKoQVekvENL9gBHMgIgUFXQJ08p8UJqbgO3xzAl/028epEcXpoo+67XNrZ/tpE=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23784,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiTdURACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmpNehAAiD2gtqzhSh2eICxL6/d4YIBnirdrOPBL0FTl0D5GKdPw9D5K\r\n4y2z6peQtU9vW2i7DnAK1uQFi5q1bA6FjTlZipzXACoHqdIgVm3p1yUiS2Xs\r\nEjjaykCtT8bbkq0RY1eVWvUGM9Wo4s21kK/WnltxN+g3xhMY7q3MCxFuckun\r\nQe3Kw/a7KJJ1pPlrrV1TNFxXtSddP2G504BNIDtcQ2jnQ2OJUUA7bDSxsa7g\r\ndXO3CApXnbFwCPGxV/Jqixx7Yw5ZFwIDr24jqKocF7mW3BLWRUa/e20rVYbU\r\nhBeHIzURRtz9QhDNeadNj4qSpDzc5BxOvHeywLoCBPcQ+XKC6sdV7Glj/c3A\r\nMAoREu7CK43vk7T4XS2EHs8TX5GXT4jTYiuHupJoKAknodLUejN7gQseS9+0\r\nMCqGqsV5rauofxmdYfNwuyDxIPgWw2L0mx45/ZY/EjOMX+h4589R5st0w48D\r\nEOp+dJUJDODpic92bh1yNY0PGlJsZUrS+4u2/rB+vftVhfzmmFohD8fBK4n5\r\nlH/Jqx4i1VfQhILUo9FwQtCDCth8CpILoq9gVzNS07ZNiv/RrOEX9H0418fQ\r\nNKg3bAFdKIzB0rCX4zSIRQ8TWb4PLeEcQyTPThOahNHj2342910B6vX5pZFQ\r\nkntp+kTvoOkYuI6C8yR8tYXYxDm8sW97TBw=\r\n=yzQN\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.2.0.tgz","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.2.0\n- #6933: Replace peerDependency on @axway/api-builder-runtime with `engines.apibuilder`.\n\n#### 3.1.3\n- #7139: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.2\n- #7284: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.1\n- #7303: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.0\n- #7282: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.10\n- #7111: Internal refactoring.\n\n#### 3.0.9\n- #7155: Update `@axway/api-builder-oas-flow-node` dependency.\n- #7155: Fixed issue with [CVE-2021-3918](https://nvd.nist.gov/vuln/detail/CVE-2021-3918) and removed the dependency on the `request` library.\n- #7155: Fixed an issue where the 'Authorization' header could not be unset (i.e. it was set to `null` in the Advanced HTTP Options).\n\n#### 3.0.8\n- #7123: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"8cb351825976a95bd2aae73e1cdf0ee69ecd3170","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.14.16","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"14.19.1","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.0","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"readmeFilename":"README.md","devDependencies":{"fs-extra":"^8.0.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.0_1649267984995_0.245227027181248","host":"s3://npm-registry-packages"}},"3.2.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.1","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"95f113f39023d07eb5bfe7863b3bf19d0e955673","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.1.tgz","fileCount":4,"integrity":"sha512-EZuoR4TWMY5+H7EcL5r9VihCcGE1HTNhm9O5AR3UnTW83M8Qi98J9/Kye6bizBjZmG5SU93WY1GSpHsrMXsufQ==","signatures":[{"sig":"MEUCIQDih7jwG+rtOUcPkOT94/2EYdVTE05Zs4w4TqpRyt2+KwIgVBXzMFYWZiPSZYhLaXEsH3mcYXZd31R7ZP7ourBaepQ=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23831,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiTwevACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmrUpg//ehtQ+ZhVDnwMw7raJ8Kq93teBwNmwJx9M/knvGOu3Bgy9w6h\r\nE1LGI6eOTMmn6/egzZdaFzDt5hK9Qer53GZhjBZm2V1n6WCKtLP9bBtxRwri\r\nomMwzpPuJdXDdLceqgEVK7vexmhpmeBzmizcZaX8VCSSlO8s2CgZTljbhdFC\r\nsBXFu9zZ9OvB+eQ7kUNXIOCYUVMDnUCkj6hQyqLGnOT/5xpZARxdFvaoLlza\r\nbQ2FEagE5OBa5taA5OGw4edXxZSak9DQ/Zhz93Hr91CxlkRkOm8I+Nt8w8PV\r\n/DzuQHdOkFtc3rbuFDVbJ5B7rQmNYfToE1Dw5gNRD6bBPDx9u7uXqOb/v5P9\r\nQl5sOhwRLhljm18wlRp3zSXh5cJwtxQSjMFCX5NgCHSx/HlIDVhAB12g9K1o\r\nh5k6tVmcHVmh1kyGZhEAVY+BKwYzJegBMccINdDYi7Abs+gQl2NRTSudKrHT\r\na+H19xFH9RIWp1l59f8Zzv5e3PbUD/WkL6jpYnTEdVBvKePVDqhmfSrJr7A7\r\neSaJWGS5PHUomcDvrBRXVVgqTLGq1LqAewoUvd/701v8RhPtcJ1Oe+8DSd6i\r\nn19NgJf4Vu6J6KmPt/SC6iABZMkZ/iUf6XiHk65BZNz7lE+5hXLWVpA0A8DU\r\nMGjRkUGK43tkF3KySxJldA/xhbgkvg+SRtc=\r\n=RsPe\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.2.1.tgz","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"631ce0a3ec268870d363ac6f39dd02c76fc023fb","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.14.16","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"14.19.1","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.1","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.1_1649346479215_0.4122555435763484","host":"s3://npm-registry-packages"}},"3.2.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.2","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.2","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"840261e4f5890cf984638c47968818be9f59381e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.2.tgz","fileCount":4,"integrity":"sha512-yZZgAEso6xxD7ksJnPOyDag+puFZga8GRlF+7Zs+LfKR1X0GgvRmKyEfU4QSXzEXuhJeY1nRXGioXt32E6JHgA==","signatures":[{"sig":"MEUCIQCdNJ+HVWzou414LkOgTqJYJ2M9rP7QK86lhyKznCQj3QIgceCQrpYpxOPiMGr6LEYMeRkfasv1e+ElPc6Ej9gZwwM=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23934,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJig5lVACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmqwEA//TQgvpg8T8rw4OMaMoyo75VKTkIYSEH/9AfZMqefLjX8XX1yh\r\nJYN6n5kNEePLJvYCYv6KaW3yiXvUBRa/WAQ2m74IU77dbwWpEyeXY0dGvKRr\r\nyhjEwrWbzLoNwLzw8KTOY26VXr2+jysVOSbRJ2iEP4fcE8KAFJeqpKeEDV48\r\noRhqT6vIYjUWBU1oXQPGzbC4zhUyIRgLAR8YizNDRcntQIAsYuHWKKcxdJ0J\r\nx7SWp6PLT6Fcx79s84jFWs8yKGapE8YjCSgVPoVvB7CpE2EpnGFxp5iS0Isy\r\nKk1T+o1N2YIV6f1k1CEwaBWKiWLt0p94JOCKpq0GkMq1X1SY/fcCqzZrgWPg\r\n466/pmGIBoRBlzCYhfyB8VnyM69dI1L1c9Q6ntuL5pxjCHDnwTclyMyrKNEz\r\nEoKWWnfNvX3fckWGYlXOBpwWmijJRyODgZy87w9S3ksnXcMW8mYTeb87l/8X\r\nS2qH5DnrnmueAqHSp+kUDw6p6dHrKvUszaW4Iz4QIEXYpT0s+7w0nqPy6Dg8\r\n9Osp8lYHgbnwA2BFPF/VR+xnDv64Xhl8BKVv4EIaBq7fPJz2HtcZw0ucFSTO\r\nmfHsh+qmEpBJ4NF30dmILBlCTovpjSVCODpXD9iz/8gn5XFe4TI5iWPkVcEq\r\ntLCqslVYr3vRdA40nXfOYNCLiFWXndcl1vk=\r\n=TrCV\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.2.2.tgz","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"60b5bda030e5d6cdd19dc7d67653a79311970a5f","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"","_integrity":"","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"6.14.16","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"14.19.1","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.2","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.2_1652791636821_0.14272603436749565","host":"s3://npm-registry-packages"}},"3.2.3":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.3","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.3","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"0f958e3b1e98c7f6680fae9c19541bdafb27b130","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.3.tgz","fileCount":4,"integrity":"sha512-4CRHwHPyCGZG7AcMYxZy4d+pf8JXDiYH5kHv5871yuOO8xmFIta50JcUntD+8eOAIdLNjLvlfXCgUGH4LjGJEA==","signatures":[{"sig":"MEUCIQCW5YplYgaor2PoPwvMKZGqPXw+UlipEpN0UNE2WMksgAIgflYfkZUWT0O1PuhupDzqNUN9xPnY/cOR4tLaQnBi4qk=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23970,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiqKgjACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmqYVw/+K/hod0MVvWJ9YLjVegPNIjbBGYvj5RBBGYXeXdALgnHHoeNw\r\nZRI9iBxTWc/eZEITxFnyCOqXT9od0ZM6tUMl7rnF2QjGanKt+yf6VA/9hC2V\r\nkUQchqrqevqHBHq6ZGMFkPOhUWE+XFqDoyfYYi5wrvOSrubgrSdFZgtEFtqr\r\n2nf1XCDoqvCbkJkgSi6xXxFzikRSQNYeUEqDA3XkKr6PRW/w63NCczfy9GSS\r\nVZH+xDYHCJMQNwTdaV/zEDgtjKIlHdGzphQoYp31fOzQRDyAZH+DJgruTBL1\r\n93a1621SB+hLrWd8ZRgdAodFjr6C6QT7FvaCjJhQ9/9o8HoRKAleUtzx1ISs\r\nNW+EW2Xoo8+kyuqklihcrclcgr6k54gu+/ccUQ44ky9M+LaTlm5+K+LnXon3\r\nI3wYZHBpJTXdWDZJpPfkG5S6FGBvtF1Aw4ETfMaCYAGq7pMdjr6DPQie0xPV\r\nhmMwzC+z3j2s2UHqQHAYoul8TfD0aVGr1CzKSIRX0d7bwgxBEPGBMb6aUNbt\r\n3uqQgqFz3BdrTJtYDL3AheGN1NIubfbmDPpLhn/zbbt6vi+FFH0rfWGyTPmf\r\nytsbEH9/FBlma434TWqDxwZ0mMHyV8t5jhApFsjWWMZHlBcUNoXFu75KYsqt\r\nWC65GKCIZCTjLYaIFzFvRW/ptSzbKYJCMgY=\r\n=RHCD\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.2.3.tgz","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"601d7a5e9e0216efe22ad4b80c406785a636c6e8","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_resolved":"/builds/amplify/api-builder-plugins/published/@axway/api-builder-plugin-fn-swagger@3.2.3.tgz","_integrity":"sha512-4CRHwHPyCGZG7AcMYxZy4d+pf8JXDiYH5kHv5871yuOO8xmFIta50JcUntD+8eOAIdLNjLvlfXCgUGH4LjGJEA==","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"8.11.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.15.1","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.3","@axway/api-builder-project-utils":"^2.0.0"},"_hasShrinkwrap":false,"devDependencies":{"fs-extra":"^8.0.1"},"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.3_1655220259739_0.567957912560936","host":"s3://npm-registry-packages"}},"3.2.4":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.4","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.4","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov@axway.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"4a61d7fdfe168d9f5e012b6866b8f5ceb0947477","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.4.tgz","fileCount":4,"integrity":"sha512-FZP/anzuXrIWGRFFAqxRVM7XLY/Pth5ERcdiISL5mtVXICs63UZygejTNtkRjo8ORdUCQwux0g9NzYmIH29JiQ==","signatures":[{"sig":"MEYCIQDbhRGsiSsu3Fri2abMeVNrcnHdbN1jCO3IdH/Wkrk9aQIhAMdbQFwzAbfXhSbA28f3EXKW998fixCKfsXmGoDUDCng","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":23968,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJisIn4ACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2Vmq1jg//VruwnHQBPpXepYZT0uCAPofxJGvNOjH77D/4DdC2S6GlclFl\r\nLC/75sY+CXVcD8TCtVZb6q9aSWU3nvq+LEsbI+7owjGiilaTZ5P0g0FKTTr0\r\nWqiKSGKObhTjIm8BgBFQ1ZcySeJxCSyKUt1g3yhBVAAMXFGqIfpnknk+i+0W\r\nnaOwBiXO4YM/r2qco9tCoseZ/lb9mfMiGc3vXw/xxyHxk1Hq14HaK38zNyM5\r\nerBsnsHtFz75r4HwobRDJLKROAGZBbDaJVt3qejdLwD5/78Oa4x+ZSCIlPvN\r\nkUUw4N31Xg+JV3BHpjRdtFihW/BU/uTDHPlRTlegO0ArXwKiQX49Dv+MDjH8\r\n4Qbhnzjr2FCawD2F+4zcRIywEnXVRBLdUE5XwZjMVz8vHdHwqF18nOxR2FV8\r\niLjj2/RmIg6mV2voo7iVuTIIOS6pfsazENb/ZrOkHZ4WT423Fbc28qIC+OPR\r\nlu37pAiNqzNXUZHbN4UDmZ6mxl9j9wA8tdW2BF9vhBtgvbuWlaqqGTc4yIrz\r\n9Da2sP8evfIRN9eF95USukCBZG+2m2aERrETBVc9LwXoqKawdFHaB90oI8cy\r\nl4vKhcf+tw3P9+ckSpYxYSpPZYssaz9eEWNMx0dYsjKrBzcda0MSWfJmxx1G\r\nhiPsOSC4rxl9h4ZCOgIvvFp9JbhsMaB0F0U=\r\n=4ReI\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.2.4.tgz","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"6c3f7532c3d202e58e6aa7a1ddf35142dd750fd9","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"_resolved":"/builds/amplify/api-builder/published/@axway/api-builder-plugin-fn-swagger@3.2.4.tgz","_integrity":"sha512-FZP/anzuXrIWGRFFAqxRVM7XLY/Pth5ERcdiISL5mtVXICs63UZygejTNtkRjo8ORdUCQwux0g9NzYmIH29JiQ==","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"8.5.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.4","@axway/api-builder-project-utils":"2.0.1"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.4_1655736824178_0.8292611673504715","host":"s3://npm-registry-packages"}},"3.2.5":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.5","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.5","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov.work@gmail.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"9bb73a229747b85eeea5eb6250a774b28836118e","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.5.tgz","fileCount":4,"integrity":"sha512-cy6jHOCD/Q0F8js/vOFg72PIw3/o5oq9ILp20YASdeHQCUp/gEOeslwpmSqHZuNKASM1J5N59R2qL8/YFWm2Bw==","signatures":[{"sig":"MEUCIFQWy686R/ul2x5fvFguXIzJKIEGk/l9OtUptoYNNcP+AiEAhujkH5OmMJ5f6P5t7jnon8KNjPB6uzAcvIxN621wEug=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24019,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJizqoAACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmrkjA/+NfkJJ5wUz5SB9Z91BUSw9IUphVlTY7ZZY9e5w+GV/iIUVWDs\r\nG96X2lIp1npPa1ZAT4M9VHsCGhmrjSqSOIYq/jO3CGSB+w1mg9V5Dzy4/h6O\r\njRFab4q2o5srJPE9H2tzDNCx7DSBytgGZkPntDgjB/EZT0atX1xdcoG+f5uT\r\nXCGbqhpWHp5+JHNMy89wA6ss+kr/5jijJK07rm0wNAI2pmqgYjL/ilaOpkI3\r\nW81PdvYn9WEY83nBnPpF6/iy9aJr2A4P5dAx44gwc37X9KeHnfH98E14znYW\r\nlmN1wp49GuBq2O36cAp7mdilH+UScUNY1vvaTALYX6wtlQWYv9WUV/wRzP8e\r\n4LlWFQN7rxaq6f7f60pk8NCVZwTsDNWD4YmrhPFXaHRbdEmSKknGfS8XOAW8\r\naVdu7C09FfL7zI1vS+YSbtcX5cxu/k+VMyiuBDG95f5iEjDUlWKqySD0GnlK\r\nPX+VJZMcWYz7XbtsX+ZP4YIJoP6JNEYm6TQYxeejXhDSbssggSUb7QyPLTMt\r\nJasHw3HrrIGqfkeHaximWr9InLxspm5wzOJXYfSddSHDdolWi87+N33Jw2jt\r\n4Hf52aETiv15ORqq/2JyX9teZzmQDv+tZGST12DjRqviW8UuYUkTkci525WI\r\nmW4Ri/HvFsKtR5ka89pGuXRg3cFF7d3pvl4=\r\n=Jc9R\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.2.5.tgz","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"b15f6456458c7b2009c3d704d80a962d6de14d45","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"_resolved":"/builds/amplify/api-builder/published/@axway/api-builder-plugin-fn-swagger@3.2.5.tgz","_integrity":"sha512-cy6jHOCD/Q0F8js/vOFg72PIw3/o5oq9ILp20YASdeHQCUp/gEOeslwpmSqHZuNKASM1J5N59R2qL8/YFWm2Bw==","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"8.5.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.5","@axway/api-builder-project-utils":"2.0.1"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.5_1657711104059_0.5520184428483863","host":"s3://npm-registry-packages"}},"3.2.6":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.6","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.6","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov.work@gmail.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"990264b93254c39a1264a0d39fc902f39e5908d1","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.6.tgz","fileCount":4,"integrity":"sha512-PSfmCeYR6EH1IOQU4gYUAV5zVlzfvcIOMz9qXqwObo900cy3ZpVIXe/ObxHA4Dv5Qmf+iwU3RTJFD9e6lqvZCQ==","signatures":[{"sig":"MEQCIF4rwtv0XN9us0p59CLsp9dSAgzmqSNLwMHMpNv/edQVAiATa3Q3cmDnehd6sCET29AUowjhFVwl9zG1cnbWgcaJbw==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24092,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJi4BZQACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmpAxA//fwYxxdxPx8N0O9sR5Wx+MEMGPMpeAupMCPsK8jF5pikOEtNe\r\nDqDW0tLtbgxo5sulCngo8hRh8aUdEaE3UGaO4XXCNt7iXOOoCMma85Oc+w5x\r\nM4WnAn55Lpso60FqgehkzApgcIbD2n/hXIhxRgHpX/jo5Qx4F3hUSCLd+qNB\r\nhJJH34YpIYFQoNxA9KWE24ztz0FGRUfqfTOGVYMRgw5pHnzHVImyvE3EcJEp\r\nmrbFv5ccsYcfU6nX9I7YLZf77GuoPvemBRzRq/lNzZzNxhPfWEOY+nIKf1Ot\r\nai8iBYeb4VoBhovFE9PxFGaK4bk49d1/NbiFifR1n59IklZ+OjFkBM7JeJ1b\r\n4m42MfwcaEjdedMGFLRjsYe0A3ApaYhTESMux4egAs4UsR4e7/9lTChas1N9\r\nDQOCOZUBk/LtVoTo+QQvys20As8ZJcNNzOBT8Rn2PvMc5KXL5YK3iKphaPq2\r\nttqjEAtbhtf4CEw3IUJ94ZELBbwO404yRxXbTMUr7A9VhLuIStAMYiYukLGw\r\nQzLZHDlW6E5IGwktG0dU++LPxiI5do3fJFu1fAF61I0qdnmr73QZy1srXhnl\r\noXjEsql3PFcnPYtrEDjfLJ45W59t5LIGNEUfjZZKxqvOxCLlR25CpwAN96Ow\r\ngJ+UkQnWSiY2f9vUoKpSX9i/OG8HnCbdGro=\r\n=4Z5b\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","_from":"file:published/@axway/api-builder-plugin-fn-swagger@3.2.6.tgz","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"b884eb250ed5b7c859bdb18ec953a3ad32bc6a63","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"_resolved":"/builds/amplify/api-builder/published/@axway/api-builder-plugin-fn-swagger@3.2.6.tgz","_integrity":"sha512-PSfmCeYR6EH1IOQU4gYUAV5zVlzfvcIOMz9qXqwObo900cy3ZpVIXe/ObxHA4Dv5Qmf+iwU3RTJFD9e6lqvZCQ==","repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"8.5.0","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.6","@axway/api-builder-project-utils":"2.0.1"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.6_1658852944312_0.4697624609225548","host":"s3://npm-registry-packages"}},"3.2.7":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.7","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.7","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov.work@gmail.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"81c7417028edda8b984ae0cf7f6b797be9cb38e6","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.7.tgz","fileCount":4,"integrity":"sha512-8CgjxEm6OKAIlvnS4+UJriKg0kyi5pN5NIIUMjA0bjlUPtOEr8AIUmB1s8XSVQOLwMM9YO98sDeK6O4dOg22+g==","signatures":[{"sig":"MEYCIQCavAtdHnv0Y7Ha3Zq4Bxge9vZvYzDwtnkllVwBCuVYqAIhAM+KN1LeWgmiLUa0xbkjvBy3RduG5WUQlX5OJ45p5Xll","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24409,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJjCJ94ACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2Vmq8kw//Z8b0KYnFN+k2iKTmofna375aakgqSGVF7pYVs9VcKOPir1Rt\r\nYninlFkgcGG8rf2B6qHtDAVTH5zgSZ5M1Ipnv+7XCXCbjob3No040bRogiW9\r\nA/65oZzMaf83AUh6cDArfXbaVYI6EXGN7lSiEa4l8yWV8hiu0MIhqMj4ICcT\r\naGMxqG/TclbGDyfiTCSaiX6WIcGGWUk1bCCwbCUHPP6hk8hIizoLAXLQxJZg\r\n4K9SwPbQlF6mWeJRknt3fp3us3LGWXzSAhxbC8QHNeTnJHg8HpH8dCZMLP2a\r\nIruHnK6WjW5V0NFLlaxu7adTYNCENu96e/L3fg5ddmdH8k2o0o9xpI1Le3ew\r\nyr4hNv3w+6r7MyqPKC++M/waSVTED9s5wv/EdU7mtWU9zyzXRVakNhViOmaO\r\n3lWuEfoxFd6eoDgeahtjQ+AvVl55BKG28DdKWnVnfKpWuMQU+QsNE1J+7KN0\r\nzoE70QVSvOXJcTAFYK9Z9MDddhDeJTYO560ZNNMVHXqP+RTMwsq84WmagKLp\r\nKVThrts7RuiY8C7UE9LskwEu8oNQ1cB9RtYc3TeFbRcoS+Fom08M64R0L1zc\r\nc9y/XzOYmpppoTDzX9iF4003TTC023BkKxM40z8EoggdgIi7frp/6OOCTjG7\r\nt95hC4t2yKR1JGlt1iP5Z+QG90hytcbqZ6k=\r\n=ef+8\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"fbb1e12ff10dd9b73510cc5dce4cb7a27d7fe9c9","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"lerna/5.4.3/node@v16.14.2+x64 (linux)","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.6","@axway/api-builder-project-utils":"2.0.1"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.7_1661509496344_0.003845964222018994","host":"s3://npm-registry-packages"}},"3.2.8":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.8","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.8","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov.work@gmail.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"a643581a7a7bc6f5ac3fb31baa531d23948af864","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.8.tgz","fileCount":4,"integrity":"sha512-/Bdfav0xOKhihxSTP4yPl+VDrIH59H2N2f6HGg5/EQYxg0nrjl1WPSnBPdesWkv77C+3qJW3l9YYG4+5csjK9A==","signatures":[{"sig":"MEUCIQC8waq3r3RmnmFwsFSfbiutyuC6C+ryCPQs3AqYQHrKXgIgOiO0aPFLw4Me6cF9o44s3/w3I548gnNzI59bNUKp9Ck=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24482,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJjGKuOACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2Vmpp5w//YPxBmstqCM/1hY9963C2f+Hbluj1HQLOINQyqfZ0ceWNDzwC\r\nm7hAmktT7k5sjhf4X9Wbp6fYRI87buVr17qGSKvy9xg3E2lSl/FPQirKP7WR\r\n7x98k23smkLKiqemmMI3pt01I212c1YTjukLhRbqt4Oj9sy8s5lTSBxlSuIM\r\nYnRsfH0qK5PtSDbTZBnAHJzhzKYIOZakj1wx/Lc1GY9OhPOE7Rp/IaDOOutV\r\nWPiy8blw6M/X5BrC5bZZKX5fPFX3qapPm5Lp0PhEo8hg1E3eDqIXPpwEDcEJ\r\nIs3GYIgcoVL+YbQIzZ9mEf0jR8ZhRG3OMBhG1JcpwPZX+SVZq7HQv7rxxTjr\r\nLDdCklsZKEHgW2A/o329eD0PmOuXWcNNqd7yliDDBNRGXoyvzzix27+ZnaFn\r\nhRCH7xh+oYyG+PuwsligP7q69zq8NDJokoA+X04JeCcVvrXnVydQAAasdc8J\r\ny+sZFo8YwJIlV8vUqWrQnSzQTzwou0MB2Mk3C0iyIMW7YUMZ2CHu8XSwwXAv\r\nolq2CUSivCQgP9Qj/o/ovYq6njJoP7UOtK/KNvEucfOTZPdMhYIStVDqoNje\r\nOtB6FvyBnGzO5Qbe20LkXyHd55C6IIKa/InaOJRXHIrPKd8SJ6ESxI+xfLDS\r\nihSlEMyOmFEtkDjjHemH0yZplIPJTOul2+I=\r\n=cXBP\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.2.8\n- #7470: Update @axway/api-builder-test-utils devDependency.\n\n#### 3.2.7\n- #7495: Updated `README.md`.\n\n#### 3.2.6\n- #7466: Update @axway/api-builder-oas-flow-node dependency.\n\n#### 3.2.5\n- #7474: Internal dev-dependency move.\n\n#### 3.2.4\n- #7412: Pin in-house dependencies.\n\n#### 3.2.3\n- #7411: Internal bump.\n\n#### 3.2.2\n- #7403: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.1\n- #7345: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.0\n- #6933: Replace peerDependency on @axway/api-builder-runtime with `engines.apibuilder`.\n\n#### 3.1.3\n- #7139: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.2\n- #7284: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.1\n- #7303: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.0\n- #7282: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.10\n- #7111: Internal refactoring.\n\n#### 3.0.9\n- #7155: Update `@axway/api-builder-oas-flow-node` dependency.\n- #7155: Fixed issue with [CVE-2021-3918](https://nvd.nist.gov/vuln/detail/CVE-2021-3918) and removed the dependency on the `request` library.\n- #7155: Fixed an issue where the 'Authorization' header could not be unset (i.e. it was set to `null` in the Advanced HTTP Options).\n\n#### 3.0.8\n- #7123: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n**WARNING**: Installing this release can cause your application to emit a MISSING_KEY error(s) on startup and cause flows to be uneditable in the UI. If you encounter this issue, please contact Axway Support (support@axway.com) so that we may assist you with your upgrade.\n\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"e7b554d9558a642ce410e50a3e07f7241b439789","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"lerna/5.5.0/node@v16.14.2+x64 (linux)","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.7","@axway/api-builder-project-utils":"2.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.8_1662561166331_0.7671438366305225","host":"s3://npm-registry-packages"}},"4.0.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"4.0.0","keywords":["axway","amplify","api-builder","plugin","openapi","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@4.0.0","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov.work@gmail.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"1041955f3b549d3f3d1f453fb97010a90a7bed52","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-4.0.0.tgz","fileCount":4,"integrity":"sha512-gPDYfU0qSCRxk6p/NfQYAoei9TIw5FD0+QL5xo9LR2y88WDO5uDZNvlZQ8x7O6Wi1kTzDJT+GwQGqPy02MhMeg==","signatures":[{"sig":"MEUCIQD3Q1XHhXQPHNTgWCwtPxb+WrGYlNbHF/PaecRI8wTc/gIge6SoY9wwO0UeoqOcNR0pd9LtRXWdC1dTR0PyeQ5dC50=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24384,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJjG1hRACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2Vmp1xw//T45x4kkLpyLz/ZXSmrC/i1sD5JT8r0gxJPsyy7uBm6cY/nl4\r\nPmn+d6sIJapYK8jN9lhoRwLJzmrGqLUhGZFoUrRNbbvFIfntHXyC/9VCMJ+d\r\nn9MIuy01L50iEX9m6uQ2xOJAblFCiCZgsE/sKtqXxxtyXG7MslzhGk9ZO+W1\r\nXCudZ2fZeOnMo1t8BsU8Ojqg6JzsS2ZCu31aRoTZbWS+iEVDYxv5OhysRFC6\r\n+rO0uYqo5fIQ67czrcwp07JRTknCIyMLi5oKdgPh7pmQ8vbRoKcZ3sG4gyBq\r\nBnh/E2IYxLySTGL1Gh23bT1qTL/ObKJZLEZl/Flke129unDfkK1p6C9lRyTc\r\n0OPV5WCRnP0+euinLxw4ELQ9jDDc7jX1aCRRlOUP5dbYad6jxYyUAwjsRYBk\r\n6OhPErmUroXFxUKSIluO9biPBrHyYBAOBOeabaWP8ZVacGpn52+Ex7+mzdvj\r\najUGj/w1uZ7bxEZBHutocl6FwnJmdF9v9df7m6BfY6M5QiwpR1V25OXXgH1t\r\nNONzanqdOkPxczaAJAkYX/opDI3Fbw4dTnzjNCz+lzLHu+IdRw1NPdhrYGLO\r\nX7Y1calUX1NLhs8gJHly7XL54tmSRR8zBavYoPsRer8N1hHrugRv5wOuq0UR\r\nLrnEGm4/emMLwdJTK4OOzrgBNNLPi/S+RDA=\r\n=3yeZ\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","engines":{"node":">= 16","apibuilder":">= 4.69.0"},"gitHead":"6897fc91490e48b16876f5ab78f4cbe4f1ee26ab","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"_npmVersion":"8.15.0","api-builder":{"onlyPrerequisitesBreakThisComponent":true},"description":"OpenAPI client plugin","directories":{},"_nodeVersion":"16.17.0","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"3.0.0","@axway/api-builder-project-utils":"3.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_4.0.0_1662736464952_0.3932887892693482","host":"s3://npm-registry-packages"}},"4.0.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"4.0.1","keywords":["axway","amplify","api-builder","plugin","openapi","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@4.0.1","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"cb1kenobi","email":"chris@cb1inc.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"awam","email":"ewanharris93@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"npetrovski-axway","email":"npetrovski@axway.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov.work@gmail.com"},{"name":"cdobrica","email":"cdobrica@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"7b9c41d19d8d55e3f7c668d79a29da7b3c6577b7","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-4.0.1.tgz","fileCount":4,"integrity":"sha512-wtMykPDUrRHwZbE9sWxfKS9+j2fUrAoZbXrN+L+7P09re+Ng7WpN70YpMS4YgMDNvTZ1f0gyHH8y0KxdlQ21jA==","signatures":[{"sig":"MEUCIQCG3sZbkD2GknLNmqeQkyAeMo+dkY4rzA8irVqu0KuGhQIgbmpD97Lrqu7m60sadv+iOp/0bWAkK1baMqygCZGpld4=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24513,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJjLbLoACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmrmHg/9F7DAZ2NrO2/c9B97d8dTjc5Qd63JbMEAtorLdCIvB1eEHM/K\r\nY/PslVIWGVdjlXGlXj8B/A3s2z6N1dthf36V+y9Fw5jyPy01pEPyJQ0BYxy7\r\nQU/SV0DTpoz/qomLDx/FMbmIwa6Kafh2xnpXzlOUDUQ/T09quFyhgCGiYPa1\r\nZoQxyMX98kBpgUcNRxOqw2haclCghfHOE3WiJlNCrtGLUzsGTFinOJo4nc2t\r\njsQauEFQabwoYajb6fAdWUKRY49kpdFB2F8cUrUdCV1AdYUOSJ5Ijwr6TOWB\r\nkWQb0kNYxAM1doZ/Q1n1sthooOBMZOvixYAZULEkyZRBsqr4pF40xITCp3C9\r\n9mUHESek3RqEWXSvJzp6bxuwaO7QgfzKOX0UnJJXyfeS2JLrtyAy8d31Zvgt\r\nbnjNhq3FhshojAy44pRnemmnyFE2K5/6y0FmqsHKjDtjCM9qtD0EjK1GrrE2\r\ncYXMreWZd31PSw0JDuO+Qkfm3DrNHiFViMXxuM/4ypUbM6SOUl1W+hscGha2\r\nP2o8DwFihJD6R2omnm20toh8uGuQyX602kcwIOE8qmQMG3EBdqAgq45wEdjK\r\nv9fDjsHhhvuQQnAsvZyOpk2KvAZ99RE0Gg76a0mjKPY9hgzlJfjzJa9UWFCo\r\nitsYIxtyaCL6bJ080EWuUDrbFxUD2DeKD94=\r\n=L8kR\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","engines":{"node":">= 16","apibuilder":">= 4.69.0"},"gitHead":"64d3c8c662fcc06ea9579fffa121ab822f715e2c","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"_npmVersion":"lerna/5.5.2/node@v16.14.2+x64 (linux)","api-builder":{"onlyPrerequisitesBreakThisComponent":true},"description":"OpenAPI client plugin","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"3.0.1","@axway/api-builder-project-utils":"3.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_4.0.1_1663939304445_0.005864603900837206","host":"s3://npm-registry-packages"}},"3.2.9":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.2.9","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.2.9","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov.work@gmail.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"6f23ea7b5ea5b729f9fe5f5a78b3538614b2c4a4","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.2.9.tgz","fileCount":4,"integrity":"sha512-O9WCbxZ4kwh9DzfG9klhv9R/wF7Ijsf1r3IjZx+FgoyenZouV43zAo0I+1NGKb9gej2x5Fmh/uFMnIqcdtPlaQ==","signatures":[{"sig":"MEUCICe5XgtkGF99hjGLzi/ZR+HJF56tpVXBJ08qU3wVYamCAiEAsploSiYfOGKswM/SKZhewh6MS8tNfrNNDDE+lYvp9uc=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24661,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJjQBtcACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmpjWg/+IcvP77Yg6+/SBezx4vk7hJeRfxEdrQWh9fjw25TJqcC7/OMR\r\nuWZ5Dyqf3Bbuc7op44MqZDGEVhbFhREFnIWyip/aYrh4NIWzu8AlCIrUcjVD\r\nvD8LUoAqItnSAHJrzTbifnwhNlFqIjAfK+zaUPOJGUJYtf93I3sl14s1Qmsi\r\nwIJvcvdS+yodipNq/f88bQAFeTOrRKfJ0VdrHs9UV3OyUH0WiVFpT/2O3Nc4\r\nCCnwJjnGwKWvcnQjWXh0DAfcyBGKrnCy7ngbXv/jUzojBsN5yba/RfdN9kiH\r\nIBBIkKn1H9oWKF7+L/EGaALQ1351ED8K8wtZblcGEgy0Q1MzymFh5qjzaay7\r\nYIB79Bp8eChpyJwPNwOsOxSlMCln332lsN2Q0HbuoojhW1MRtTtclVE7KocK\r\nLhkaEIlOPfF6Z0IOZoZbXKvP0nMJRb/hrzaKewbtwPHVJsRwPCL7K+sf9q2q\r\nCN3C8IkABafqkZIPTrCV1SGS4vzeHdrY+jGpz/HF29SH0cGa3uKWc3GGUaHA\r\nlwGZrGZ5OM4l+tNX7Yi5v3jqNGUG6Xwi8SUXospPr5QmgPnuZhgK2N5V7C+X\r\nJhRdJeXfasGduWhI3RjGBg34UYZB3Z9Ny6h9oYye1d+WaV+QiXYgbKPahmSV\r\nOnA4Ouu5EnTZDIDQfOXDo5rfzYssPVUPnMc=\r\n=hHzW\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.2.9\n- #7538: Fixed an issue where the request content-length header was calculated incorrectly when the request body was a string that contains multi-byte characters.\n\n#### 3.2.8\n- #7470: Update `@axway/api-builder-test-utils` devDependency.\n\n#### 3.2.7\n- #7495: Updated `README.md`.\n\n#### 3.2.6\n- #7466: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.5\n- #7474: Internal dev-dependency move.\n\n#### 3.2.4\n- #7412: Pin in-house dependencies.\n\n#### 3.2.3\n- #7411: Internal bump.\n\n#### 3.2.2\n- #7403: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.1\n- #7345: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.0\n- #6933: Replace peerDependency on @axway/api-builder-runtime with `engines.apibuilder`.\n\n#### 3.1.3\n- #7139: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.2\n- #7284: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.1\n- #7303: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.0\n- #7282: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.10\n- #7111: Internal refactoring.\n\n#### 3.0.9\n- #7155: Update `@axway/api-builder-oas-flow-node` dependency.\n- #7155: Fixed issue with [CVE-2021-3918](https://nvd.nist.gov/vuln/detail/CVE-2021-3918) and removed the dependency on the `request` library.\n- #7155: Fixed an issue where the 'Authorization' header could not be unset (i.e. it was set to `null` in the Advanced HTTP Options).\n\n#### 3.0.8\n- #7123: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n**WARNING**: Installing this release can cause your application to emit a MISSING_KEY error(s) on startup and cause flows to be uneditable in the UI. If you encounter this issue, please contact Axway Support (support@axway.com) so that we may assist you with your upgrade.\n\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"b7dabe6949b4ff43790b95492941ae9404547a08","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"lerna/5.6.1/node@v16.14.2+x64 (linux)","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.6.8","@axway/api-builder-project-utils":"2.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.2.9_1665145691926_0.74286723254813","host":"s3://npm-registry-packages"}},"4.0.2":{"name":"@axway/api-builder-plugin-fn-swagger","version":"4.0.2","keywords":["axway","amplify","api-builder","plugin","openapi","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@4.0.2","maintainers":[{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"axway_darnaudov","email":"darnaudov@axway.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"agrakhov.work@gmail.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"2d54d9528d5e22da7077e2545a418b3cc1d4df88","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-4.0.2.tgz","fileCount":4,"integrity":"sha512-AS/N60zXSvoLJysbe4qRBeJRfBOSHrl7OEdXUHESZG9Sl6aWJ9GcuBj5QZsJrt/wnBOH0UrLYp4lselyKPeUzA==","signatures":[{"sig":"MEUCIAsDObtwHIvjMiutxYI8waOLNBiCUdC7to5rVvtXcL5tAiEA0lJkgs3k+7FUd/bBx/atqARgH9axeyf7/duy3Geaa+8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24863,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJjQDPeACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmpZPg//RzMoJw9kFlB8zXH+Dcgb5REfH7a27L7/tmI8hBRHvyVEO9CX\r\n//mnEA2a+vHSprzkgJHBJ0O0YrJiAgVR97J+6Hg4Y2b3o1q9vto1XXpTS8QW\r\nEXph4FjVsf4JzbY0FmrQ7iI3GExCB8PM12awE9eAmurKCcRJNFHQoGKia4U4\r\nstQMJhUPd56Y1q9kGc0VjwD8NnRrVqzfDQQFeQIl8GOGWVZM+QotLa88N5hs\r\nSolteAlEq/HiBClo+ejtnftu8TSE/n0lBSPSLuwz8HDL10cQacbKGbJ5M09s\r\nJF7d3kjp8kNm+RQ0OYGOTsFGghDe1VqNekMTw0Auzm2EA+VWUK7uhdGUpw9k\r\n56Txa7TeFsgacl3ua0hslpZ2EY8BPszNxNGMzxl5nxim2zRIfsiMLNv2SjP7\r\nB/SmqoiAqTYnBvq9mx6AqVsaBvbZBTbBN/B9qfZxKf/cDxc9bqGrSKWqBSmd\r\n6+8CZpBQw4xyw0RGwm1+qxkhU1/r1wWVpMxN9Nr5aodaz0PT4Qck/MrulOEf\r\nHAWD33fE7Hcb0e7SgfaKUJoOohcLoCQD2Cb1IA0B1PKtfC/vV+CxnZecyJr8\r\nxAvTX+G5GyNAvhDgqYP/TN3XB/9KxTmIs+FC1lm9HQ72DhaE44+2CU7Xo1G1\r\n1JqajNeQXsB2/O1DRHpQysDgWIsJdM0MHQU=\r\n=Jnz4\r\n-----END PGP SIGNATURE-----\r\n"},"main":"src/index.js","engines":{"node":">= 16","apibuilder":">= 4.69.0"},"gitHead":"c17c6025a442ded8c911a0d15e769063063b4f0c","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"jamie.peabody","email":"jamie.peabody@gmail.com"},"_npmVersion":"lerna/5.5.2/node@v16.14.2+x64 (linux)","api-builder":{"onlyPrerequisitesBreakThisComponent":true},"description":"OpenAPI client plugin","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"3.0.2","@axway/api-builder-project-utils":"3.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_4.0.2_1665151966478_0.5611817241005479","host":"s3://npm-registry-packages"}},"4.1.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"4.1.0","keywords":["axway","amplify","api-builder","plugin","openapi","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@4.1.0","maintainers":[{"name":"buildernpmuser","email":"npm.modules@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"bchristiansen@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"618a8f54de9239bb0f8eb8a3f95e03b933b16013","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-4.1.0.tgz","fileCount":4,"integrity":"sha512-qICmRbRRUDbeqA4P8XzrRGwYg4yj56oz15+QHDU+G5X8o1bGQjNtbuMxLUmY9xTMcVw4VeJ6kBMAKWCzLczdMw==","signatures":[{"sig":"MEUCIQCEPqnVLdAzhf15Tb0WqZxvmPOeuV9QPhYDDOFyqWVRBAIgKb5ZBNfSVU2JwiQ+KMYiH34OO9vXa3texyXkBfgtXRs=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24920},"main":"src/index.js","engines":{"node":">= 16","apibuilder":">= 4.69.0"},"gitHead":"b96a6950717b0fcc64941bcc08f9ee65b8a4dc5e","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_npmVersion":"lerna/5.5.2/node@v16.14.2+x64 (linux)","api-builder":{"onlyPrerequisitesBreakThisComponent":true},"description":"OpenAPI client plugin","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"3.1.0","@axway/api-builder-project-utils":"3.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_4.1.0_1697037864062_0.05703087287009434","host":"s3://npm-registry-packages"}},"4.2.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"4.2.0","keywords":["axway","amplify","api-builder","plugin","openapi","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@4.2.0","maintainers":[{"name":"buildernpmuser","email":"npm.modules@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"bchristiansen@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"b1b64772fc4680f4c3514eea9954d468fd386db0","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-4.2.0.tgz","fileCount":4,"integrity":"sha512-nB+zdy+trFp2VR0Ahmo3akzr2g+YqONoWW1JI352Xj0BN5BwJriP+6v99BRVKCWJT3aLV2MaH029F6Wh6EjjVA==","signatures":[{"sig":"MEUCIQCTZJq0Dt9toe6wqOG7/6mClBPpuraHr22hTdSPMDRCrAIgWlThmpNFjcNZe6qkhZbjcGK6u7P7N+IHdZBNWtDiwTY=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24966},"main":"src/index.js","engines":{"node":">= 16","apibuilder":">= 4.69.0"},"gitHead":"528551080521522d8f7ffc59a8f8923a1837d8f0","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_npmVersion":"lerna/5.5.2/node@v16.14.2+x64 (linux)","api-builder":{"onlyPrerequisitesBreakThisComponent":true},"description":"OpenAPI client plugin","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"3.2.0","@axway/api-builder-project-utils":"3.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_4.2.0_1698926253589_0.44382439265063334","host":"s3://npm-registry-packages"}},"3.3.0":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.3.0","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.3.0","maintainers":[{"name":"buildernpmuser","email":"npm.modules@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"bchristiansen@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"20badd41a1f1e5af70a2bf9fdd0ce8e89dfe268a","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.3.0.tgz","fileCount":4,"integrity":"sha512-PKAp081hdFY85MybTY85VxiGCtTUcajmOPYkR226dntv6wewuljB6Kbz3NVah7zy/3ZmlDt/08U5BebaVV4hyw==","signatures":[{"sig":"MEUCIQCyYkW6TlVJ49eMGi+EoSqkaW3sczPYsHBMyYkUalbstwIgLCeVWw0jU8ccoR6dB4Y9Qhcq1C67FA2q+Idyl4SVN5Y=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24718},"main":"src/index.js","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.3.0\n- #7595: Update @axway/requester dependency.\n\n#### 3.2.9\n- #7538: Fixed an issue where the request content-length header was calculated incorrectly when the request body was a string that contains multi-byte characters.\n\n#### 3.2.8\n- #7470: Update `@axway/api-builder-test-utils` devDependency.\n\n#### 3.2.7\n- #7495: Updated `README.md`.\n\n#### 3.2.6\n- #7466: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.5\n- #7474: Internal dev-dependency move.\n\n#### 3.2.4\n- #7412: Pin in-house dependencies.\n\n#### 3.2.3\n- #7411: Internal bump.\n\n#### 3.2.2\n- #7403: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.1\n- #7345: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.0\n- #6933: Replace peerDependency on @axway/api-builder-runtime with `engines.apibuilder`.\n\n#### 3.1.3\n- #7139: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.2\n- #7284: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.1\n- #7303: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.0\n- #7282: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.10\n- #7111: Internal refactoring.\n\n#### 3.0.9\n- #7155: Update `@axway/api-builder-oas-flow-node` dependency.\n- #7155: Fixed issue with [CVE-2021-3918](https://nvd.nist.gov/vuln/detail/CVE-2021-3918) and removed the dependency on the `request` library.\n- #7155: Fixed an issue where the 'Authorization' header could not be unset (i.e. it was set to `null` in the Advanced HTTP Options).\n\n#### 3.0.8\n- #7123: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n**WARNING**: Installing this release can cause your application to emit a MISSING_KEY error(s) on startup and cause flows to be uneditable in the UI. If you encounter this issue, please contact Axway Support (support@axway.com) so that we may assist you with your upgrade.\n\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"1c113572d8e57a903b51622757f0778dd49f5635","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"lerna/5.6.2/node@v16.14.2+x64 (linux)","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.7.0","@axway/api-builder-project-utils":"2.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.3.0_1699277357274_0.3154126274930553","host":"s3://npm-registry-packages"}},"4.2.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"4.2.1","keywords":["axway","amplify","api-builder","plugin","openapi","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@4.2.1","maintainers":[{"name":"buildernpmuser","email":"npm.modules@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"bchristiansen@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"01b154e75418bd4af38fbc5f2ffe087ade45e4eb","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-4.2.1.tgz","fileCount":4,"integrity":"sha512-+Bsd/1jnsvNRl78jg00P14tErW+yt9s+01FMZaI2rjJp+EA52dc5oLWZffaQN66nnT6yAnHz+xiyIS6zR2dM7w==","signatures":[{"sig":"MEUCIHjh9kyzzzSUwBsjgWdDi+wlffVD594jcmM9fTHcZPWfAiEApNvL9LVZBl4Fy47d0CEn3T0yZNm4IZpkg7O9nZJzyEk=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":25031},"main":"src/index.js","engines":{"node":">= 16","apibuilder":">= 4.69.0"},"gitHead":"a3d246bd81f8a03219b70f3c04cd8eed0b63a1e3","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"_npmVersion":"lerna/5.5.2/node@v16.14.2+x64 (linux)","api-builder":{"onlyPrerequisitesBreakThisComponent":true},"description":"OpenAPI client plugin","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"3.2.1","@axway/api-builder-project-utils":"3.0.0"},"_hasShrinkwrap":false,"_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_4.2.1_1699646131342_0.2543829615166029","host":"s3://npm-registry-packages"}},"3.3.1":{"name":"@axway/api-builder-plugin-fn-swagger","version":"3.3.1","keywords":["amplify","api-builder","plugin","axway","node","connector","api","service","swagger"],"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","_id":"@axway/api-builder-plugin-fn-swagger@3.3.1","maintainers":[{"name":"buildernpmuser","email":"npm.modules@axway.com"},{"name":"nkeranova","email":"nkeranova@axway.com"},{"name":"axway-npm","email":"builder11@axway.com"},{"name":"bladedancer","email":"bladedancer.gavin@gmail.com"},{"name":"ddimonov-axway","email":"ddimonov@axway.com"},{"name":"neon-axway","email":"cshantakumar@axway.com"},{"name":"vchauhan","email":"vchauhan@axway.com"},{"name":"mdimitrova","email":"mdimitrova@axway.com"},{"name":"pdzhorev","email":"pdzhorev@axway.com"},{"name":"axway_alasdair","email":"ahurst@axway.com"},{"name":"pltod2","email":"pl.todorov@gmail.com"},{"name":"pbozhkovaxway","email":"pbozhkov@axway.com"},{"name":"mbonchev-axway","email":"mbonchev@axway.com"},{"name":"axway-vertex","email":"bchristiansen@axway.com"}],"homepage":"https://platform.axway.com","bugs":{"url":"https://axway.com"},"nyc":{"all":true},"dist":{"shasum":"e687fbf98b84e522ed559a61622292dbb49bcd32","tarball":"https://registry.npmjs.org/@axway/api-builder-plugin-fn-swagger/-/api-builder-plugin-fn-swagger-3.3.1.tgz","fileCount":4,"integrity":"sha512-0/JloZfynl4JlCiGpsnTG/yfXaWQu0+qDEuz4fp8k1Mp+zEnN0PPKZR1ZSgk8vYf5NXX/OX1qLCOgd5IV75fLQ==","signatures":[{"sig":"MEQCIAQTuAzC8jqBLZHCpVqMt4Hps7atZdPYbf19rUeXs6txAiBT/Oa0HlfCz0lM/+5Ks+sg++DTQqmGFY8rEpjCwI1J2A==","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":24783},"main":"src/index.js","readme":"# @axway/api-builder-plugin-fn-swagger\n\n## About\n\nThis plugin searches for swagger documents in a swagger folder in your application and generates one flow-node per document to be used within [Axway API Builder's](https://www.axway.com/en/datasheet/axway-api-builder).\n\nThe generated flow-nodes export functions that can be used withing API Builder flows for communication with APIs services described in your swagger documents.\n\n\n## Getting started\n\n1. Follow the [Getting Started Guide](https://docs.axway.com/bundle/api-builder/page/docs/getting_started/index.html) to learn how to install and create API Builder application.\n\n2. Then make sure you have the plugin installed within your application with:\n\n```\nnpm install --no-optional @axway/api-builder-plugin-fn-swagger\n```\n\n## How to use the plugin?\n\n1. During the **npm install** phase the swagger plugin will create a folder named `./swagger` in the root of you application. Note that if the folder already exists it will be preserved with all of its content.\n\n2. Place your swagger JSON files into the `./swagger` folder.\n\n3. (Optional) Place your service icons into the `./swagger` folder. The icon should have the same name as swagger JSON file for your service and should be one of the following formats - bmp | jpeg | jpg | png | gif | tiff | svg\n\n4. Run your app with **npm start** and the flow-nodes will be available in the tool panel of your application. In the Connectors section, you should see a plugin listed for each JSON Swagger file successfully loaded from your `./swagger` folder.\n\n5. Each flow-node will have a corresponding number of functions based on what has been described in the swagger JSON specification for particular service. Each of these functions could be used during the flow execution.\n\n## Authorization\n\nAuthorization parameters described by each flow-node are supplied via the flow editor.\n\n## How to configure the plugin?\n\nThe first time a new Swagger file is detected, a new configuration file is generated with the name of the Swagger file.  For example, if you installed \"petstore.json\", the plugin will generate `conf/petstore.default.js`.  You can configure the plugin using the configuration options below.\n\n### Configuration options\n\n| Option          | Type    | Required   | Compatibility | Description |\n|-----------------|---------|------------|---------------|-------------|\n| **proxy**       | String  | _optional_ | OAS2, OAS3    | The URL to use for outbound proxy requests. |\n| **insecureSSL** | Boolean | _optional_ | OAS2, OAS3    | Enables insecure SSL on outbound requests. |\n| **uri**         | Object  | _optional_ | OAS2          | Contains overrides for the server URI. |\n| **uri.protocol**| String  | _optional_ | OAS2          | Overrides the server's protocol, one of: `\"http\"`, or `\"https\"`. |\n| **uri.host**    | String  | _optional_ | OAS2          | Overrides the server's hostname. |\n| **uri.port**    | Number  | _optional_ | OAS2          | Overrides the server's port (default depends on `uri.protocol`). |\n| **uri.basePath**| String  | _optional_ | OAS2          | Overrides the server's basePath. Should start with a leading slash, unless providing an empty string to remove an existing basePath. |\n\n## Known limitations\n\nThe plugin has the following known limitations:\n\n- #6187: Does not support OAS3 semantic validation on startup\n- #6187: Does not support OAS3 [wildcard content media-type objects](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-11)\n- #6187: Does not support OAS2 [collectionFormat](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#user-content-parametercollectionformat)\n- #6187: Does not support OAS3 [parameter styles](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#style-values)\n- #6187: Does not support OAS3 [parameter explode](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#user-content-parameterexplode)\n- #6187: Does not support OAS3 [multipart encoding object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#encodingObject)\n- #6228: Fixes schema references to definitions as they were incorrectly stripping characters.\n- #6187: Does not support OAS3 [parameter nullable](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [cookie parameters of type object or array](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-20)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6187: Does not support OAS3 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#fixed-fields-10) or OAS2 [parameter allowEmptyValue](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#fixed-fields-7)\n- #6276: Does not support OAS3 [security schemes](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.3.md#security-scheme-object) of type `openIdConnect`, or type `http` with any scheme other than `basic`.\n\n## Changes\n\n#### 3.3.1\n- #7600: Fix @axway/requester explicit dependencies.\n\n#### 3.3.0\n- #7595: Update @axway/requester dependency.\n\n#### 3.2.9\n- #7538: Fixed an issue where the request content-length header was calculated incorrectly when the request body was a string that contains multi-byte characters.\n\n#### 3.2.8\n- #7470: Update `@axway/api-builder-test-utils` devDependency.\n\n#### 3.2.7\n- #7495: Updated `README.md`.\n\n#### 3.2.6\n- #7466: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.5\n- #7474: Internal dev-dependency move.\n\n#### 3.2.4\n- #7412: Pin in-house dependencies.\n\n#### 3.2.3\n- #7411: Internal bump.\n\n#### 3.2.2\n- #7403: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.1\n- #7345: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.2.0\n- #6933: Replace peerDependency on @axway/api-builder-runtime with `engines.apibuilder`.\n\n#### 3.1.3\n- #7139: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.2\n- #7284: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.1\n- #7303: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.1.0\n- #7282: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.10\n- #7111: Internal refactoring.\n\n#### 3.0.9\n- #7155: Update `@axway/api-builder-oas-flow-node` dependency.\n- #7155: Fixed issue with [CVE-2021-3918](https://nvd.nist.gov/vuln/detail/CVE-2021-3918) and removed the dependency on the `request` library.\n- #7155: Fixed an issue where the 'Authorization' header could not be unset (i.e. it was set to `null` in the Advanced HTTP Options).\n\n#### 3.0.8\n- #7123: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.7\n- #7143: Internal unit-test update.\n\n#### 3.0.6\n- #7132: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 3.0.5\n- #7105: In `@axway/requester`, response `body` is no longer logged at DEBUG level to improve performance.\n\n#### 3.0.4\n- #7059: Fixes problem loading OAS spec with the error \"Cannot convert undefined or null to object\".\n\n#### 3.0.3\n- #7057: Updated documentation links.\n\n#### 3.0.2\n- #7008: Bumped `@axway/api-builder-project-utils` dependency.\n\n#### 3.0.1\n- #6295: Ensured `Server URL` parameter of generated Flow-node(s) is editable.\n\n#### 3.0.0\n- #5352: Breaking change: updated required minimum version of @axway/api-builder-runtime to Utrecht (4.69.0).\n- #5352: Updated to use a new version of `@axway/api-builder-oas-flow-node`, that added support for OAuth2 Client Credentials.\n\n#### 2.9.6\n- #7010: OAS methods that describe binary input `{ type: 'string', format: 'binary' }` will now generate parameter schema of type any (i.e. `{}`) instead of `{ type: 'string' }`.\n\n#### 2.9.5\n- #6934: Internal refactoring around code style.\n\n#### 2.9.4\n- #6938: Update `@axway/api-builder-oas-flow-node` dependency to resolve security issue with z-schema.\n\n#### 2.9.3\n- #6783: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.2\n- #6732: Fixes `No @axway/api-builder-runtime instance` error when running OAS plugin tests from a sub-directory of an API Builder project.\n\n#### 2.9.1\n- #6546: Update `@axway/api-builder-oas-flow-node` dependency.\n\n#### 2.9.0\n- #6296: Added optional Advanced HTTP Options `Headers` parameter to generated flow-nodes. This allows overriding headers, as well as defining any headers not in the OAS spec.\n\n#### 2.8.0\n- #6549: Fix regression from 2.7.0 where basePath could not be overridden in config for OAS2 definitions.\n- #6549: Allow an existing basePath to be removed as part of an override in config for OAS2 definitions by providing the value as an empty string.\n- #6412: Added custom HTTP headers to generated flow-nodes.\n\n#### 2.7.8\n- #4567: Added [`api-builder-project-utils`](https://www.npmjs.com/package/@axway/api-builder-project-utils) to handle automatic `swagger` directory creation in a project when installing this plugin.\n\n#### 2.7.7\n- #6397: Fix integration tests to fail with non-zero exit code.\n- #6397: Fix unit test assertions which were not being called.\n\n#### 2.7.6\n- #6411: Fix failing unit-tests.\n\n#### 2.7.5\n- #6412: Updated to use a new version of `@axway/api-builder-oas-flow-node` that works with `@axway/api-builder-sdk@1.0.0`.\n\n#### 2.7.4\n- #6322: Previously, references to schema definitions/components that had keys containing URI reserved characters ([RFC-3986 section 2.2](https://tools.ietf.org/html/rfc3986#section-2.2)) (e.g. \"Pet!\") would be incorrectly encoded, causing a runtime error, \"MissingRefError: can't resolve reference schema:///...\". Now, references are correctly encoded.\n\n#### 2.7.3\n- #6320: Fixed `Uncaught Exception Unable to register flow-node` on API Builder startup when handling OAS2 definitions with response schemas that were `type: \"file\"`.\n\n#### 2.7.2\n- #6318: Fixes unused references warning.\n- #6315: Internal chore.\n\n#### 2.7.1\n- #6233: Fix install configuration banner when console width is undefined.\n\n#### 2.7.0\n- #6187: Supports OAS3.\n- #6265: Now uses the actual service directory, instead of process.cwd(), when loading OAS files and generating config. (requires @axway/api-builder-runtime 4.26.0)\n- #6187: Supports OAS3 schema validation on startup\n- #6256: Supports loading external OAS definitions from file or URL.\n- #6273: Previously, methods that had file inputs would allow the types `selector`, `object`, but there is no way of providing a valid file as a JSON object. Now, you can chose from `selector` for files and streams, and `string` for raw binary data.\n\n#### 2.6.12\n- #6116: Internal cleanup chore.\n\n#### 2.6.11\n- #6114: Refactor code for style, security and performance improvements.\n\n#### 2.6.10\n- #6115: Internal fix for Sonar scans.\n\n#### 2.6.9\n- #6074: Internal CI chore.\n\n#### 2.6.8\n- #5764: Modified request and response logging from `debug` to `trace` level.\n- #5764: Update `@axway/requester` version to `4.0.0` which provides more accurate logging of data after making modifications before making the request.\n\n#### 2.6.7\n- #5711: Internal cleanup of npm scripts.\n\n#### 2.6.6\n- #5713: Update `nodehandler-utils` dependency.\n\n#### 2.6.5\n- #5708: Internal changes to update mocha configuration\n\n#### 2.6.4\n- #5709: Internal changes to update eslint rules.\n\n#### 2.6.3\n- #5707: Internal cleanup to code coverage during build process.\n\n#### 2.6.2\n- #5742: Internal change to remove `dot` dependency for internal config generation.\n\n#### 2.6.1\n- #5552: Fix for wrong URI creation in cases when basePath is not specified in Swagger document.\n\n#### 2.6.0\n- #5653: Add support for circular references \n\n#### 2.5.1\n- #5622: Fix regression introduced in 2.4.1 where the format of the data returned would change depending on the value of the response rather than just the content-type header. Now, when content type is \"application/json\" and \"Decode Response\" parameter is set to \"auto\", a JSON value will be returned, otherwise it will throw an error while parsing. For other known text-like content-types including \"application/xml\", a valid string will always be returned. For every other case, a Buffer will be consistently returned.\n\n#### 2.5.0\n- #5630: Add support for `multipart/form-data` in `Content Type` parameter. `multipart/form-data` will be prioritized as a default value if the Swagger method has `formData` fields of type `file`.\n- #5630: Add an enum property choice of `application/wwww-form-urlencoded` and `multipart/form-data` to `Content Type` parameters when Swagger method has `formData` parameters which are not type `file` and do not define `consumes`.\n- #5630: Change the default value for `Content Type` parameters to `application/wwww-form-urlencoded`, falling back to `multipart/form-data` and then the first `consumes` value when either values exist inside the Swagger method's `consumes`.\n- #5640: Fix issue where charset is stripped from the default value for `Content Type` parameters in some cases.\n\n#### 2.4.1\n- #5622: Fixed error when the value of `Accept` was a derivative of \"application/json\" and 0 length response body was returned.\n\n#### 2.4.0\n- #5329: Support requests using formData parameters with `application/x-www-form-urlencoded` content type.\n\n#### 2.3.0\n- #5432: Swagger plugin adds support for `Content-Type`, `Accept`, and `Decode Response` parameters as \"Advanced HTTP Options\" on the corresponding Swagger Flow-node, enabling developers to choose the appropriate media-types, and to control how response is decoded when communicating to backend services.\n\n#### 2.2.0\n- #5459: Swagger plugin now supports YAML.\n\n#### 2.1.5\n- #5488: Swagger plugin is no longer apply swagger validation with swagger-tools package\n\n#### 2.1.4\n- #5413: Swagger plugin will now fail on loading Swagger files with semantic validation problems\n\n#### 2.1.0\n- #5364: Support insecure SSL option on outbound requests `insecureSSL`.\n- #5414: Prevent logging circular JSON references on error.\n\n#### 2.0.5\n- #5359: Log to the console to notify the user whenever configuration files are created on load.\n\n#### 2.0.4\n- #5360: No longer fail to load plugin when unsupported or invalid security definitions are defined in a provided swagger document. An error is now logged with the details instead.\n\n#### 2.0.3\n- #5392: Removed `config` from request log data and now only log specific request configuration options such as `proxy`.\n\n#### 2.0.2\n- #5395: Refactored tests.\n\n#### 2.0.1\n- #5349: Remove dependency on the enableAuthorizationInFlows preview flag.\n\n#### 2.0.0\n**WARNING**: Installing this release can cause your application to emit a MISSING_KEY error(s) on startup and cause flows to be uneditable in the UI. If you encounter this issue, please contact Axway Support (support@axway.com) so that we may assist you with your upgrade.\n\n- #5384: Breaking Change: Previously, Swagger responses were mapped to outputs having `statusCode` property which was inconsistent with the rest of the product.  Now, responses are mapped to outputs having `status` property.\n\n- #5073: Requests and responses to external Swagger services are now logged in detail.\n- #5349: Breaking Change: Minimum supported version of API Builder is now Jakarta, which supports flow-nodes that advertise authentication parameters.\n- #5314: Support generation of stub credentials from new Swagger documents loaded by the plugin.\n- #5007: Breaking Change: Previously, there was no validation of the Swagger documents loaded by the plugin when the service was started. Now, the Swagger documents are validated and, if any are invalid, the loading of the plugin is aborted.\n- #4919: Breaking Change: The configuration parameter `x-vendor-openapi-uri` has been renamed to `uri`.\n- #4919: Replace `superagent` with `request` for http communication.\n- #4918: Breaking Change: Previously, if a request to a method which documented an optional query parameter with a default value and was not supplied to the request, the default value would be sent to the service instead. Now, default values are not used when sending query parameters.\n- #4918: Breaking Change: Removed support for the following credential configuration values. Authorization parameters should be provided in the flow editor instead:\n\t- `x-vendor-openapi-username`\n\t- `x-vendor-openapi-password`\n\t- `x-vendor-openapi-key`\n\t- `x-vendor-openapi-token`\n- #5358: Breaking Change: Headers returned from service are no longer modified by us in the following cases:\n\t- Headers not defined by the Swagger are no longer removed from the output.\n\t- The case of header keys are not modified to match the Swagger definition.\n\t- Headers defined by the Swagger but not in the service response will not be output as undefined.\n- #5358: Breaking Change: A `Default` output is created for all flow-nodes regardless of the Swagger definition.\n- #5358: Breaking Change: An `Error` output is created for all flow-nodes to allow routing on connection errors.\n- #5358: The default JSONPath selector for all outputs is now `$.response`. Only the Error output defaults to `$.error`.\n\n#### 1.1.1\n- #5177: Previously, Swagger plugin was taking specific configurations for all the available services in Swagger folder. Now, it takes optional `proxy` as additional parameter which is used for tunneling http/s requests through proxy server.\n\n#### 1.0.19\n- #5235: Previously, when an error occurred while loading multiple Swagger documents, the filename displayed in the error may refer to the wrong Swagger document. Now the correct file name is displayed.\n\n#### 1.0.18\n- #5116: Previously, when errors occurred on load, only the message was logged. Now, the stack trace is logged as well as the path to the Swagger file which caused the issue (if applicable).\n\n#### 1.0.17\n- #5111: Previously, Swagger documents with extensions in the same location as path methods failed to be loaded correctly. Now, extensions will be correctly ignored.\n\n#### 1.0.16\n- #5112: Previously, the server start would fail with a schema validation error when attempting to handle swaggers, that didn't contain the \"definitions\" section. Now, the loading of services with a swagger documents without the \"definitions\" section is allowed.\n\n#### 1.0.15\n- #5050: Updating license text.\n\n#### 1.0.14\n- #5004: Previously, the default configuration file generation did not preserve the service name during the creation of the initial service configuration file if the service had its service name manually changed, resulting in generating unique file name every time the service was restarted. Now, the swagger plugin generates configuration files by preserve the service name and stops once a config for the given service is created.\n\n#### 1.0.12\n- #4979: Previously, api-builder-plugin-fn-swagger generated incorrect inputs and outputs for flow-nodes when references were used in multiple places in the original swagger document. An example of the incorrect behavior would be required parameters not being marked as required in the flow-node. Now, the generated flow-nodes will be generated correctly.\n\n#### 1.0.8\n- #4897: Previously, api-builder-plugin-fn-swagger failed on loading swagger files that specify parameters with missing \"in\" property as well as did not dereference schemas from global \"parameters\" and \"responses\" sections. Now, swagger files with parameters and responses that just refer to schemas in \"parameters\" and \"responses\" section are loaded successfully.\n\n#### 1.0.6\n- #4757: Changed SCM repository and associated internal cleanup.\n- #4760: Correctly trigger default response.\n Previously service connectors and flow-nodes generated with api-builder-plugin-fn-swagger did not handle the cases where the swagger definition have default response.\n Now service connectors and flow-nodes generated with api-builder-plugin-fn-swagger will use the proper response description even when default descriptions exists. For example if the service returns http code 301 and there is no response defined for 301 the \"default\" response will be used if present in the swagger document.\n\n## License\n\nThis code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here: [https://support.axway.com/en/auth/general-conditions](https://support.axway.com/en/auth/general-conditions); EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.\n","engines":{"node":">= 8.9","apibuilder":">= 4.69.0"},"gitHead":"b4d1bde915913e7646a9f2ece14121364556a96a","scripts":{"test":"nyc mocha ./test/*Test.js","build":"npm run build:lint && npm run test","test:fix":"eslint . --fix && npm test","build:lint":"eslint .","test:debug":"mocha --inspect-brk ./test/*Test.js","test:watch":"npm test -- --watch","postinstall":"api-builder-create-directory ./swagger","build:lint:fix":"eslint . --fix","check:dependencies":"npm-check"},"_npmUser":{"name":"axway_alasdair","email":"ahurst@axway.com"},"repository":{"url":"https://git.ecd.axway.int/amplify/api-builder-plugins","type":"git"},"_npmVersion":"lerna/5.6.2/node@v16.14.2+x64 (linux)","description":"API Builder plugin for creating flow-nodes from swagger specifications","directories":{},"_nodeVersion":"16.14.2","dependencies":{"chalk":"^2.3.2","@axway/api-builder-oas-flow-node":"2.7.1","@axway/api-builder-project-utils":"2.0.1"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/api-builder-plugin-fn-swagger_3.3.1_1699648517690_0.2921361206084683","host":"s3://npm-registry-packages"}}},"time":{"created":"2018-06-17T22:33:20.735Z","modified":"2025-07-25T08:30:25.241Z","1.0.0-1":"2018-06-17T22:33:21.062Z","1.0.0-2":"2018-06-18T12:10:26.944Z","1.0.0-3":"2018-06-18T12:33:57.795Z","1.0.0-4":"2018-06-19T09:36:08.352Z","1.0.0-5":"2018-06-20T10:17:16.332Z","1.0.0-6":"2018-06-20T13:06:43.799Z","1.0.0-7":"2018-06-20T14:08:52.999Z","1.0.0-8":"2018-06-21T11:11:30.437Z","1.0.0":"2018-06-27T10:12:05.392Z","1.0.1":"2018-07-10T17:14:00.487Z","1.0.2":"2018-07-11T10:59:51.433Z","1.0.3":"2018-07-19T10:05:44.611Z","1.0.4":"2018-07-23T11:26:12.628Z","1.0.5":"2018-07-23T11:51:03.319Z","1.0.6":"2018-07-23T12:14:10.460Z","1.0.7":"2018-08-02T13:04:06.291Z","1.0.8":"2018-08-03T09:28:02.156Z","1.0.9":"2018-08-03T10:20:14.511Z","1.0.10":"2018-08-03T11:38:44.796Z","1.0.11":"2018-08-10T09:07:01.610Z","2.0.0-rdpp-feat-4940.3de41a.0":"2018-08-14T11:06:59.608Z","2.0.0-rdpp-feat-4918.59fced.0":"2018-08-23T12:16:50.903Z","1.0.12":"2018-08-23T20:48:40.289Z","2.0.0-rdpp-feat-4918.5ff06a.0":"2018-08-24T14:09:50.223Z","2.0.0-rdpp-feat-4918.bcf75e.0":"2018-08-29T08:17:09.626Z","2.0.0-rdpp-feat-4918.76d99a.0":"2018-08-30T15:22:40.104Z","1.0.13":"2018-08-31T09:16:54.559Z","1.0.14":"2018-08-31T11:56:00.905Z","2.0.0-rdpp-feat-4918.0c3b98.0":"2018-08-31T15:56:49.965Z","1.0.15":"2018-09-06T13:22:19.811Z","2.0.0-rdpp-feat-4918.adf516.0":"2018-09-13T08:31:03.230Z","2.0.0-rdpp-feat-4918.083e37.0":"2018-09-13T15:09:32.186Z","2.0.0-rdpp-feat-4918.416e64.0":"2018-09-21T12:22:47.939Z","1.0.16":"2018-09-27T16:29:36.444Z","1.0.17":"2018-09-28T09:11:52.181Z","2.0.0-rdpp-feat-4918.804579.0":"2018-09-28T13:53:58.729Z","2.0.0-rdpp-feat-4918.a5e408.0":"2018-10-01T15:55:16.466Z","1.0.18":"2018-10-03T07:56:10.257Z","2.0.0-rdpp-feat-4918.c3db6f.0":"2018-10-04T12:06:02.697Z","2.0.0-rdpp-feat-5235.4f6541.0":"2018-10-05T13:31:32.451Z","2.0.0-rdpp-feat-5162.960006.0":"2018-10-08T15:02:27.029Z","2.0.0-rdpp-feat-4918.8bfb82.0":"2018-10-08T15:23:31.583Z","2.0.0-rdpp-feat-5235.29dff2.0":"2018-10-09T08:42:35.230Z","1.0.19":"2018-10-09T08:46:35.227Z","2.0.0-rdpp-feat-5235.b37758.0":"2018-10-09T10:24:42.604Z","2.0.0-rdpp-feat-4918.2d5162.0":"2018-10-09T10:30:25.255Z","2.0.0-rdpp-feat-5162.b48298.0":"2018-10-09T12:02:27.636Z","2.0.0-rdpp-feat-4918.6bd6b7.0":"2018-10-09T12:06:31.273Z","1.1.0":"2018-10-11T22:31:08.552Z","1.1.1":"2018-10-12T11:25:50.054Z","2.0.0-rdpp-feat-4918.50304a.0":"2018-10-12T11:29:22.379Z","1.1.2":"2018-10-12T12:10:45.104Z","1.1.3":"2018-10-17T10:50:44.981Z","2.0.0-rdpp-feat-4918.629929.0":"2018-10-17T10:54:40.272Z","2.0.0-rdpp-feat-4918.38ef09.0":"2018-10-18T18:26:35.171Z","1.1.4":"2018-10-24T15:25:32.702Z","2.0.0-rdpp-feat-4918.d87e6a.0":"2018-11-13T11:49:37.549Z","1.1.5":"2018-11-13T11:51:10.352Z","2.0.0-swagger-v2-preview.5f3d96.0":"2018-11-14T13:39:35.426Z","2.0.0-swagger-v2-preview.44b0ee.0":"2018-11-14T15:57:42.560Z","2.0.0-swagger-v2-preview.927944.0":"2018-11-14T16:11:29.495Z","2.0.0-swagger-v2-preview.d782ae.0":"2018-11-23T11:21:21.049Z","2.0.0-swagger-v2-preview.09c711.0":"2018-11-23T12:48:38.082Z","2.0.0-swagger-v2-preview.b8c6ff.0":"2018-11-23T15:07:06.866Z","1.1.6":"2018-11-26T12:43:38.188Z","2.0.0-swagger-v2-preview.7862b0.0":"2018-11-27T16:21:33.347Z","2.0.0":"2018-12-07T11:33:47.502Z","2.0.1":"2018-12-07T13:35:13.683Z","2.0.2":"2018-12-11T17:11:33.968Z","2.0.3":"2018-12-13T10:55:04.149Z","2.0.4":"2018-12-14T14:45:56.970Z","2.0.5":"2018-12-14T17:06:33.404Z","2.1.1":"2018-12-31T14:49:33.981Z","2.1.2":"2019-01-25T15:24:32.081Z","2.1.3":"2019-01-25T16:24:17.197Z","2.1.4":"2019-01-25T16:59:28.416Z","2.1.5":"2019-02-01T15:09:03.773Z","2.2.0":"2019-02-11T12:50:01.850Z","2.2.1":"2019-03-01T11:13:04.734Z","2.3.0":"2019-03-13T12:05:16.115Z","2.4.0":"2019-03-25T13:48:41.770Z","2.4.1":"2019-04-01T16:06:42.631Z","2.4.2":"2019-04-05T16:54:38.900Z","2.5.0":"2019-04-10T17:38:09.327Z","2.5.1":"2019-04-11T17:15:06.986Z","2.6.0":"2019-04-24T17:42:08.437Z","2.6.1":"2019-04-25T07:56:55.304Z","2.6.2":"2019-05-03T11:40:43.447Z","2.6.3":"2019-05-10T18:43:18.536Z","2.6.4":"2019-05-13T15:45:49.312Z","2.6.5":"2019-05-15T13:20:59.770Z","2.6.6":"2019-05-15T14:21:13.274Z","2.6.7":"2019-05-22T14:23:54.031Z","2.6.8":"2019-06-06T18:08:31.268Z","2.6.9":"2019-09-27T11:56:44.181Z","2.6.10":"2019-11-26T10:10:30.026Z","2.6.11":"2019-11-29T10:55:06.178Z","2.6.12":"2019-11-29T13:03:24.151Z","2.7.0-rdpp-6187.528e39.0":"2020-02-14T18:04:40.827Z","2.7.0-rdpp-6228.8dbc60.0":"2020-02-28T14:36:48.801Z","2.7.0-rdpp-6269.fcdbdf.0":"2020-03-13T17:06:35.563Z","2.7.0":"2020-03-26T21:26:38.753Z","2.7.1":"2020-04-03T09:38:58.066Z","2.7.2":"2020-04-08T07:50:46.611Z","2.7.3":"2020-04-22T08:53:32.646Z","2.7.4":"2020-04-22T12:23:10.305Z","2.7.5":"2020-06-05T08:48:57.178Z","2.7.6":"2020-06-05T10:21:35.076Z","2.7.7":"2020-06-16T11:35:17.183Z","2.7.8":"2020-06-17T05:43:05.072Z","2.8.0":"2020-09-10T09:12:59.770Z","2.9.0":"2020-09-11T11:32:37.463Z","2.9.1":"2020-10-23T07:42:38.587Z","2.9.2":"2021-02-05T12:20:14.048Z","2.9.3":"2021-05-05T11:59:06.728Z","2.9.4":"2021-06-25T15:25:20.281Z","2.9.5":"2021-06-30T12:02:38.131Z","2.9.6":"2021-08-25T14:33:17.855Z","3.0.0":"2021-08-26T18:00:33.469Z","3.0.1":"2021-09-07T15:32:07.266Z","3.0.2":"2021-09-23T16:13:08.825Z","3.0.3":"2021-10-08T13:40:00.097Z","3.0.4":"2021-10-20T14:50:59.434Z","3.0.5":"2021-11-04T13:07:38.327Z","3.0.6":"2021-11-18T13:43:26.852Z","3.0.7":"2021-11-24T09:19:49.218Z","3.0.8-rdpp-7123-5cfec9.0.0":"2021-12-01T13:05:10.821Z","3.0.8":"2021-12-01T13:05:16.533Z","3.0.9":"2021-12-16T21:49:10.055Z","3.0.10":"2022-01-11T14:37:40.382Z","3.1.0":"2022-02-18T08:21:16.633Z","3.1.1":"2022-03-04T11:15:42.457Z","3.1.2":"2022-03-07T10:32:16.615Z","3.1.3":"2022-03-09T15:30:01.746Z","3.2.0":"2022-04-06T17:59:45.148Z","3.2.1":"2022-04-07T15:47:59.360Z","3.2.2":"2022-05-17T12:47:17.029Z","3.2.3":"2022-06-14T15:24:19.892Z","3.2.4":"2022-06-20T14:53:44.319Z","3.2.5":"2022-07-13T11:18:24.244Z","3.2.6":"2022-07-26T16:29:04.481Z","3.2.7":"2022-08-26T10:24:56.512Z","3.2.8":"2022-09-07T14:32:46.490Z","4.0.0":"2022-09-09T15:14:25.096Z","4.0.1":"2022-09-23T13:21:44.580Z","3.2.9":"2022-10-07T12:28:12.181Z","4.0.2":"2022-10-07T14:12:46.684Z","4.1.0":"2023-10-11T15:24:24.269Z","4.2.0":"2023-11-02T11:57:33.762Z","3.3.0":"2023-11-06T13:29:17.414Z","4.2.1":"2023-11-10T19:55:31.539Z","3.3.1":"2023-11-10T20:35:17.833Z"},"bugs":{"url":"https://axway.com"},"author":{"url":"https://axway.com","name":"Axway","email":"support@axway.com"},"license":"SEE LICENCE IN LICENSE","homepage":"https://platform.axway.com","keywords":["axway","amplify","api-builder","plugin","openapi","swagger"],"description":"OpenAPI client plugin","maintainers":[{"email":"nkeranova@axway.com","name":"nkeranova"},{"email":"builder11@axway.com","name":"axway-npm"},{"email":"bladedancer.gavin@gmail.com","name":"bladedancer"},{"email":"ddimonov@axway.com","name":"ddimonov-axway"},{"email":"ashtripathi@axway.com","name":"neon-axway"},{"email":"vchauhan@axway.com","name":"vchauhan"},{"email":"mdimitrova@axway.com","name":"mdimitrova"},{"email":"pdzhorev@axway.com","name":"pdzhorev"},{"email":"ahurst@axway.com","name":"axway_alasdair"},{"email":"pl.todorov@gmail.com","name":"pltod2"},{"email":"mbonchev@axway.com","name":"mbonchev-axway"},{"email":"bchristiansen@axway.com","name":"axway-vertex"},{"email":"npm.modules@axway.com","name":"buildernpmuser"}],"readme":"","readmeFilename":""}