{"_id":"serverless-azure-functions","_rev":"127-61a1a653acc1b23b6f4eaa8e1806cc79","name":"serverless-azure-functions","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","dist-tags":{"latest":"2.2.1","beta":"1.0.2-39"},"versions":{"0.1.0":{"name":"serverless-azure-functions","version":"0.1.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"async":"^2.1.2","bluebird":"^3.4.6","chalk":"^1.1.3","lodash":"^4.16.6","fs-extra":"^2.0.0","jszip":"^3.1.3","request":"2.79.0","ms-rest-azure":"^1.15.4","azure-arm-resource":"1.6.1-preview"},"devDependencies":{"eslint":"^3.15.0","eslint-config-standard":"^6.2.1","eslint-plugin-promise":"^3.4.1","eslint-plugin-standard":"^2.0.1"},"engines":{"node":">= 6.5.0"},"gitHead":"629ade76534b82df0977f9e629906ded29a94fce","_id":"serverless-azure-functions@0.1.0","scripts":{},"_shasum":"49c5a6c0e2310a9ea6d1c60c0e5cd63bd736749f","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.5.0","_npmUser":{"name":"christopheranderson","email":"chrande@outlook.com"},"dist":{"shasum":"49c5a6c0e2310a9ea6d1c60c0e5cd63bd736749f","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.1.0.tgz","integrity":"sha512-17eetDqQf05yZ7f9iw736JkofxHGCpaocf4410V7mRsX46JBMqfnN3+7f/ac0dxhhcNWJNUyoPGH4M+yhAhTIg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCCO9K96sSHVou2QLKAsnfERAWeNceRe2LJGn0JCyapSwIhAIJmB6bPGmleswmmrtUbDSOllYoFCqY8xal9Bwu8PzH8"}]},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/serverless-azure-functions-0.1.0.tgz_1487711278221_0.4487984322477132"},"directories":{}},"0.1.1":{"name":"serverless-azure-functions","version":"0.1.1","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"async":"^2.1.2","bluebird":"^3.4.6","chalk":"^1.1.3","lodash":"^4.16.6","fs-extra":"^2.0.0","jszip":"^3.1.3","request":"2.79.0","ms-rest-azure":"^1.15.4","azure-arm-resource":"1.6.1-preview"},"devDependencies":{"eslint":"^3.15.0","eslint-config-standard":"^6.2.1","eslint-plugin-promise":"^3.4.1","eslint-plugin-standard":"^2.0.1"},"engines":{"node":">= 6.5.0"},"gitHead":"14df98b035cc336555e8121957b1b917d57ed0d8","_id":"serverless-azure-functions@0.1.1","scripts":{},"_shasum":"570438bba99ebd57cbe503d47df40708a572f003","_from":".","_npmVersion":"3.3.2","_nodeVersion":"4.0.0","_npmUser":{"name":"christopheranderson","email":"chrande@outlook.com"},"dist":{"shasum":"570438bba99ebd57cbe503d47df40708a572f003","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.1.1.tgz","integrity":"sha512-RCdmgWAiGbT2mG6TMtGDmha8uLztMbuE+M6PfX1phcErYGw/yWxdj5NZLEeA9sZF0PxmsK+Ihln/3BT4aWO2vw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGjxRnLsphzV+CyHtibYld8uA8Q1d8gGkwVMf41Obi5rAiAT5bpEsirVQ4griy7HIeVJDmqfvTreC35FtE7AWHshIQ=="}]},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/serverless-azure-functions-0.1.1.tgz_1487832792014_0.5230242784600705"},"directories":{}},"0.1.2":{"name":"serverless-azure-functions","version":"0.1.2","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"async":"^2.1.2","bluebird":"^3.4.6","chalk":"^1.1.3","lodash":"^4.16.6","fs-extra":"^2.0.0","request":"2.79.0","ms-rest-azure":"^1.15.4","azure-arm-resource":"1.6.1-preview","zip-folder":"1.0.0"},"devDependencies":{"eslint":"^3.15.0","eslint-config-standard":"^6.2.1","eslint-plugin-promise":"^3.4.1","eslint-plugin-standard":"^2.0.1"},"engines":{"node":">= 6.5.0"},"gitHead":"e6d45788b9fe3bed9573cb8f1b3a4c834bb4f941","_id":"serverless-azure-functions@0.1.2","scripts":{},"_shasum":"2654194e11e3ee2c3f4b8d554cfbb7a5141c3b3a","_from":".","_npmVersion":"3.10.10","_nodeVersion":"6.9.4","_npmUser":{"name":"pgopa","email":"pgopa@microsoft.com"},"dist":{"shasum":"2654194e11e3ee2c3f4b8d554cfbb7a5141c3b3a","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.1.2.tgz","integrity":"sha512-pVGL2sgdxcBlfPkGXLzSE31oMEPtcqQRLUjqNbdQVrYoI5I5vPTjHx1mY2+mCvcBaMHwv2e3y8N5Vq9ecgZLSQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCnBVbrMBJxx5dIu225TcVIvU0C/t8s8r+kRvh0XX0oFQIgCH5cDjPIib2WTZA+rqeRe0pBHppS9N0lS3V1rIlb+TE="}]},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/serverless-azure-functions-0.1.2.tgz_1490037021086_0.5107477663550526"},"directories":{}},"0.1.3":{"name":"serverless-azure-functions","version":"0.1.3","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"async":"^2.1.2","az-login":"^0.1.7","azure-arm-resource":"1.6.1-preview","bluebird":"^3.4.6","chalk":"^1.1.3","fs-extra":"^2.0.0","jsonpath":"^0.2.11","lodash":"^4.16.6","ms-rest-azure":"^1.15.4","request":"2.79.0","zip-folder":"1.0.0"},"devDependencies":{"eslint":"^3.15.0","eslint-config-standard":"^6.2.1","eslint-plugin-promise":"^3.4.1","eslint-plugin-standard":"^2.0.1"},"engines":{"node":">= 6.5.0"},"gitHead":"5f86decb698b6fc3451df7649a9b9aaf849419fc","_id":"serverless-azure-functions@0.1.3","scripts":{},"_shasum":"b95aa78c1dc6f7fed23f74d83e88a51877b99912","_from":".","_npmVersion":"3.10.10","_nodeVersion":"6.9.4","_npmUser":{"name":"pgopa","email":"pgopa@microsoft.com"},"dist":{"shasum":"b95aa78c1dc6f7fed23f74d83e88a51877b99912","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.1.3.tgz","integrity":"sha512-rxLgWgaL1AzsN1ENP/w7a0F/Y5IR5jcDl8Fuq7mlCKh/7mLcxgaM/niAwwzym2f9YkWKJ5mp2tHl68EN0d86ig==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD/PpwOeXgvgODWODTy4TuIceLqO1LXO2HG1FM8I+ZEtAIgGUvP4TGMiHko5PP7xIQGu26rv12+eFL2Rn2EnHKRvbQ="}]},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"}],"_npmOperationalInternal":{"host":"packages-18-east.internal.npmjs.com","tmp":"tmp/serverless-azure-functions-0.1.3.tgz_1493830738583_0.512596610467881"},"directories":{}},"0.2.0":{"name":"serverless-azure-functions","version":"0.2.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"async":"^2.1.2","az-login":"^0.1.7","azure-arm-resource":"1.6.1-preview","bluebird":"^3.4.6","chalk":"^1.1.3","fs-extra":"^2.0.0","jsonpath":"^0.2.11","lodash":"^4.16.6","ms-rest-azure":"^1.15.4","request":"2.79.0","zip-folder":"1.0.0"},"devDependencies":{"eslint":"^3.15.0","eslint-config-standard":"^6.2.1","eslint-plugin-promise":"^3.4.1","eslint-plugin-standard":"^2.0.1"},"engines":{"node":">= 6.5.0"},"gitHead":"430ae5fe73cc177adf74c2b52dd84f6aab99e3a0","_id":"serverless-azure-functions@0.2.0","_npmVersion":"5.0.0","_nodeVersion":"7.10.0","_npmUser":{"name":"fiveisprime","email":"maherna@microsoft.com"},"dist":{"integrity":"sha512-qzd5IZvMER3UkvE78FJt18U7GjOiFA/UOdYIo7faE8ylKYlxhrTzC+/MKC7zeRGKykn7Lio7E5yziTlum1Bj2A==","shasum":"7ef64220d30e28504301156d86049eebae756a5c","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.2.0.tgz","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC+4ULhYSXq78WsRU1fT7rCKiXxsRR3I3NHVFlUsZjcjQIhAPUYlOatMhiVK3SaAxobOGXHG/i0i9p1o9NH7wqSDu8/"}]},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"fiveisprime","email":"maherna@microsoft.com"},{"name":"lostintangent","email":"joncart@outlook.com"},{"name":"mattmason03","email":"matt.mason03@gmail.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions-0.2.0.tgz_1496357403238_0.18282476626336575"},"directories":{}},"0.3.0":{"name":"serverless-azure-functions","version":"0.3.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"scripts":{"test":"eslint **/*.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"async":"^2.1.2","az-login":"^0.2.3","azure-arm-resource":"1.6.1-preview","bluebird":"^3.4.6","chalk":"^1.1.3","fs-extra":"^2.0.0","jsonpath":"^0.2.11","lodash":"^4.16.6","ms-rest-azure":"^1.15.4","request":"2.81.0","zip-folder":"1.0.0"},"devDependencies":{"eslint":"3.19.0"},"engines":{"node":">= 6.5.0"},"gitHead":"f2eeb21fe665730ea4d7df752d91cc7f70a7c50a","_id":"serverless-azure-functions@0.3.0","_npmVersion":"5.1.0","_nodeVersion":"8.1.3","_npmUser":{"name":"fiveisprime","email":"maherna@microsoft.com"},"dist":{"integrity":"sha512-w3ieDNhT1w/b72HNqsuKA1wyYBM3ZiVM0d1o++xF0+0L6u8sjMmj+9Hl4fA1Sj0jXz+9xhao5wdGVaw5yEaoMQ==","shasum":"bb0301703942bad7f49c4c914ead9c06bdf20255","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.3.0.tgz","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHMh1qAcjykekglpBJxc8wsfcEjAbJq4mU50KVY4st4SAiEA+/2SUbaJdAdicsd1pNcdK6GR74fqaoV1FFFPffxsCS0="}]},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"fiveisprime","email":"maherna@microsoft.com"},{"name":"lostintangent","email":"joncart@outlook.com"},{"name":"mattmason03","email":"matt.mason03@gmail.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions-0.3.0.tgz_1500566083549_0.6733083932194859"},"directories":{}},"0.4.0":{"name":"serverless-azure-functions","version":"0.4.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"scripts":{"test":"eslint **/*.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"az-login":"^0.3.0","azure-arm-resource":"^2.0.0-preview","bluebird":"^3.4.6","fs-extra":"^2.0.0","jsonpath":"^0.2.11","lodash":"^4.16.6","request":"2.81.0","zip-folder":"1.0.0"},"devDependencies":{"eslint":"3.19.0"},"engines":{"node":">= 6.5.0"},"gitHead":"407e36954b0a66586b13fd8d7f27f94e569b4597","_id":"serverless-azure-functions@0.4.0","_npmVersion":"5.3.0","_nodeVersion":"8.2.1","_npmUser":{"name":"fiveisprime","email":"maherna@microsoft.com"},"dist":{"integrity":"sha512-9EcMZn5FK59WA7VFH2XCYZRsewz0Vt4Se00vXIqe806rnLjNTa+BecvRw1arx0MwnTI7xOvADefmUCjMbTKCXA==","shasum":"351393c725a4d31759a08f5df43802807c20334b","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.4.0.tgz","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBv2F3JAC7nml49JvYNpZK6Sllo3V3FS6rkUSaJ6FW30AiBV+bQeA1HFUXKmwX1sKJMEXOnq8y8/hDp6cTY2NbtlhQ=="}]},"maintainers":[{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"matt.mason03@gmail.com","name":"mattmason03"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"azuresdk@outlook.com","name":"windowsazure"},{"email":"chrande@outlook.com","name":"christopheranderson"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions-0.4.0.tgz_1501376331867_0.3439816937316209"},"directories":{}},"0.5.0":{"name":"serverless-azure-functions","version":"0.5.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"scripts":{"test":"eslint **/*.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"az-login":"^0.3.0","azure-arm-resource":"^2.0.0-preview","bluebird":"^3.4.6","jsonpath":"^0.2.11","lodash":"^4.16.6","request":"2.81.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"eslint":"3.19.0"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"63309fd99d0f6107bf80850d098e4d0d959c5794","_id":"serverless-azure-functions@0.5.0","_npmVersion":"5.7.1","_nodeVersion":"9.8.0","_npmUser":{"name":"fiveisprime","email":"maherna@microsoft.com"},"dist":{"integrity":"sha512-Cp/t90Rj1z/OScHoDEqFr/78JcvmiUpl6gUXvsaMp1EAiUDVGeRS3BroHrC+CQtmPTXSLeDSIZgLQ9azn18Z4w==","shasum":"e8f9c4cee0a6c6dde72f7d7e9885352dd1ff4456","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.5.0.tgz","fileCount":31,"unpackedSize":127902,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBliUb9q0j1SbyePHttUS3ObMx9ndNtrzpY0+MGCTSlbAiEAiCgZa9XfQSqSlk7N6EfLAw+b3utUXuO4FqU1o+BwXv0="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_0.5.0_1521001698704_0.524222968274163"},"_hasShrinkwrap":false},"0.6.0":{"name":"serverless-azure-functions","version":"0.6.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"scripts":{"test":"eslint **/*.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"az-login":"^0.3.0","azure-arm-resource":"^2.0.0-preview","bluebird":"^3.4.6","jsonpath":"^0.2.11","lodash":"^4.16.6","request":"2.81.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"eslint":"3.19.0"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"1a8692d0dd3a959a4e1c6ac2abc7c74b61acfc0b","_id":"serverless-azure-functions@0.6.0","_npmVersion":"5.8.0","_nodeVersion":"8.11.1","_npmUser":{"name":"fiveisprime","email":"maherna@microsoft.com"},"dist":{"integrity":"sha512-ph0VMaxTWBtxfniOny+9QTPRSawpKldpjzsZ3touHFkLI4+QqHrA618ARc/Gz/5WRaIhPmP+pdzzw2HP1FFCZg==","shasum":"593f1970c457fc6cc3d2786f152874bc8ef1d7ac","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.6.0.tgz","fileCount":31,"unpackedSize":128017,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJa4e2bCRA9TVsSAnZWagAAjAQP/1w365XRAMVy6qsP0qqb\nT57zTzvV91Lg0xRn9vDqMCcNVVO+d8hyfVwC8GFv8cBh2XSRL1FJWIjIxjCT\nRiZUP1bkgWgLlhA8Srf/+joP0nf3sX/DlyqyHC23aaQIWMYPcN5gTQE9D37t\nJCEYbxTrZ2uCFG0lNJC9XNZcyVDxJyr+K4PDx6ollaeXwN3z7djClB/ke1Bl\n1GT/N9Y998YvKbdpG+3HbACwECuEtenW1uzysnTg+jkFZgKQ2ompOyJIuocN\ngAg/XiImW9NjzKRC6wnhMMChzFoEEwnGu1fEVxtflxUDOXUZ1juhESsMo8/5\n/UwC+LFHptpYD6N/APGPE3Gt1qgwww/mFQ78ol/PmkTWnBMajVkTTYcwstIF\ns0tje8zR3pzThLuXqQ9mKSzc9VvqEAbtwgTlB/IRqY5DBsNIiyCeFU7Czxts\nRjF7yqBkDhADjlSqOz7JpEWUlYbkPUKv6d5rue8XTOsCNZdcrCvXeRM5zNgM\n1fBN+1gg0I5AKu1j3gA2Hjsy+xg6YlMWcYH/DSvEhMbsj8nB459OiJdVd6yC\n9G83OGXBZArQRe3Ae2SDwyHaVS6vIS/FzHnEdCb5+rWNSBr3dlsOmlksGcji\nrbH+KAz1t1e95oq5kN9hGpyRPAWapDZ96veGEk7Ou8D7oywsBDTortXp9RXZ\n2qOd\r\n=fhcT\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD3xrnLuhwA6+7j6LdM66de/gihIwz0e+4ABwy3WveoSAIgGWCaexOEnr+g+2mMAhvU9duNjpB2DqIK0MOYn0WW7Xc="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_0.6.0_1524755866941_0.40073508103947875"},"_hasShrinkwrap":false},"0.7.0":{"name":"serverless-azure-functions","version":"0.7.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"index.js","author":{"name":"Azure Functions"},"scripts":{"test":"eslint **/*.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"az-login":"^0.3.0","azure-arm-resource":"^2.0.0-preview","bluebird":"^3.4.6","jsonpath":"^0.2.11","lodash":"^4.16.6","request":"2.81.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"eslint":"3.19.0"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"2ac5123e3233d01522ec4aebe72c9889e1ab82be","_id":"serverless-azure-functions@0.7.0","_npmVersion":"6.0.1","_nodeVersion":"8.12.0","_npmUser":{"name":"fiveisprime","email":"maherna@microsoft.com"},"dist":{"integrity":"sha512-U+Pooah0xgKyPyLdxssNvfIvY6I03E/5/pyRXNZ+Lw0tZ8EXW5kg6zRQeLGhxpjuOpDK8UldjpauzPass0on3g==","shasum":"8e3c8713b48979680042c070d017fb16b43226bd","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-0.7.0.tgz","fileCount":31,"unpackedSize":128018,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbyQkGCRA9TVsSAnZWagAAHjQP/iTIbYHk932OVNzumT4O\nObPBgtQBdwRu8WOhjyNOQeYfTp2W5MUhYhCwP5UkBxBusX0VnI0w6jhkyL+V\nqZ9sefij8K+MgpOdx4SqPvQeD/C/cN8q5+VK0s6RAaMiV0FA4Ki2jUu3U7m+\nsxW+fMHUXubK1rx4RmFHGfOwFjrWVR/AwxS4yxlHrFATvNgFJDoeKZNC9hFh\nDrjhIRgIEgjk/Tf9deFqbBLLZkuEZMDbHzAoxK3A5NqBRNhcBcTnletL+s1B\nCrG35bpCTSIWpN9dFE9NQsTkI3OHDDQfyY6iKbMQznEBKIBH0MnNW1bLsFJh\ndH7ee4CQCE/8x6PPD/IWo7ckiy6Pu6i1UCbLhxpy3PIxRAVH1LHcgQAzBupl\nQRoJVInYW3INgayCZ9Z8y8382JfeiWwVpQOm2MBpurelwIdOll6MPz/1MhOS\nJs5a9TT++zTgxUwp1nPTUhgLbomc+jhj0X8UzZbAanBXfStZawv4lVSYItPX\nVGIfsLImeEmeraL0+2gWKMLNeHMv0sEKDYd2p3iBGl0EUBPNJ0qdAAOGzV4Y\n2IHzl4wbFZpLJ3IkgwIhgjbPCzAvUkG4rJurL0+pWwdQKK/44RMijC4PMSTu\nmGp9+vKxKGFKABHrHAFoLymXTNTLby6FF+0jiH9yFFtl62sJ18J5elZv1/Uy\nUrHl\r\n=JNbT\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCLfsCEhQX2hZwf5xVpvL8P6oauGjvsAi3LsF3bgKCEjwIhAL8CGEtN9QmKB3YOF9eej5xjeqQY+Gwo59JSoB4Wklhb"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_0.7.0_1539901701640_0.9219092606011239"},"_hasShrinkwrap":false},"1.0.0-1":{"name":"serverless-azure-functions","version":"1.0.0-1","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","prebuild":"shx rm -rf lib/ && npm run test","build":"tsc"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/ms-rest-nodeauth":"^1.0.1","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"2f15928d9c24cc8ed3d20d359652cdf4ccc4e795","readme":"# Azure Functions Serverless Plugin \n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Getting started\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure service\n\n1. Create a new service using the standard Node.js template, specifying a unique name for your app: `serverless create -t azure-nodejs -p `\n2. CD into the generated app directory: `cd `\n3. Install the app's NPM dependencies, which includes this plugin: `npm install`\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\nsls func add -n {functionName}\n```\n\nThis will create a new `{functionName}` directory at the root of your application with `index.js` and `function.json` inside the directory. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\nsls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}` directory and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Deploy, test, and diagnose your Azure service\n\n1. Deploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n ```bash\n serverless deploy\n ```\n\n > Note: Once you've authenticated, a new Azure \"service principal\" will be created, and used for subsequent deployments. This prevents you from needing to manually login again. See [below](#advanced-authentication) if you'd prefer to use a custom service principal instead.\n\n2. Invoke a function, in order to test that it works:\n\n ```bash\n serverless invoke -f hello\n ```\n\n3. Stream the output logs for your function:\n\n ```bash\n serverless logs -f hello\n ```\n \n4. Make some code changes, `deploy` again, view logs, etc. and provide us feedback on how to make the experience even better!\n\n > Note: If you're working on a single function, you can use the `serverless deploy function -f ` command instead of `serverless deploy`, which will simply deploy the specified function instead of the entire service.\n\nIf at any point, you no longer need your service, you can run the following command to remove the Azure Functions that were created, and ensure you don't incur any unexpected charges:\n\n```bash\nserverless remove\n``` \n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended for most users. However, if you'd prefer to create an Azure [\"service principal\"](https://github.com/Azure/azure-sdk-for-node/blob/master/Documentation/Authentication.md#2-azure-cli) yourself, you can indicate that this plugin should use its credentials instead, by setting the following environment variables:\n\n**Bash**\n```bash\nexport azureSubId=''\nexport azureServicePrincipalTenantId=''\nexport azureServicePrincipalClientId=''\nexport azureServicePrincipalPassword=''\n```\n\n**Powershell**\n```powershell\n$env:azureSubId=''\n$env:azureServicePrincipalTenantId=''\n$env:azureServicePrincipalClientId=''\n$env:azureServicePrincipalPassword=''\n```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run-script build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin. \n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-1","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-8fyzJw00NmmJoa5SQzI3jxR6O4CJgLlkPpwsJ7dVsVSZE1ArRkL5X0lV1UGieEgmF/+z0VKrrQrQPLn4mj8L+Q==","shasum":"ca8e71a09f8e9aee2507cbe3157bff0db85f157b","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-1.tgz","fileCount":111,"unpackedSize":396606,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdCEqkCRA9TVsSAnZWagAAZDIP/1zTNS1UgjVNtUKtZmfo\n3zX3cvnDPTb0kS425jjps6ZB/YyXfEY2qs4/GDCZ5GQcJMMFgThTFiXRXmu0\nnoDWu2HesFBpbhUXAqysJBTc5Dcq6ce0jDVPKa2ujvDnEDqmCbuRAQBdc5J8\nDGCXbvx97/irjSXsE3bTDaLxA9BGo+cE1UrLpMxWZFmCjuU/VeLqYkU0NKdy\nlrQhMfZrylncasnkTsVSa/VhJ5y9UYEcXnbMToaoxhp4xjVdiiP5CvwyjRff\neAjQMWjffrOqnQjeUKZlXXB4x9WQO17gJ4EOYSFV21u6FRcXvctd+8BB7Jmz\nZzJRPUC1zMXT6qsqKa3aTPO1+N+USx1Js71k/c9VqzusqzQ9SQ0ytA67XDYU\n3mSm2JY5L1H4+Hqi4ZbwerrVVT2BclRxR/hkMdCMeI5HLgC4v7mwNOBY3AEG\nzyHoolgW0QM2bd9DEkloNkzFvEOQfbULKCxK/9r2MRbrD25qcZqWou2PWwA2\nxOviTlnc6F5XBvK/YNOwITXructeVddcfbv1+l+IrtiS+5ukvhWagvEcl8r5\n7Keg436zERX2tWzD+ncshquab26uuRkcsMJssN3ynyNWVP1hxoRJpxWKPYmV\n5++c15Z6CGhiIoOSPrcsphiNZZeKjxluG4x2Q0EfvElYuUE8FsOm9hfNNRxe\nuAFh\r\n=NL1k\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDh4iNWaBOQ/IjN1oJGjtGq/19bqt9dwqtHFnARcu41OQIgQfLIjsczM/18tx7uTORB45mXzSc6SSb3zShGPacCd5g="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-1_1560824483624_0.13174049593027792"},"_hasShrinkwrap":false},"1.0.0-2":{"name":"serverless-azure-functions","version":"1.0.0-2","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","prebuild":"shx rm -rf lib/ && npm run test","build":"tsc"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/ms-rest-nodeauth":"^1.0.1","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"2ee56720ded88421acb2c106357f4721f61b3bbf","readme":"# Azure Functions Serverless Plugin \n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Getting started\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure service\n\n1. Create a new service using the standard Node.js template, specifying a unique name for your app: `serverless create -t azure-nodejs -p `\n2. CD into the generated app directory: `cd `\n3. Install the app's NPM dependencies, which includes this plugin: `npm install`\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\nsls func add -n {functionName}\n```\n\nThis will create a new `{functionName}` directory at the root of your application with `index.js` and `function.json` inside the directory. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\nsls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}` directory and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Deploy, test, and diagnose your Azure service\n\n1. Deploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n ```bash\n serverless deploy\n ```\n\n > Note: Once you've authenticated, a new Azure \"service principal\" will be created, and used for subsequent deployments. This prevents you from needing to manually login again. See [below](#advanced-authentication) if you'd prefer to use a custom service principal instead.\n\n2. Invoke a function, in order to test that it works:\n\n ```bash\n serverless invoke -f hello\n ```\n\n3. Stream the output logs for your function:\n\n ```bash\n serverless logs -f hello\n ```\n \n4. Make some code changes, `deploy` again, view logs, etc. and provide us feedback on how to make the experience even better!\n\n > Note: If you're working on a single function, you can use the `serverless deploy function -f ` command instead of `serverless deploy`, which will simply deploy the specified function instead of the entire service.\n\nIf at any point, you no longer need your service, you can run the following command to remove the Azure Functions that were created, and ensure you don't incur any unexpected charges:\n\n```bash\nserverless remove\n``` \n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended for most users. However, if you'd prefer to create an Azure [\"service principal\"](https://github.com/Azure/azure-sdk-for-node/blob/master/Documentation/Authentication.md#2-azure-cli) yourself, you can indicate that this plugin should use its credentials instead, by setting the following environment variables:\n\n**Bash**\n```bash\nexport azureSubId=''\nexport azureServicePrincipalTenantId=''\nexport azureServicePrincipalClientId=''\nexport azureServicePrincipalPassword=''\n```\n\n**Powershell**\n```powershell\n$env:azureSubId=''\n$env:azureServicePrincipalTenantId=''\n$env:azureServicePrincipalClientId=''\n$env:azureServicePrincipalPassword=''\n```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run-script build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin. \n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-2","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-YVaayxadZ7LVV6C7jLzhU+N4dyOw49/wXa0x77e59RtLQOAUAQj5oWbdZJ3Np3DgIB77u/CJMIoE6KBOgxZAjg==","shasum":"2678100428a31d658b9fc78cb010dc8a1b3d5c2a","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-2.tgz","fileCount":111,"unpackedSize":396606,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdCEvNCRA9TVsSAnZWagAAj6oP/0/CJEICLfiETN/GlHl9\n9Zy2748KvybgYC+mmBIiCgl/qhCkoYsN0kTkGxnRO2kvn54S46/yzRwDFLbu\nMP76KQSAqTWaxK8ydhfmhgMha9m1iaZ4lp6vcqcSwHckx7obeAcOVdqjpavY\n18lFx3Qe8ga2/u8jVRNH9giRWq8wch6AbXKDMfZKaHBE6LtfLeh+c88pu+ZB\n+ZcE51QzBINiUlz0T6f7C3hZZuQojIgKWfkhNB4LImIJl20zp44XWY0EiqVv\nghSpGehgEicAz9aAOa60ioomKGuuVR5JaW4gB8JZC7THvScbNCIxU3a7SPD3\n1qPFy9F7N/4Do0B22eE8IXIhOpOJoXlLfTckHBEDynkiFRRC754qn8/kiYGM\nwx1yHa8M4Xy5yISvDIDexaBlFXhDfjuSi9OVeBhJ+YW68Fv3kq/IEP47LwXp\np1MkriVIgKoWQEW1ZnyUh4fBNDyCyUoSP2USOs/fJsJLPrJHHQHed32/IdF2\nBqgENiXJ396WeVpyW3h8clteTGUYRYZ3DvPFplhtjNuYvHD/Y3AT3koar9tQ\nEGQDBA6UkwCW+JpMngdRjH5WtArUxWzgEfHEGQVAvwxPIt2N+HUBvQpHG3wE\nidNO+YNa3/qyL/ziXs+yYvhAQPqtE1PhSHGhAqze1IoLye6OwcWYuIiO+yXG\n2F0q\r\n=CkW4\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDW8kTZ0HUq3kg9QCxx7Ff31k0SeqaZidIBmYz9xW6eqQIgBVDN5YbsxreYEYqDLe3jb3z2NEBgqcA8UloRK8SNw6I="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-2_1560824781038_0.5103490206629759"},"_hasShrinkwrap":false},"1.0.0-3":{"name":"serverless-azure-functions","version":"1.0.0-3","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","prebuild":"shx rm -rf lib/ && npm run test","build":"tsc"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/ms-rest-nodeauth":"^1.0.1","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"6ecd91e241fdabdc1a24af2a90870a7ca38a7688","readme":"# Azure Functions Serverless Plugin \n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Getting started\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure service\n\n1. Create a new service using the standard Node.js template, specifying a unique name for your app: `serverless create -t azure-nodejs -p `\n2. CD into the generated app directory: `cd `\n3. Install the app's NPM dependencies, which includes this plugin: `npm install`\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\nsls func add -n {functionName}\n```\n\nThis will create a new `{functionName}` directory at the root of your application with `index.js` and `function.json` inside the directory. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\nsls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}` directory and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Deploy, test, and diagnose your Azure service\n\n1. Deploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n ```bash\n serverless deploy\n ```\n\n > Note: Once you've authenticated, a new Azure \"service principal\" will be created, and used for subsequent deployments. This prevents you from needing to manually login again. See [below](#advanced-authentication) if you'd prefer to use a custom service principal instead.\n\n2. Invoke a function, in order to test that it works:\n\n ```bash\n serverless invoke -f hello\n ```\n\n3. Stream the output logs for your function:\n\n ```bash\n serverless logs -f hello\n ```\n \n4. Make some code changes, `deploy` again, view logs, etc. and provide us feedback on how to make the experience even better!\n\n > Note: If you're working on a single function, you can use the `serverless deploy function -f ` command instead of `serverless deploy`, which will simply deploy the specified function instead of the entire service.\n\nIf at any point, you no longer need your service, you can run the following command to remove the Azure Functions that were created, and ensure you don't incur any unexpected charges:\n\n```bash\nserverless remove\n``` \n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended for most users. However, if you'd prefer to create an Azure [\"service principal\"](https://github.com/Azure/azure-sdk-for-node/blob/master/Documentation/Authentication.md#2-azure-cli) yourself, you can indicate that this plugin should use its credentials instead, by setting the following environment variables:\n\n**Bash**\n```bash\nexport azureSubId=''\nexport azureServicePrincipalTenantId=''\nexport azureServicePrincipalClientId=''\nexport azureServicePrincipalPassword=''\n```\n\n**Powershell**\n```powershell\n$env:azureSubId=''\n$env:azureServicePrincipalTenantId=''\n$env:azureServicePrincipalClientId=''\n$env:azureServicePrincipalPassword=''\n```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run-script build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin. \n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-3","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-qHDEKhkTt09Jy40+/Vfnz1mdoBKNCKvS/+qPYqS3VEPOaJr+AyGCQ97IIOdth0WWLTFB3G0JZiPDPS4UMdKs4w==","shasum":"52b3a7997a34792b04fffb9095fec7013dde3975","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-3.tgz","fileCount":111,"unpackedSize":396606,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdCE8xCRA9TVsSAnZWagAAe5EP/RPGJPnmTUSMfEgDfMGD\nbdOqWTvU0x9FwwICBwjkWNHzgzU1tBAIkPlSz5n5w/YPIMVwa5rcPrKiGt7E\nCRDd1/za8SV+2iAqDxIqMfETS5KcyOffn/5ALudP/7zfgkg6R2UMRhd/S0PK\noac/L7y2HqYrQfuNbhCFT1Pmd/W7GFaXXRTVJ8piTHXQV05wDYwM7qGi0AJX\nJ+EpnwNR3DzWq38ZjA96hSksG2EDWP8ErgRo2xqgMJa0DSfYf1jJ4vU/tN4Z\nkV3ZT61cH/wXxYGxcZcUDNM1//O/lCimXcwS94n9md19HKmAgqpolSQupnC+\nId4yf65NHyHtH009Od1kSa0wDTRKUvUNUBgzOhu9DWqBFPo14/37QveV1jhb\n0vbm2pRzgjIxpT0qLEsZLA9jS7lqHopfRyJDKPW3iOmtWdqF/Ug6cBv3uC6I\nbue19ZjFZpHxfs2G1uhlI519zWotIfqho0p7LKZ9gAh+8SGHZNuHahNkkidU\nF3NKHZZexGAaM/xZMUjx/Wj6CA5NO5EmiGkcGdrwrvcnz/Llss4dDgmB3Bh8\nSrp0ZSOgyERRPLUvYz42Dxf3mFPdI9XM0FHHYf/PqH7dZVsMnKhfUd0FGqJ+\nJiC/LZLLXZoi+ddNPw25W5hP5dNqMVmgK0mf2AWX0Q6VNc5mZN0ELUiw1put\nQR81\r\n=I/vG\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD42ztIGahRJqxyfqqil4Yc5Mp5t3GcIMYuv83IG28FsQIgarEjboVoCnzSzxw04yEFbXtJAgIJz54Jq8coq102WCU="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-3_1560825648765_0.7073229856629177"},"_hasShrinkwrap":false},"1.0.0-4":{"name":"serverless-azure-functions","version":"1.0.0-4","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","prebuild":"shx rm -rf lib/ && npm run test","build":"tsc"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/ms-rest-nodeauth":"^1.0.1","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"c453882a87ad3f04e2fb948cf1f4c3555479bed5","readme":"# Azure Functions Serverless Plugin \n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Getting started\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure service\n\n1. Create a new service using the standard Node.js template, specifying a unique name for your app: `serverless create -t azure-nodejs -p `\n2. CD into the generated app directory: `cd `\n3. Install the app's NPM dependencies, which includes this plugin: `npm install`\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\nsls func add -n {functionName}\n```\n\nThis will create a new `{functionName}` directory at the root of your application with `index.js` and `function.json` inside the directory. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\nsls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}` directory and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\nnpm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files\nsls offline\n# Starts the function app\nnpm start\n```\n\nThe build process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nThe `npm start` script just runs `func host start`, but we included the `npm` script for ease of use.\n\nTo clean up files generated from the build, you can simply run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy, test, and diagnose your Azure service\n\n1. Deploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n ```bash\n serverless deploy\n ```\n\n > Note: Once you've authenticated, a new Azure \"service principal\" will be created, and used for subsequent deployments. This prevents you from needing to manually login again. See [below](#advanced-authentication) if you'd prefer to use a custom service principal instead.\n\n2. Invoke a function, in order to test that it works:\n\n ```bash\n serverless invoke -f hello\n ```\n\n3. Stream the output logs for your function:\n\n ```bash\n serverless logs -f hello\n ```\n \n4. Make some code changes, `deploy` again, view logs, etc. and provide us feedback on how to make the experience even better!\n\n > Note: If you're working on a single function, you can use the `serverless deploy function -f ` command instead of `serverless deploy`, which will simply deploy the specified function instead of the entire service.\n\nIf at any point, you no longer need your service, you can run the following command to remove the Azure Functions that were created, and ensure you don't incur any unexpected charges:\n\n```bash\nserverless remove\n``` \n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended for most users. However, if you'd prefer to create an Azure [\"service principal\"](https://github.com/Azure/azure-sdk-for-node/blob/master/Documentation/Authentication.md#2-azure-cli) yourself, you can indicate that this plugin should use its credentials instead, by setting the following environment variables:\n\n**Bash**\n```bash\nexport azureSubId=''\nexport azureServicePrincipalTenantId=''\nexport azureServicePrincipalClientId=''\nexport azureServicePrincipalPassword=''\n```\n\n**Powershell**\n```powershell\n$env:azureSubId=''\n$env:azureServicePrincipalTenantId=''\n$env:azureServicePrincipalClientId=''\n$env:azureServicePrincipalPassword=''\n```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run-script build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin. \n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-4","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-mAcPSC8eVdLxAcNPODE3GC5KkkZqurkH6USsJkEk/DWkm8nJNhmRVZycXVh6m9WhP8MdK8ouh98LV4FhyE1yoA==","shasum":"90497a425861b6891b5626c9846e68ac6ddd6f5a","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-4.tgz","fileCount":116,"unpackedSize":425786,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdCre5CRA9TVsSAnZWagAAg1AQAINaZO8I3JyKthxIjS9t\nVZo79i9IHD7mX8TT4DvPl3AQ6OTev3HqPI57VvTy+vqHDEE0sPwsTn8eoUCi\nwd8sunpHxNEVb7hk09Gdbu2zEtG5zr2ik3vLWadKcuSDJGehokpukyX0nHjA\nFY+ttLmF1tPXTtndxViWUylVM0KHVEBn3y/A3U9XFcd1yiglFyJLEKOZKNbe\nGrWnP73PCJVYblxXNntCr53ZDxKJpVm2rGgyzDdtRXCYFD7YASVYYgAn5spQ\nugQdgIoEmM5cgdLgYN/JVd5tcDCuj8Ye4447OMCIYeACzP1k/2OCLdRSDsbe\nxMnQy/wU/eWz/K6+h/175dETxEZxb5UZm3v5JDiCVtSCt4fi1vZjmnsM2mFN\nJCIrCTGztHuEhsy3WlrKP7Y3+sqOFkuod9rGqUb17qr5+2MqTGicIkDmD8Af\nU6rW8RFrL/4V7UqNso2Z1ipKbYDr/N3bnCb0hEg9sGhpGflna1bBNk431b+q\ndjKewxtq1vIVkjXTQnbP9OGi+dLG+QNibFuEHHgXxwvx0Y/MQhWegercXKa5\n2J6hO1zBTk3Tz/c5bs+H+u5SIcKqyz6wlvsM6XjZQrFLs1j7YZuFAQQC26Nl\nPO3x9Lu3xFAm9fKTg/oeuhvgATagf161fQVfHSwz/T8DjWlTf+9kXzCf1YsB\n9TaH\r\n=rlTr\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGfRooq6s1TWcJfuh/ggX6x7/aegvWL25/PSrL3qoCUpAiEAhwSgB1CbJCF6DsbKvQLOm3QzYKHmRuBnCd+7ZWiffOE="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-4_1560983480909_0.1357603717642153"},"_hasShrinkwrap":false},"1.0.0-5":{"name":"serverless-azure-functions","version":"1.0.0-5","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"2aeae38d899adfb6b1e753e6014e6343aa3cd377","readme":"# Azure Functions Serverless Plugin \n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Getting started\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure service\n\n1. Create a new service using the standard Node.js template, specifying a unique name for your app: `serverless create -t azure-nodejs -p `\n2. CD into the generated app directory: `cd `\n3. Install the app's NPM dependencies, which includes this plugin: `npm install`\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\nsls func add -n {functionName}\n```\n\nThis will create a new `{functionName}` directory at the root of your application with `index.js` and `function.json` inside the directory. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\nsls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}` directory and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\nnpm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files\nsls offline\n# Starts the function app\nnpm start\n```\n\nThe build process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nThe `npm start` script just runs `func host start`, but we included the `npm` script for ease of use.\n\nTo clean up files generated from the build, you can simply run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy, test, and diagnose your Azure service\n\n1. Deploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n ```bash\n serverless deploy\n ```\n\n > Note: Once you've authenticated, a new Azure \"service principal\" will be created, and used for subsequent deployments. This prevents you from needing to manually login again. See [below](#advanced-authentication) if you'd prefer to use a custom service principal instead.\n\n2. Invoke a function, in order to test that it works:\n\n ```bash\n serverless invoke -f hello\n ```\n\n3. Stream the output logs for your function:\n\n ```bash\n serverless logs -f hello\n ```\n \n4. Make some code changes, `deploy` again, view logs, etc. and provide us feedback on how to make the experience even better!\n\n > Note: If you're working on a single function, you can use the `serverless deploy function -f ` command instead of `serverless deploy`, which will simply deploy the specified function instead of the entire service.\n\nIf at any point, you no longer need your service, you can run the following command to remove the Azure Functions that were created, and ensure you don't incur any unexpected charges:\n\n```bash\nserverless remove\n``` \n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended for most users. However, if you'd prefer to create an Azure [\"service principal\"](https://github.com/Azure/azure-sdk-for-node/blob/master/Documentation/Authentication.md#2-azure-cli) yourself, you can indicate that this plugin should use its credentials instead, by setting the following environment variables:\n\n**Bash**\n```bash\nexport azureSubId=''\nexport azureServicePrincipalTenantId=''\nexport azureServicePrincipalClientId=''\nexport azureServicePrincipalPassword=''\n```\n\n**Powershell**\n```powershell\n$env:azureSubId=''\n$env:azureServicePrincipalTenantId=''\n$env:azureServicePrincipalClientId=''\n$env:azureServicePrincipalPassword=''\n```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run-script build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin. \n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-5","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-ybVzL0CtDTqbOTwIki9UVomBYJMBIlZx+LoKQgSC1sbRuPG3YSegeDsWbm2n2jrVixQBrWE/ftcp7jGQq7j1Ug==","shasum":"cba1de8af1ce53531736a437d6e8a4cf3c516036","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-5.tgz","fileCount":146,"unpackedSize":538060,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdFRpQCRA9TVsSAnZWagAA3A8P/3SsdYcNGPO1F5s6ghYK\nFVH2xTOOA/ZlJpT7X8gNfxdnWWoiXuortsxQ3chKMoqidFkMjzLne1UJCgJ9\ngwYkSAaoF7BZzzwnItr7NK1SBEbN8kex9oCIrv8noi3lZIKf1quu+OQJQy+j\n4RPn1h9WNKeEfJ70EH13UpFARAA/f7/lkW9RhwRjjudX0GJ9TMQ5kCPoD1OY\nOcE6JdQtp2wkbHbIA7kSmYJSsmf4D6F7qPMcdMfPGKCYTUqSdE5o5ydBsPmb\nFYiffHJtO+fkzSat5H0meO6O7aLsVwa6qt7cWEcFm2g2CTdVA2Gj3ky3c74X\nPN+jCc11HwmMbBEEv4BKS0h3hPpfhxY8nxEK75dcHrcnH3p3K4yuGgoj2/29\niSUtIHaR55gvS+lZutDm7ZCB57Pufox5BYuHx/NyRNz3HC2wqiUifEqGqKd1\nQW2il6QiUNLDIH7KfqMPtZJ29HvArgbyoV1+ykd/IFmxvM1Ui+5Puf7vhPmC\ntSQs/vKce1vn7VX0eCcsDUKZLsaM4/ONSFs9zBPrUa7iASuRTAm60LqwQJrx\nQPjpP7VK3y9lA/1R5Pmw6tnrZHtsJPEEkLNsFBgsjBtM9V31pgvir+y9Wl7l\n7VeL7wmC5t45ZWe9DiBxSTmYdwyWV3dLv2cMV5L/YWMVMJmfiWg4j4VgrHWo\n172n\r\n=876R\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFHMo6zm7E2u9PbI4uWeYT9HP29c9odBMQj7XsSLlmyoAiEAkl1NeMGYFnEfRoiaCB3Y7uPP8jLEn+uFpvcCPaIqYKg="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-5_1561664079755_0.19016870304522837"},"_hasShrinkwrap":false},"1.0.0-6":{"name":"serverless-azure-functions","version":"1.0.0-6","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"c056a69166cca71061165bfe8f0d3bad0dc9888d","readme":"# Azure Functions Serverless Plugin \n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Getting started\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure service\n\n1. Create a new service using the standard Node.js template, specifying a unique name for your app: `serverless create -t azure-nodejs -p `\n2. CD into the generated app directory: `cd `\n3. Install the app's NPM dependencies, which includes this plugin: `npm install`\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\nsls func add -n {functionName}\n```\n\nThis will create a new `{functionName}` directory at the root of your application with `index.js` and `function.json` inside the directory. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\nsls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}` directory and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\nnpm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files\nsls offline\n# Starts the function app\nnpm start\n```\n\nThe build process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nThe `npm start` script just runs `func host start`, but we included the `npm` script for ease of use.\n\nTo clean up files generated from the build, you can simply run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy, test, and diagnose your Azure service\n\n1. Deploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n ```bash\n serverless deploy\n ```\n\n > Note: Once you've authenticated, a new Azure \"service principal\" will be created, and used for subsequent deployments. This prevents you from needing to manually login again. See [below](#advanced-authentication) if you'd prefer to use a custom service principal instead.\n\n2. Invoke a function, in order to test that it works:\n\n ```bash\n serverless invoke -f hello\n ```\n\n3. Stream the output logs for your function:\n\n ```bash\n serverless logs -f hello\n ```\n \n4. Make some code changes, `deploy` again, view logs, etc. and provide us feedback on how to make the experience even better!\n\n > Note: If you're working on a single function, you can use the `serverless deploy function -f ` command instead of `serverless deploy`, which will simply deploy the specified function instead of the entire service.\n\nIf at any point, you no longer need your service, you can run the following command to remove the Azure Functions that were created, and ensure you don't incur any unexpected charges:\n\n```bash\nserverless remove\n``` \n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended for most users. However, if you'd prefer to create an Azure [\"service principal\"](https://github.com/Azure/azure-sdk-for-node/blob/master/Documentation/Authentication.md#2-azure-cli) yourself, you can indicate that this plugin should use its credentials instead, by setting the following environment variables:\n\n**Bash**\n```bash\nexport azureSubId=''\nexport azureServicePrincipalTenantId=''\nexport azureServicePrincipalClientId=''\nexport azureServicePrincipalPassword=''\n```\n\n**Powershell**\n```powershell\n$env:azureSubId=''\n$env:azureServicePrincipalTenantId=''\n$env:azureServicePrincipalClientId=''\n$env:azureServicePrincipalPassword=''\n```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run-script build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin. \n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification)\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-6","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-wTd/jYC5Fv7M62Sn4IHgJU+3vr/NI3GF72gbmv9yvF5enkh6Wse1Tsi34nO55LHidG3+07ztetVwRGX2izVmSA==","shasum":"0e3b61042d8d7a8348303cbcfa5c1d9e6d8e5364","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-6.tgz","fileCount":168,"unpackedSize":676652,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdKPA/CRA9TVsSAnZWagAAc6MP/jmlc4AMUGFiX37xxEvx\nDvI0F3wKiL7EASwKkoRYCruowprAZRLdV1hk9uBEuyrURg+zJK6Qn4/tjBTA\n4Rkla65qdPCGrNhQc9Txb4gR2+34tKKywqMR3isOGxCuYuP2b0QeOcqwIW1T\nWNcpARkIOU1j0hr2LYJlvSMrmGOKUfoGySyTAD0lcepqH0l7PICyncFfqB9i\nMs1VXj+LHZfyNwA/RVxpHd+kqgLbOot5ybkuTB6ilPFpb8It/GvIPl2DQ4XQ\n0HcAFOYea6gd0oULyn74Z6lQgsrZGwqdRwcL7GQIDRHRNpG2XIbjhDnlpvKL\nH017vVl/3H/zGlmVeRSiqqsdJhFUhku+Vr/xKbsZoxzXKey8is4ql5mG5PU5\nfCMIAfMAJ2JSq5JcGuL0pVkHwm8crHxVocreIQCkwfrwJPM9vP50XKLHHZSq\nUnXHkgRLjp2UzeJcMvN0uUPL9Z7KRFHEOh5RhBn2NZMBKYyULYIit9U2jT1k\nSmhLQFvojR6bPbDmQ326GBPP1DzmclXgonZjjQltV498ihmH45ojO2lyIal5\niNWA+t2H6PDKq91DPdLdAyS/EvYxJfVBRJubDWhOEtG8I0XbJDxffQ2xSU4u\nULbc+S3yZlX+V5MUFO9XsUXucWTcORfJQg3fhUHDwWC8HwvwCvJa7On5l5e4\nQqWm\r\n=H+Ek\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIH10xSGu8dYH9htDhTfxGFbQWEsz9vFbjTnJ7Sg+JKpaAiBw2I6+ookksbKB94j6u1sXu6K4rNyzzxuBrkEbBRAekg=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-6_1562964030744_0.47065068248051056"},"_hasShrinkwrap":false},"1.0.0-7":{"name":"serverless-azure-functions","version":"1.0.0-7","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"592e8382c4ea3f21796211bcae9b9944c16dd6bd","readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files\n$ sls offline\n# Starts the function app\n$ npm start\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nThe `npm start` script just runs `func host start`, but we included the `npm` script for ease of use.\n\nTo clean up files generated from the build, you can simply run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-7","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-n+4vfP9aSy7rlxHmLlWpkON2HhMoob81SowMjDbojABmqeFEBRzh6+uhi59cBFHgVGPhx4gtYVd92mwt/NZZtA==","shasum":"1c437470046ea11e39bc6c355ea3b660e4b63780","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-7.tgz","fileCount":168,"unpackedSize":689524,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdNdcBCRA9TVsSAnZWagAAVd8P/1Yezx2IgLwtfMJmjlv9\n0S2VawpF87vSnUyclLyYr7sMXOw7UZYbbUduFmqHVo6CSoRhFPWEFskRFJaM\noo+dRnOjm5br4Tf6EpWP2JTwVqj1q6iCbTHM5iQJ4bdS7d/XWy24SF6Ru3yW\nrCtXycIFRqPFA/mKEklHRuywd++HG+C1CfvvpL6gpX5xWTNLuKjw2I9HxuLo\npZTBymVSYsyOcI5o2MgJyH+3L2LDfQDfD540fOmPG/TwhHCgjtHUNDcLbOY5\n45x37bS34jJgZzkruDnm4H2/tVg4qMuRZzJiFif8JEZnxkEu8HZfM9c9uvAz\nXLPEn2ySBcdQSfGP5j6bwgjmIA2f07dpRrgeyVTK+lMcPf+3bkcG6w4nsAnb\nIwOMgLZIGQCNQ3gZcuNP+JnsGmdj2CVksc50TVA7ywt4F/uLKgcAd5fsNwVy\nFYNPFJ99o2qecIcAL3BqFkzyaJa9c+IjQE1bAFTMqYmtKVY0SWobNAb6ISxQ\naTJcPcx+/3VS4FGlPBVJejXjTzHtfEfMY0ft9l/vZ/uLfPn2At41XotWkT9n\ntCcWmv/lczeYEW95HdgiScTe2FbWYM3aGR4pjj2sqYsZYnozI0rl7SEUkaSJ\nmxHPu1Dwh7xSmEcDLpbwZonMu1oGhcGOnFzYrCc0FXFcN0pqVn5t89GwRBV2\n83T+\r\n=Q396\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCRGA5FzvSBEUUNbe/Wxw6GnRgE7HxonF0e5a648ac1PAIgRg8LK/ca7I5enRwo+VCJXPxrOgAFmyeCmADHirCOdgo="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-7_1563809537111_0.2569625645268334"},"_hasShrinkwrap":false},"1.0.0-8":{"name":"serverless-azure-functions","version":"1.0.0-8","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"844ffb5c93224f34b986460937c9cd2015f5b5ee","readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files\n$ sls offline\n# Starts the function app\n$ npm start\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nThe `npm start` script just runs `func host start`, but we included the `npm` script for ease of use.\n\nTo clean up files generated from the build, you can simply run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-8","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-eYQ4cxGfNCz0HxxfWdbSRhql1dBprV9dlREa6nCuKKi+MPgDCH9JntXALW6Rnq8vXH92i16UoBgyqrZJkay6uQ==","shasum":"0e721b3b9ef7fc3fd6af5162499d00d7283a9a20","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-8.tgz","fileCount":170,"unpackedSize":697797,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdOHyTCRA9TVsSAnZWagAA1f4P/Rwl1El1QSwhBndrZs5v\nLKpCvkIGhBisDEMOo5XmK7ZOqhiqwR042GjSiGJUQcpMPpi+bPta8GL3fUwl\nur3xnUsm0XkjSphbIzRpLCW+yHyKlhfw9JoGoX7t95REvGH0bpKjxknVBKrv\nHKtJpQERvPHMAiIRL1DpVl4psXKrRRmhBUr4lzEJzRd+IlzEEOC5dIUiGSxD\nWYqi43A//K/ByTlt2bQMaFujOv/m9DQd4GS32G/jzFNQl13/3ESXlUpldbjr\nWT0GoXS+YCUoc00u/GhXYHZSVfF1iCv4Zu2k+KEh/sHFAa/2jz/nY2shIw0x\nv+Zon9gecbKhi7Xa2ra1WuSmOjM6MJ79XkjxTcyAehBbmx+8Fj8lau8rfDrn\nbeRIE3VnXihJ9dJmkP9w85fYjjujQ0n1Ox8CMmHUNJ1mOU1F6WGO+zNIvyjE\nCJA2z1lfpZa1MdICNEiPCOkI7uLmUt4jl0JwOupD+YvPr7u50Rj0jOJmTsEK\n7BMXO3VuXYuBj5EwoUhj7Fo7ToAjSlWQG2QOklDOAGVKhTEWKZBZIEVM0qbd\nCriXUysld9ZNk6hDsXof27cRGZIgnUP3NWoTj7c0C9EFmu0+0AInxax3rYNn\nlHF2RzyF9zRdTcLzVjRplKypSButE2tL4m5lEWDM08LQe+37tmpN6mCvCKRd\nAfmi\r\n=q5xs\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCixPQodCf8oEhGkd48bWlqp6kElu521X4KHjwE0Qc9eQIhAM4aTl7Y4qom7wfSKtdhe3rekTCMQEas/QQ65JxOZck/"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-8_1563982994791_0.5236289105444436"},"_hasShrinkwrap":false},"1.0.0-9":{"name":"serverless-azure-functions","version":"1.0.0-9","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"1df392c52dc269f16561793e76663aa2771934a8","readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-9","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-c3O0U6m4Nebpa1yjXJd7pKllw5RP29QfNC2RwhF5k37VU5Snc3TUahHq+DwZIPsflgmB0mTZyuMzEf39jBXDfQ==","shasum":"8975f947e8f92b5e73334e3c47b6aa017e97994f","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-9.tgz","fileCount":170,"unpackedSize":702904,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdOgpDCRA9TVsSAnZWagAAjmsQAIUgRp9ChR0v1DcytBic\noY5rcFmagO03jMtlsBIgwv00/yI5zk5XFGhEKDc84nCsDTnTtAukdcGWxZkc\nm+NsPBl1PnSYZKNdP5IAuyoBqwUxUOGhKPyz70D6xAMrUB71nsE1NS/otIkH\nia4BF+imKN8DA1A8naKo0rOEvL8dwmh4qQorOyoP97/WwK88ozGy2UbfHnZU\numzoouc06HCutcSa0iBXIlvIFBpF8DmhT+BU4wt8FLYR5tJ2taYD/HmyWHod\nfQlRo4W6PW8hD4yTPbhSmJSRwUXsxMn/I4DnUQIEZz73PzV3ozKYh82CF7Pb\nh7W5jie39bcTJxaY9E01cZkaIBNTC+DUXbOJFb8uvVSD5vPXyoihHlt+kCLH\noQJ/kE+FTYWt+qiUzKs4/25fBFLSPZytS5/Kix/GaC94sqbPg+zQtV+KEHQ8\nEbe8/EZxgaxCtnqCGP/o4t8wxUye2coWQGT2AZybSfg1XYc1t2uW0G3jnMAk\nC7viauEGBqWm0qknD7BU4d7erSoJs8BBwigPWrLYP/sxHHzkE0Yvuxjq5sdH\nn7x1iTZqsiw36enZ6D3EL2ADOZj3QyYbmVqU7a7MyePcQaR6BJktfG0iFJr0\nOzedxiZih2P3aWFQccQo63nkjE729h68N8mdRw/hROX44R8aWd/442WEjLm8\n1I4I\r\n=Ksnm\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIF7qKvbVTJquTqtuid4kkSFiMp5WQwAAco26gKc3cmmMAiEAxBLftQbSZVhpmX7YF6FIP4fHHTGEOrM+QMjKShiBWG8="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-9_1564084802243_0.4330609348081609"},"_hasShrinkwrap":false},"1.0.0-10":{"name":"serverless-azure-functions","version":"1.0.0-10","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"c3f08053bc0493434ec384493ac146fa78733a32","readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-10","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-uaTtnWt+CQTrNRi9sjRmd3TQ1uCLQ0c5EUsLY7pAU6R60NMr6Jk7EJabLhT1tfdDbtKGx2D6sIVVr79kAWIuPw==","shasum":"56089538f0aca9c16e88ee6d012053505e3ff15d","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-10.tgz","fileCount":174,"unpackedSize":723600,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdSnJlCRA9TVsSAnZWagAAw5sQAJ+2yti2FegPfkQ0FTR9\ngyrnZN869j6iinGBcF1D3mGbHNldrA3dPHN/+LOuhDH0l9MO55wGRDZhqnYU\npkuenqaNriksKf/czu6XKQy67XBm781bIVfrWr85C0KMGE8QyzeFfTxxZsaZ\nMplGtsnzgB49n2w21TEJCYYcxahXg0WIsW1cKPI409O0hcNXHsnUVIPvUyq8\nNVxKGi9uM+jmo15qFrP4+TA37OnfyRZMb4sZ70pOqEnPYsjokzXNpvXWCQjY\nSEmGjXmxYRmSkjqFUziWeMpaNg8hNhUE279hcrGxgY4xCZGHpwH7iy3J+zar\nWlYf/d2d3u94IbcwA4DdambP0p31nI7b0WngBbxcgvoB66afxiWgcx0HW2sO\nt2WsDKhrBs37+ur0iDv/cr3RAzpfbWr+aAd9WPAUt366XCVGWvYVxnrOnPOr\ngBnErcYiTaG1YnJ4j8ssc504FcmJMIJR5lZLk9P8GTWa5U+wdMXEpqHIuqt2\nOBgT+VRDfVHzoW3bPF06RbOniHNNHsR5TDWwBmxD47OAMP70c/uL8PL1pm/h\ncr9qElaD+6kFS/tH9kwyLsujBYcInv5Kz+t3BxtNqD8nB8/ax6b5QSwvGZy/\nWDGhyXRIgT/41KDRMI7q5K8O6KTKk6duipmFaE/0KGpGU4qP8lA1BS6z9Vrc\ncP2m\r\n=kciv\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIB3ZO0JP9v4Fvc9gSfujwDiaxGMwN6s6gr4Y5DWLHWUbAiEA4SyVBwlTTTGdji6XAJN8V1r+vMKk+0tpTpl4aKxAuHU="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-10_1565160037252_0.6835600965254847"},"_hasShrinkwrap":false},"1.0.0-11":{"name":"serverless-azure-functions","version":"1.0.0-11","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","coveralls":"^3.0.3","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"962c619767870ce6a76cbf7a8cdacf15f7d0e658","readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","_id":"serverless-azure-functions@1.0.0-11","_npmVersion":"6.4.1","_nodeVersion":"8.16.0","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-YaZcbKzbn5hNsBsqfsDkUJHgv7msGsZFdXWwDVT1rc25vCH1FUeBFy/burccoadvIj/oiMLWw4kPWw50SC2x7w==","shasum":"5dadf8e1302848cc8adb008ea7fcfccb83b7c1fc","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-11.tgz","fileCount":178,"unpackedSize":749900,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdTK13CRA9TVsSAnZWagAABJcP+gJ0BF9qNi0H29S38mIX\nmWQBbtiJne1t46ziXnDD6ergEswmrMTe/twMyTHAZfQCgwsyl9rOHALe0skk\nXwe1UDRwfwh7HfI35SS52Nd0jBopY4Pi09MoxHK1PWKnsKwRxwgQLfoehxMK\nHPAIBNM6ht11UxwYGhDRzC975hvMzQq/MrSh5JphQicRdX1z0G4kThC8om7N\nkKyhFhb1Mh0YHxNdPjrs4A/bQZYdE04JWOtE4ZkQMO16jC/Qs9c2Mql8KmYt\nTtLdn4wZemXGSRxAjNq5l1JeJZRPx888D2EfhkLghuMOfaycNF3xsX6N1s3o\nzfiIQYApl5+j3JZZzyJodUhHaMY3yVoYyucokrwS7YgzsrzgE9s3hYNqlyOH\nuOZKgMNFBUrSjJQPqQIsrXvAcARyR6iN/aYeU3kIr/Bz4f+NAzlBYf1Q1UTa\nSoRJf97k5yBMeDQ5a+IyJ/2T53eCV/gVrdqHvDOGGuCzOqYNQA9Rank/YFCy\nyzecUV0hCQSnjgqnmwXXtci1w3Im0I9WrefHIkJ4hmJ79uwNd3qWgC2Ky9FG\nMgasDAAPNnYiBYjAxF6cIRmedDd/atf3hAhSMT+Jyh3jlJu1UTsGMOBi2Tu1\nQWyC2U/C26QudURZNy9OzfS6mZFgTDAOvezZSGP1PNkjAE4vSHZh/qSSdDzS\nLNra\r\n=LIcu\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBTeklLdshDD/9IgwiaTT5XZL3Es/sSyV5Bxk2oGeEi4AiEAmU7hC2ae1BynDDuxqv5UsMCI5pAg78fnUoxWqIJ+57Y="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-11_1565306231185_0.6827322290148601"},"_hasShrinkwrap":false},"1.0.0-17":{"name":"serverless-azure-functions","version":"1.0.0-17","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"75c8815a9d217dc9d0b5881dcfeea15c4a1acdd6","_id":"serverless-azure-functions@1.0.0-17","_npmVersion":"6.4.1","_nodeVersion":"10.14.1","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-ZkWJscu9hdtug1mUKydfZEmKp2D2HeQ/Hn/d8XksQADasD6WSgYSzdImFWf/c+w795Pd6RKBqAvEWlX8M8TfnQ==","shasum":"9003dc0a57bf5eaf995a2bfdf2e860afbd306733","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-17.tgz","fileCount":107,"unpackedSize":441703,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdZsEJCRA9TVsSAnZWagAA5b8QAIENgvFfbHuop0Z105Cv\no+W3dGWjr+Aw8Rkr0A4s3xRxvQ+b6ibQ31ji2YAsfhUm9h3zIaEILfRRCIxK\n3tnlxAxEmtmsp/3FERwfxh6BZqUUBGHh4vNViaPVr1wWJDZc7V6r3DWVMkPz\n6+u67c0XO5jPk+4iQpHVl60dy2NnyJFPY/ANAgeUqXjHp6UUZ5oPcH8qcgIC\n/8bT6cZtGgMRo+iDW4UutuemcK7hzhcKlmxvWcJU6rmTrWfvKqYKJj7emdyt\naXVCHwZqeawq+MCCvRPaz8UfyXsqXKFebPXFTkuMs+CzP7S70x0FnB1XJiiM\nzmyHzajisWHfA4cudpoReYLU6W9BEiqpjIlgtHn1ozsOUA/lkYzEWQlYMWkW\nDLWn2D5mHM6WrkV7XkfZb9SWWZiokBdrm02+Ct0AThPBZjwRZInOVPmqiUQX\n6QVJwH+oX4x0OW9nzJt1kfG0XOF73GlygjM9f7ASPegv5qIRU1/2FlPMbIPZ\nCMNCloxUyzAJGPwYAyzHLmtYdYnS9EscLZDw389TwMUrbrFRH1jzWDPhP9zv\noT3ZnlbIEwZ11mziZlASwbTfrSHZbkEHAWJfU3ZPGrk3hpdK2P9SBO973L3h\ndYMjFr+fLuEMWAIt39OtNuF5U5gIP/dRU9Rq284s3Yc3nbHCmlRknS/Ppfg9\nqb+2\r\n=wqMq\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFnV0AkbHPjVurj3n8eDlYACh+5NVCLNTA8XeHV4vOjyAiEAyzSm3yPUHC2PJwu8/xlhK8e3HTWHFXJXTTymSNMyJ3Q="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-17_1567015176418_0.4816136485331084"},"_hasShrinkwrap":false},"1.0.0-16":{"name":"serverless-azure-functions","version":"1.0.0-16","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"297d4cd8aafe8c97b366dd0c1046054f59696226","_id":"serverless-azure-functions@1.0.0-16","_npmVersion":"6.4.1","_nodeVersion":"10.14.1","_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"dist":{"integrity":"sha512-CSbVq7q6UQEuxiLa4PR8wuKLXNvRRSVbXgXSFPdeEBhPmEwMzfQivKiF1EYhSc8g6EjAbhx7vNFG2btqnWaMzg==","shasum":"9c295b2fbe2ad4d49d6d64e6e42848ef1a8ba139","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-16.tgz","fileCount":107,"unpackedSize":441703,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdZsGjCRA9TVsSAnZWagAAuU0QAJGEe+hVtu8uQtCzoq9k\nxXXEratVCrxTKLCHdFSGR9GSeA6yZhlrpyZdd/bxmhy6Tt7BZBihk1mwSBWX\nH9iJKkrEza4M5zpqflT/yAG1Tr5tdKYeKrykp+PXLNjJMFQxvxltkXDXLtSo\nyIp5UniHkva/tNutcBDPTbhpDqV0bnhzEOrvMArw6BFhdv1kZT6swVWTiczr\nK7xkycZbs5zJTlmfzq6I8OnbaWvOmjwePbI5u7zUDNKJ+mASu70O5PbyBtCf\n51XkLoab07ZRSk2ifGGVeFJ9Uo6Qz5Ura3IJFW81niSpPsoV3sgHbcndkx0w\n9Ei3toFeM8/0b5/6zVbuWW3P2eSDoPjORkrzseDURlOo15ucz+/wAlVuFGqW\nVo5YlEmPsmijZkPu6xqAx58cNegwiysS2+fHVhpZY/uyQJF/hvZxvp9Psd6J\nmvgQqNlSyBl0OPpfkGcNdIEzs9zkE3Wi8wvgXdDDv9LbcQHbj4dypua8ToJ1\nzDcSD8YV7/WN11YlTHYGcHj05mn12IqeKglVbqpLCXgSzedJpbgsiZlD6e+k\nIfFREO05bCBJkTJ16wiAeIytaHGc8J3WYTqtPZNM26Nrtahge4+ia8q+H01j\nR7Wkrf8b0Uq8ktUDhz/PoRidad9dLKq5OWTA4PdJ4dXRuAkCg0YePUd6s6Ko\n0ynC\r\n=KSWk\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCImxwBlQhwvpPBgK1nUVmj0vzejoYHuQ+G/8RtbmPpWQIhANA7aSdWKAjol8ikQ1uPqMbBY3eR/c1/Hp2EXbO7W4lb"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-16_1567015330954_0.9428679094054304"},"_hasShrinkwrap":false},"1.0.0-18":{"name":"serverless-azure-functions","version":"1.0.0-18","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"5815a2fa7e58284e6d35e5723abcf45aa85a8173","_id":"serverless-azure-functions@1.0.0-18","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-YVyYKYzGG3P0+gOunPKU29diI+rzyKwbsnw1PFsLFov7zR+XkArAMuvbqB8QJ7Sjt/ti18KGd4Q2PyWQ+aZ2JA==","shasum":"3a0507e4e3a4276eed0f9ce48b10e75994c39303","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-18.tgz","fileCount":107,"unpackedSize":441703,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdZsx/CRA9TVsSAnZWagAA7OcP/RUzHpDN4vJFKoJqSJd4\n03O8amBNTTlBR1ehpmgKS6SWvevLmFRZD5eC/lDFu1xVeba8UFjx58nK8tYI\no+B7wp/9vV5IimkRPXIP9Un0S3qOaLP/qkZW0/CtA/BZNkVmfT9zdcznMjQQ\nMVI0S3XLieZZCehM82qtK3gwP34hrn5UkJpFytlrazYVFo0dXn+4kcEAq8tR\nJ+LCuxgrVy3qHZScWmtWPsDSToLRoeV5X5ScqbOkGOAvDjAg066vIvjyazUR\nHflgl9CCBPs9HV7dPoqrRN3vj3ubmdE0EGlmaeQAMlc9Nw3622wgiLbCqZBF\nJuXaF3FeRgAyyTSIByUnycXQxwA+pfaO6mgL0w1YZX0Nei3P7nlDRmvePaPp\nX9IKczzeB0vTsXW2zUdUd9fWwn/u+O3wqnrlygSo+5hDGPAzGnaJrOk19GS0\ni0pwfQMDFvvFvvnzoawoLE6KvIHxK8y8Y8wLtcpsMRKBPmo5K/oxTWRSw58m\n4Q75XYKc6x/rLvHaCJKLeIV4HliLVBJEJrMoPIeKrCWu3W+CDCjSzkltuGkb\nYnRREh8Nyw3e9w4vBaB/p+siGd3GBBLl0QJZSUF09Q4f3EFkc5evphNVROzK\nGHaTtjwBDYQBme/YVhjTLBsmD71GnLXcKdY0f27cpS59WUOQdRRaELeOfent\nKRJM\r\n=sRhn\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD5xj5NJ5sCif4gtXUI0OuZKDsWprtLbfvE1RxuBQ5rcQIgGq+2M0pGGm9RL/6eUDrXUPbPEQqm5Yis8efKmjKFYPI="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-18_1567018110948_0.9547447430169935"},"_hasShrinkwrap":false},"1.0.0-19":{"name":"serverless-azure-functions","version":"1.0.0-19","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"519c19e8b8fd7ab64fd05dd09fcc5a5c8d869235","_id":"serverless-azure-functions@1.0.0-19","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-lTITa39dZeGT3qQBoc7+fR/cbrl4GTjPEqGCEQF/1E/GjsqDduIXxSFczpU/6BPiNf6c1bnlU2FRmCDSM2llEQ==","shasum":"3211f885f9751dfcaf19eeb706de459ed118b55d","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-19.tgz","fileCount":107,"unpackedSize":440593,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdZvnHCRA9TVsSAnZWagAAhuAP/0EetT8HxFXjZxD4XpDg\nBiZIFcX2Du1osiZX0Gqyx68Zd9ErwDEEn1NoP3FdU70ZBCHKMYu32Vqk/Wbk\nFmPgvONyxwl3WVPTiPFMcFLfRg9lMMZUQWPb2fVU1eN6nTfezsGptjzEpao4\nHrPF+1AhTOaSwNruSq1PPB6Lh3xZUTi+BbVx+jRG3UjXdVlKzK+R704nFsGE\nyQhcXAuzmrl5iuKlx8AlegriwECOdnjMj7+U3u8cLshxtWAKQa61XA7g5s77\nwSYlr87Rwuv0eiDJT7BRWc9G2XAwPlJHq0xDq4otYTl0CtB9Uu36WM5yTlwp\n2PL5eHWkeFWYFzmQsJXhv5+FXMm3kDqzO+goI0HsAT8zIwgzp9tvowVj2qpv\niuVGnw/fqv59CvdAhc+on/CjXW5OMzKa9ORXJ4BwFWqSdp4EewEU5xDacpPp\nPyDyZyAEyQMqX/jk21qvcNSXRX8XkpSWrVh2p8b1PSigU09gMRtzwPQgzJHS\ndbBNkRy+8iN6zjpBXPD8I94LgmKIjHnudiP5nvfSc7jTA01eih3Rr+4X5Bvx\ncQEDoTzdM13ep7GoEBrkIG9yz/K0eonmuLMGs7SxJ6YR2eF/hqrwIUL0I5YM\nj0gTP2g9FHv9XKnDo2tUHlQVrZzQ6i/gNy8bYsuYfLGmeUYc8Zj3kWO5CFXc\n+n1m\r\n=qAoX\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDGq27GZRFKs0bRWw2PIZCQWunpIDGIeWPRXeHhyer4aAIgUloQwVtOdnD+be7xAIomXlp69bp3Dpa9qnOD6uHt7kU="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-19_1567029703128_0.3980505176494398"},"_hasShrinkwrap":false},"1.0.0-20":{"name":"serverless-azure-functions","version":"1.0.0-20","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"aa8fb2dcc01b608cdcc6c949e01cf39f931cfae7","_id":"serverless-azure-functions@1.0.0-20","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-tpWhfGKgj9Hr2ByKfd3W9yXZg3nutvCpoHRV64VJKYP0DmOsX72aVKX/Po2khOKWZM1cy11//05D8yJQXO8P9g==","shasum":"d5153831c283aa154f37870917fb729370a68b92","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-20.tgz","fileCount":107,"unpackedSize":440540,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdZvrjCRA9TVsSAnZWagAAJ+EQAIw/66qigENp3i0rHEkw\nnm52gYil1Q3Q6n3If2E7BF7+0YbaAWo//1iDTPXhV7gHyfkNa86YlAwhGSUF\nquoFwq3lgLCxJMLDCOzfF8N2x4qtOdm7jwcXMe9zWcWE3JutisXYX/qM0/k/\nfcdXnuUAKxh4Ieg1s/sgW+7ENb2c6gBfd+UskR6qXg5s52GvgpNIW7B7J1Z+\nfKP/0kmO+YOs9TmK6pgL7bxBTIdWh77jKEWZyOSpGe4V0DHjf+gLEHUw6hNe\nhIQEXusDrnMO9yKUYND4lcPxx9c7ZnVJ7QC/HItQsEMxjP/R1hGKONUsNOPD\nxySx9y7RXunr4yuEUxOljePZHt/CPq59Oh9xdJ7kZDP5JCJ44gSPNwPJ0Svd\nqyk0NncXVjDFCmxsu5jxoCJ0UV4ZVrMpiqDvhCIPSEgfKKu5s21iASgMJXUk\nJw4AeiqWK5lKTKELRpI1MDkXrQvGDFeESNE8VklTh05y8o4+qLswu158t1C6\ncXXUE0vL/+GhoBOo+90is7XlmhjbBAsH3+GL7c7DSnoMQ1tWUTajXPdD+oiB\n33p2DqzqbxufcmGVxZ+jIRP6b2sib9pCDuOfBon0zgap52J+kJldhMq2/3Hi\n3pujOpSNVohXxCDBuuTFkHn2YM+Df6IW3Kyk0kzmLCWgHPweRMONivC96vLc\nJcsq\r\n=HNY9\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFEokACiqjbCLB9fbXmprtFod4w0OstSHbEn1DOBA4S8AiEA6hZ6PQ+6ezjYGqHHXtPEIzHx6CTtbGSwSKVEFEYK52E="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-20_1567029986912_0.1666385586462371"},"_hasShrinkwrap":false},"1.0.0-21":{"name":"serverless-azure-functions","version":"1.0.0-21","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"b9b6765b3212a657460c23dd499152385984c599","_id":"serverless-azure-functions@1.0.0-21","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-K+LlKAFtGVgxMIPco7gu9ZYSWcAWQxUMLrzQb3oACMdk/k+icRaV3Jd/9Wncw7PG61lX+B+wLnlqs+H/QD6Tig==","shasum":"de215bd7e05429b4ff24cfab2ce89db2e0e7b2cc","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-21.tgz","fileCount":107,"unpackedSize":440995,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdZ9yzCRA9TVsSAnZWagAAK8cP/0Jtoubbx7AcJ5zjbEkD\nwArc03aDXMPfDrk74Lz76djNrkhEx5ZmNA/MkJ5VPPOtLWfC6fruZRKvNqfu\nGqnmfl6RAOgGCMnspFM5AnJ7QIYs7iux3YuG3wa/IiOtSKeveMtXLUBr252B\nfhzfcjF/76TGZj8GpTPv47JEE4C2P+c6d9jBvPiKzF56rdtd/kBfSWQqqA45\nGpcPibPGYxu3wJvA4BUz9d5q6k3xMMqYzHYcNv49uV7aRXy/Ef7mS1iPJlqo\nL04xPG8LaxD4zMZSGD8TL3RifR8dRFzlBPvhaf8WKY4wGjESg1qgE19oBW/w\nbT6VBX0g0FBtLL9NJEBtos3j8p9Xiaa1B58wTxowtDZheTlS4CVE2NIGzggR\nAESsmwt4tqrgAnZwTmAuXFRkS7tBTWvmr+n37M8Vl38Q5K8OK5Rf60bTugXK\ntBIxaAGfI5dEwUK0nMS1Xf0MUyBYeTaKohOPxfyWDtMw9b7x9kWmm0/ghEMe\nrvIfUVKfQbRjQC49wICd1qBhGMFxrw5p7nsphCLG0wWCuNKYysDxfk1nEfdW\nIQ9qvPbeHTSVYuPlUhef11rtY9bFhKv4rkHh5ShYi3SEwBhwyx4wOWWaIKtF\nFg0r4PDNo4PWfUdDKUSoStg5IfrUNixkQY/ah0m+JRksKE7p/fg0Ic6s74YQ\nWGno\r\n=gVeA\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIA0d4TAS8vvWvaT2xS2jz2VfHyjdJB67IY4SCanqrYOqAiA9g9x//je18gmMcYrMoq2JBoYSTpMongUAogUHPiyh3g=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-21_1567087794384_0.6718100861092366"},"_hasShrinkwrap":false},"1.0.0-22":{"name":"serverless-azure-functions","version":"1.0.0-22","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.6.3","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"df63949d6bf2a77a4021aaf41aecc2a1ade26bdf","_id":"serverless-azure-functions@1.0.0-22","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-JRWp6mrNac1aLZle0t6gadXRs3mb/DD9jsxgaUkYqy4AZ4m0yylCO74TNP1eG67ILJ9ndsntumMBwfvj/JJLXA==","shasum":"c3e0ac69d03067cc268985ca91a68c0563a4a9eb","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-22.tgz","fileCount":107,"unpackedSize":441992,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdaCoyCRA9TVsSAnZWagAAjrYP/A3nvBLU5mptKTMeUDfC\nreK9ZOO3fDOMXINC56M2WszSpeWZoDgYLbouSHB7sfD9j5+vv3gsLgTDec5f\n/BK5RrdHjfPxOjma4LjBCr7+Rd80Civ8plHp5ZQSAf28ORmlzFWPfnggZa8k\nwQ0xgwRPnHJoGP5oiWIT0jlPrAS3FBCTL29UmISLbDv+UWyEKyE9mX4ToQNC\nBvruYywVb11Ld7cdpXiIraq6kYR/TDzR/ndFd4uEPcDclgurnz9vQ1YQ9QwB\n9NiP5q3zcnee/gH4+MsZxmV75sFE4vhJQyTj/lQy80tzg9JOwh77jNfZT0bJ\ntUrLxPNgoyPa7Un3WKNQgLoyLGAeHut8E5xufxqUoX1CTAfuOuGjmZbnEdHG\nRFkOJ0lKcmcK+o/ehRyPz5+Ior0j4ENO1hCHkeoznDn3Xx+syrBgEQ8A/f5m\nOykqkw0D+1ekoYXkm01/qJMyRbOACu+p7BLnT3GfTbiqVPr11wGzu5bzjx/W\nzgpKxe4zBt6iBzQbqhWsdVpIM8rCVNSc2V63v163HwhCOpKZzki02Ps4lcKt\neunYTm4kZwwCd7LaOB8cDEMPguPOZoQZDNf7H4mnZDj+rrHqpeQ2TnQ6YuT3\nX3/HS6jCytwnUapnhGYD1t+L/TfcGVWyZKCfQ05l8+TJlAP2cnBndR77L0Kr\naZqr\r\n=hxuL\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC8s2k0VEeqvTtPXsVfJ+NZbIcjwYOcuLRl+F8npNOpPwIgGWkFXe0/0bOZx+8IELgQPU9Jca8OL8eSWN9q8MTjNJc="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-22_1567107633992_0.778315870097074"},"_hasShrinkwrap":false},"1.0.0-25":{"name":"serverless-azure-functions","version":"1.0.0-25","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"bb2c6616e556d8098f7b9b1247bbbf137030c84b","_id":"serverless-azure-functions@1.0.0-25","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-h0plbA+GiDP4PORqG6VIb713hMzrLtuz3QUYITkg4GBoaKbqYDfAqcOi9Yml2+l0/FHrwSeKjJa/TK4J1R2B4w==","shasum":"cad4b03ac59528d49417008998836ad3c0060fcd","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-25.tgz","fileCount":105,"unpackedSize":432190,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdaFRkCRA9TVsSAnZWagAAIN8P/2Gr37EQbx3oM0A7p7hw\nahB2HJ1cu72Cz6yrM97QV0n1yTbxRim6k40gaFxeP0jRlWkpthPFKORbrw3a\ng/4CUGNoFUos35q49JHJHOlLlXML/dfPF2zGyXMD8nzHMjpf6RqjobRkBkJz\nVynoHS7e1hRCJVUYN5ivm0JM5bNJtB/TJG1Ykes0kfVMmfbmGLlQNzaqCBcV\n20fPYOEdk2r8mZbe+zcO8n9n2EX/Yym3/XiEbP89XaIjXR9sOSX55JucNMT9\nL0bcdbyJl1g79KckdeTdHOO8FCm2psL8JUC/m0tMdYl1o8LKZqDRTas8OByU\ndHvyLhNa8+5cfNe+jTprLeLM5mzn14WoCOD46u6kwWMEWa1s2YoyowoqMzjk\nTdhm07idvae/M/P7O5cij5g1PClvCJElcYSvmLFuBle5H0vwHdVzw+vGOe3H\nYzl9wvTklxxtJbVpyuVABi2/BI2rov6RFiBTJ5/a6VA55ul0rZ18bQLH7TMv\nzWpxRAzgKWJ4qBAHg5kda+BQe2V+dLMHQvCZ8bpkVNmSSh2ECHWdEUVmhCFN\nFlPZpCA1ftzJM/weFFvbHy4NmL3CkSxKqwMNY60M5RKMyFs8rIn56uqpCMZj\nf/GYEanNEwtvH4eqOfnrze3InfNGjh25CmhUq/6smdu64eUThCpIBa59ksgz\n/Yri\r\n=rs2M\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIG4K9wGs5MJP6xrEb6TzZXnTsb+rQeJGfJFYRgpcYbEfAiEAt6gNq8WJdzHpmYnl9gwOsPWa97ATykrUERRNqZXARbE="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-25_1567118435183_0.030802499216034063"},"_hasShrinkwrap":false},"1.0.0-26":{"name":"serverless-azure-functions","version":"1.0.0-26","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"7d320b9f83aadae62cf29ed9b38e9cba236d06ce","_id":"serverless-azure-functions@1.0.0-26","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-w9bAM+aNXMM3MhiDjtkn3lOKwODhPhH9LQ5jwq5d8Qzzyn2snelH0ifbysgR5fzZU5zUyEuLa2aA7xFnSuGY4w==","shasum":"51c68be888602faa2d97a0f6bb988793da410d55","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-26.tgz","fileCount":105,"unpackedSize":432193,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdaUkbCRA9TVsSAnZWagAAiSoP/AyO6x+NQ4H5W1j1PuoO\nzLlFBnkBxmYGtL/B7EMI3QbIjcpaIytY88XzkCbwVP1qNbHeLlDxkM4d1RO7\nnxw4VSFIefYi7dmkn1502oKoz54jrADqB7yYLmMsr8tH5359VV3CI2v35XQ3\nzirPEQ3XUQa3jzPoGMWwNHcypZ9Px9EvZFr0WdmwYCnb3ZlJkVuddgEwjxFU\nHUHqeHnJ0NYNJmVLq++OiRayNBUbYHetGNqQiXQNYFTQL3+hVOk2HRoc3N7q\n1KOL8BSwqoEsZEEacT/Vcikmvg8lofj093yNnB0z6UEVGA0ZD/7Yzh376sGN\nS4Qjeutm2WRrtmg//GNxDKzxnjAuwitxwEMdLv3hCwzjUpSZAPW/WzWi2hji\nVXdaFkDEH9EhYR81gyfpRXmLRSpLe2lmmuCo6E4A5p+1KnrH9a0U9JnSjEwo\nD25bGdJXgRtEWtCEwOSv5qOZDPVtg83V1lPMvZrBYa/H3Fic3mE0Ck00CwUD\nBAAR3yVB7P2gy3h/bBiDIXMUlTb9UkRhz30uZ2OaBKMDCpuP/AVtoenDkmuZ\nXT3KUKivXI/3+219losyPwNB6/dtFJUB9apbMaYwIKQlrFWMokDfv0sY7AOq\nDnwcmeQH8U7m4O7/Xu5piTgiVm4Nt74qVK02z2N3ETBiJmlb9GvEgbeGS0lY\nYhTv\r\n=6PGW\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGRGXvfomPaFZXA0okLXtGQOEjK6b4a/ATzfxWRagJK4AiAhCjKN6o3gyMbC75OoPIdCVagOPIIB4A//KoV3kK7OLg=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-26_1567181082572_0.9566515653429539"},"_hasShrinkwrap":false},"1.0.0-27":{"name":"serverless-azure-functions","version":"1.0.0-27","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"469214d5fb241109e5f730eda38bdf310d2b9e47","_id":"serverless-azure-functions@1.0.0-27","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-TOPYQW9AImhrmemCkSNZedIcEvKxD8mLvZqmWWXp+WLqqNwDjnV8tWziZM1GaflTENXZCqobhNWNGvpAsQlx8Q==","shasum":"2c23633c365144cacc9f47417f0f9fb3084d53d6","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-27.tgz","fileCount":105,"unpackedSize":432193,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdaUq3CRA9TVsSAnZWagAAd08P/0qF3M18dBtwsAEhP4XL\nawevXUl6oGsVsAUZsBl/uLQ9YN4Lx3hIvuKB9FEwVxBhjJpwEOyMWmnixqHA\nJzFDRSxwbV7Aq9nXo+Y6rvvFEWxZeiJTiiwjm7fxM4xnrlO16Hd+jFTzhRjH\nNkOhWfEyix+y9aQC4WbmcGa6LE/qy02t2nuZsi3Th/BaeRTeHYHaenmCtJhK\nriIkgos4qOzeHeo7DO2tIT1spODUbLZCEU/ThVfcu4pSpqtGcWnuGarm+S9R\nGGLKu9ZRP8sx41mMO5S2Xf2B84k5cY/TK+dpNzeogLiX/TeUANf1Ng3Z1o2M\ndJgfeHT/5pV7sTmO+TPh+SKLZbG6/A5ik2zKk2pHuYvWf0R5Z5A30B3fLKJQ\nBd8cX516tkYhzq6qw5Gpuc8W2M1DRQ0VA07f7m2rsnN8zNwhVIPYkKDodkl8\nCQU5F+O5GUagjH7TIcS5TauM+ikTLZjkQOu8QpqU00I0nxa98FSAacH4+QZh\n+fsCg0LhGxePsjm9s9BeAABcbMuIETSWMZD1roMuejCudXU60FQ8IpqN6Zs+\nQ3j5wtGbDAl5foqPwf2f/KJwXzZ3WMzZs817sf3Rw89sdVG4ftknPTg2yzmh\nAF5nDBH1fh8e/uICNvBLcaN5ub7+gfSqi55qZhWjDlesOm9RkglvHY7gkzLg\n/Jxc\r\n=0xsa\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCxstBZaVb2OrsguIK0hY5r2bdBGz4hJvBu6TdcGXy6awIhALIPhCVmnyWE5B3r3Ha8Nxzb+ZNkpT07ngAUF/qlAQwn"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-27_1567181494770_0.8036236148714535"},"_hasShrinkwrap":false},"1.0.0-28":{"name":"serverless-azure-functions","version":"1.0.0-28","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"8f35c91ad67c9efdf503f09f83bf72dffe924b43","_id":"serverless-azure-functions@1.0.0-28","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-UwiFWzlnIIOIcg0ZV2jKPxV19Z3nSOB+PduR+4Tf7sqCpspU7lF5IpRVz88PycFBmmUaVhYmCdezowZr68Fppw==","shasum":"cf1dc3ed10de18ec8ad87dd905408cbad20c6a89","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-28.tgz","fileCount":105,"unpackedSize":432906,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdaW3CCRA9TVsSAnZWagAANqoP/A45eHkvxLBh9w1jCemn\noTnTzTR+88en3BodVZ6W+W19IUTBr1DW+/KqEenDQ2MG+TEtpbeGfvHKTxIR\n9otRR/8JrJFWQjIkBVooiNKqS1Vm3En2gDdGAgu/LSBCQsKN0QTGrtRyVRRq\nXaDmGg5BcfTYyAV8Fl11/sVs1J1iuGqyAW2yi8jnm+yEa8QvEUckLc7HydYD\nQ43IuZSkO63eZm29d+5TaoP1BpNL2B0Ai8xbqAWFzR5//NAUGifZobyIrp9d\nD0xuqgtBqbohi0chYQKzSKeqkkyC6NRP+q1TTOg5ZeQj/lAhUpHOx8FkQdQk\nGp5V4EV7rX/PrMjpiX5uTUwYev+ByvA6SBFMQTN2KG7D8FypPT3RSRXCqWXH\nsBN9tsbCNhh3yXLxHVAHlHrNVmKOAy/B96H3MFltkPL/68jtC2IglmAWqm2h\nBDoQZ9CzPkF29m3/EeNndpXeImaOe//VvQZ1gUAjDGxJt2v2Zd6dyQE7+ih2\naH3xtALQpkJCsDrOU47EWFgMpQVtUowq7DU5tJUtsgSgu7+p9uZWgAi7ClgC\no/e/WkeAe8yhffDYrnegczLgfxPJNFfKBtY9/FE26p3XGaRIw6vAbyX6ovke\n5QDnXQiYhkMjVYhjWlJMdX20A9gjvbvaAgHRfIi5dWEA3TONKcVJosyrh5+T\nWC6P\r\n=WvKG\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDd1YhDlwwAbnfauce5U7MIRTf6iVn5Y5lEfJICHklBWwIhAN51k82ZYuj2Xmx+K0KaJvBp2Su+vq4hevCeZqwX2TtD"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-28_1567190465683_0.6731747698178598"},"_hasShrinkwrap":false},"1.0.0-29":{"name":"serverless-azure-functions","version":"1.0.0-29","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"7ffbb8b9971b991d61426fc291d3b35269d8e46e","_id":"serverless-azure-functions@1.0.0-29","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-Y0Sk9DGqENSd6JpyC3hBIQBPNqTeAMM3JeWS9G7Fp2vlWDEJOpLjXahh4Pb00OSLr21fC5S2pZCQhbbLwVYlNw==","shasum":"657180b7dd772530232571008cdc92835229c7e1","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-29.tgz","fileCount":105,"unpackedSize":433427,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdaY+KCRA9TVsSAnZWagAAZr0QAIIRC6zdP+LZZhK4h0yv\nAnyBjbQl4Cw2Ggh72SC5bQIKQ6bIQ3JNeOht2dMgxrTbKVsNB7xxd2WL1fr3\nNRtVj38ynV/N0IJViSS/8Z+onJhWg/NGtJ3hu7nPrmZ42r0eEFzs8jx/hYpK\n1I2DC8ilNd0ccXu3aiqC970YH4MKvx3TGwD6gJ4JFZeDqbGvWKBY8iPsWojg\nF9I0X7CtsYgPJfimp67Dq2qqGrIQR+AST9HVXT7mVmnlWussvRV4fOGgM74o\nOmghe7Hc1UeJUwjyVbx5sDNYQbDvtilmZxzRzZUvmICeP1LI6+AQmj470Af3\n4UqsF7yLsaDLkTwf59tRRYMCLmx5cxt06qa+mZAJrrGzh/+OBqRx/UW51CWK\nrDpc93Ktxe7tB+yKDsnS7xGXw5TkrFRsdaaBOb1U5+dEJQMGN5cKws7rCbRg\nnmlC2zYImEFbhMvdB9lmdKlliVnzxtpkHGyctbhVhe06GrNJsSmfDaGMgTqf\n1K+58i9zEaDB6aIfU3SzNGDhsmBZenkN9demyJehPHXTI7BtvbCKgRfmDkAb\n85rzQasE5H78djc4XpoB/uviZNK1NFG+jBmv3NGBqFeFKpxFHmhU11kd7FU1\nQc9lxKrRtP6bNE+o2Misqax8JodD6cJY2spcj1/B0+7sI7M4+qBMOLuLVs5z\nlyC0\r\n=HDkQ\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIAzddTXX6zeEpVa59i0LVt9f8C9BohHRTPEvo+/8apRVAiEA3ZgdcUb1gV1BL+v7EIxphsVAVoIf63YKUFW6u+a4Ogk="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-29_1567199114253_0.8952830041144768"},"_hasShrinkwrap":false},"1.0.0-30":{"name":"serverless-azure-functions","version":"1.0.0-30","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"07bee53dc9ec57e7750bc951979c3565264e8961","_id":"serverless-azure-functions@1.0.0-30","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-gaT+owIDc2OfrlujigAvlvQFdDo4hkOljgCiaNPLkSAvr9Hm/QTm7QXofetssrH1MlFUNXPi1Yi463WhVKfEhg==","shasum":"5c89c402f28e7365983b3fac0c304abb9648af8b","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-30.tgz","fileCount":105,"unpackedSize":434462,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdaaFsCRA9TVsSAnZWagAAbsgQAIeKUNvmBWYfqZI2PsUT\naIDIc4VB+6RQyVevtRKnroWk2QVpJHqeWRmvaEJQzPmUJCHgpBEBpc44H1h8\noayH7YVbF4nWMYJ0pl2iMv23sbKNcZfzqoo58kxzONjxuy7d0dvSPGEg3PvG\nOlxe98k3IR1kYZPCbTRTmZupLw4vDK6ejivBXpBKjKMoIddWLzy/ljbqh8qj\nUAXUVRwte1KkUgdkQIfgRmztq9rcyCQUM0v+FvUBDlytavTFVWgKQhMuN5zI\nmzSNJ26+Czw8Bti8LaiHhBPhh1L8eyVHPyBf9r+1AR0CjB7mpBvbj8vKps4u\nwUuMNJ0H1ybFytM5lR9hxPGit4v7VyzgGsCeUR79eQWPMNBQAzRGKn0dm9O4\nvQZJozAn+/r3e9MVFU+j3meXs0ei0Tk49A2TqqhjOntinLN7firO5bdlpKTN\nQx9Cr+GKfZX1MXVh68sSLBpLTHQ9QW31v5s/9HxoEooLB+idni739r+5Zmc1\niQDtyvVfTFkPyQbOatHFOgJBpwxjsGbXA08vnJ2Z2W4swsSFb3HH0CY0FzKN\nqS3HV9e5zqE1PLyaA0KlpGHO7L+YRzTWRryPnl0YY6IjA+qQI8KB8213i5sh\nx512EaCN4TtmXnThTenGAQzykQ7o1503E9WKM52eq9rCZiNTtYIioZDKJ0M+\n358d\r\n=UkgG\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCfEMTClVrabt8OG1hwWAEnnQY4Je8fYzsly4uXiB9nRQIgG5+2tAkFNk3HmE6qjoiSatedEHeyaLKgsJT0dGiMuUE="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-30_1567203692161_0.06891025295673203"},"_hasShrinkwrap":false},"1.0.0-31":{"name":"serverless-azure-functions","version":"1.0.0-31","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"8d3931de03a03eee88f08f8e66551bc3d02bcad2","_id":"serverless-azure-functions@1.0.0-31","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-JjctjtAUG+I9Z4/IitZ7UHJmwyTEefroNcS9EUcTP9bTh5eAy3IT4v1vWCqLskQMsOHA0crnlux+FIesiL9FMg==","shasum":"44a52d42d039babffbbf9e6f91186ecdaf29598a","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-31.tgz","fileCount":105,"unpackedSize":434488,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdbsXLCRA9TVsSAnZWagAAhr8P/0gMh6TILpROBi4uCSyG\nKUzCN7p2MtVbLqi86luHdFvDuDghCgskb7VAycfc+G0+5AkOENJsS19Y/Z9I\n/nlv8tQ5Himh2fPzTDX810fBspEbdeAvBEOb/TMv2J2265ocHBRYSEr986id\nBQzScErrFDpyaORwbRfnWGD/Lrq6jVkKnNay5mnrfZGHtlJGz8N1dNyNymiB\nDXaVEn8hBB57/wd3FOnk4SnGHzgHXp4UOQZBb6O0tPsuBv0bcG/Cv/y92SDe\nlnIuc9XJB8mLkIZdGjBE7Ag9FC+E06CVN3yxmUeBr0bjY4mphnUC5zkqwhQZ\ndS9DMyA6K4hlZVg9bJPjRd8s7d/BCIUa0USpfWglBs4XhLJB4nRIukXY4/1t\nrSxFRIB4CXhrlVj8YxiLomyBD3uWmuqhhRIdIw3LEcZ99LjK/AJufzkSv7Zm\n7dIUDnlNvcrFw0CgGvGP3n5jodJX5Ufa6z7ubVXCx18fzUJQCi167tFa01TP\nsjDKWu+CZiH42gSGT14+JAqBGWmathtg6zg1lBlYlPYGygnfkSGaLJMCNud6\na4ZVRbcAL3FaIVP4LJsyor/gctGEmMpd49A64Cp+0lv7zQEMzNwx9LhFA5bV\n5/UggOM16SjH/ufdS2A36mOrciOvaJYiaFf2AHSQhw81zSfCdmFQ8Q4Zyboe\nvWdK\r\n=BySJ\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIF2CpXCjJ84OwxTYcq5H0rIIksNYNybPTXUlyBNfQi/qAiBbQCm8lk3G6Fa/3Tjxg0xM3Csd2xYiJPtKB/6PkHeeOw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-31_1567540682355_0.9036469723020577"},"_hasShrinkwrap":false},"1.0.0-32":{"name":"serverless-azure-functions","version":"1.0.0-32","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"401c120e8c02cc8c75717b3f51532c98543fc8f0","_id":"serverless-azure-functions@1.0.0-32","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-7dnwWmPvfyB1DTd7M5pbB3cnoOPJk2OCRE9fxtALjVYnRs4m8h+GFarM28JngfcPt+Xw1Mu0DXfgaavcDRf6fQ==","shasum":"fd9a10324fa55eb5d6dbea387a38cf8e2018775b","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-32.tgz","fileCount":105,"unpackedSize":434523,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdbvA2CRA9TVsSAnZWagAAEugP/R3seSlnhlUWDfJAwiaR\nBMq/aFM05rHFWIZqJWDF9Xl3Qrr2FDQSbGC73p3hv99C/qPOlppLmqJwxF2R\nB2snuBhgGik2P+I3cpyfzgsntbll/Guh5oJJg5MEXT+lsHJh/64IwvM2ptDE\n9jjtGXU8oEH3JMU0pAjzXABHhUYuu34ALdGW6jh2j3fyI+6tQXaanPMVRmRd\nzfMKNOLmQzaS4lhyNFnX/OJW6knSUzk1jB0AM7UuqmMf8+RN+HyayEmXe+ar\n9RnwPpr9q8VqepcQMryBn9Wo8q2y4CCZPYdzP0RaPrBHS08EQ9gwuGarE/og\nB96BdyTzqpHjdxLWA047G3Az2IExlBFCdW0WygCkvNLvKqR4rYZRtxoM6wa9\nFP/GRqS7sEEFRioVsLbmBZkfFFsGfGLbCcR8fT49kXv7lEzQ1Ln3/me5rE9K\nlvuVQ7g0eAjmbd5T3Zzt0n8v9NRhiO0BBjDunmoRl9qdMqd5NQKLQE2KtQJA\nwtICsEM37sUtLySyjYFf6MeGQnksU1fRJGuIQhF1Pq/uPY8Nl2yF43gHLxGQ\n482DZIXWeztpr1sV8E2FQJnMmZEYQ7/mxh+OGdtq/oua30HPGYjf6XEM3QJ/\nd0gx0qEJHUhjnG9vllwSx2HAU+S13HU/JFYQXhpU11bJ8woTvXocz3mNnf3d\nL2Rx\r\n=LLDp\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD1Kg7efkj+FExz+3yLmcg4ezDFBCs61Of7o4bckAKgqAIhAMOkW1ZWFEffNtEqLTdwiWt02o24c4wtst4cqIy2j3k7"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-32_1567551541623_0.7779027036140858"},"_hasShrinkwrap":false},"1.0.0-33":{"name":"serverless-azure-functions","version":"1.0.0-33","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"b6433a64d0126b248ef6e78efb386d1417a99762","_id":"serverless-azure-functions@1.0.0-33","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-rc+62E3wsa+82GXgULSVZAvRqF/QKKfapaIvXOTyhnVo5MPS/hzFu5eCIhGiXXVPVvA5/UmNvHi52iHcSAR+Cg==","shasum":"86bf08518512e25757e285965399012f2d35a424","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-33.tgz","fileCount":105,"unpackedSize":434569,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcBe2CRA9TVsSAnZWagAAOUwP/2/KdyN58Ic89ynMthY4\nTL7WhIIVzWUDAB3dSpYub/L9bSdBMUZ6DDJRY6mqJ19ZVoguiYCEx39eLE+c\nXA9vKXqsGOQ3W4prU0Jm3MQN/LVsToxB3D5Nu7PLhBkaWuavXdCU2bkOaBQJ\nCfJLGIyTt7iLOxXnLVjQrIoeyk278+AMv7opm8k0FgsAgFqYCOCv/qE+6LCP\nk/3JuxB2TidOYcg0oRY/Mx3iSDPzCpPPpRde8tNr4wphzKbrh+NTdAi4Wpw6\nA8pXICSB4gyPFjYKp1eqAppbVKzl2LCR7IngAlFYhpoaADQ6x6Op1jfNLDI8\nh5ErOYDORt8uu9toIkHv0RHwfk++EjPFam+IXVIKc0mmwSxmT1+nNE304jfd\nd+WYv26aLFLb4B1twALiqKT/sLt1QiwuDy1SHTbddtTG6hW9S6XE+1OPdSdh\npRnmU/OyFM3Szjugwlp5M79RRRK5EIPkLXgj79/qinG6suVm0ACHSqApovGa\ne1W2Ev0Rlbh3ySikRLuF5arlIENjtuG8l/Vu181WRwK4Oi86vWcpc2BV4aHu\nzHOorWNF1jlUzYbLk/OquN1+8CH1pYE6izTHsMvkiXmmbjJ6KaDJuEdGaKqN\nx0FsfeHMtsUM9/vhgqUTkx6jQskqQSEFPE/EqbquMZuxOrnQC4dW8AOptLXV\n+3dG\r\n=2Yaa\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCkCiWH+jol6HPcZr0qiVXnsT6/4dz33R6+LoWN1+abQAIhAPf7/VIeVYTCCM0F2iUrN6DkPTrSTEm+Qu1gKiq01YVZ"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-33_1567627190077_0.8958255133482396"},"_hasShrinkwrap":false},"1.0.0-34":{"name":"serverless-azure-functions","version":"1.0.0-34","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"0130622bc5058f9325551da6a9c2753093da9646","_id":"serverless-azure-functions@1.0.0-34","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-rfsxSnMxkE2l2gCPH4weBnI+8wwlCqDTYtSXZDKG4OrjjZlYmC2biAIzxTKFM2WuVPjvmiLLmZJtnA528wLIDA==","shasum":"e4861d330388f16c3f910b88710b400656f6cd25","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-34.tgz","fileCount":109,"unpackedSize":446786,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcBwoCRA9TVsSAnZWagAAMpwQAJdacv9V25xSHFYgNB8P\nds7gQ+jmsSiCeHqY4mlG8L1Z0csO5aavm9N43zJ/2SJtnoFReiqg1jtUV1It\nhYP9/Pk56VmFHZ8MlakqtFeTn6uETTUL2nihd9nm2nvGZ3oivKE76jyuzTpq\nHxvCKhTIhnigG451+2fBNTs70QHL7nT23JynZyyPCZ5qDbDhnayOnB6vPDoi\nvPJBZDaDEsgrUKZ6ble0bD8pYyjC0aQgbcg87clDwvpm9za6b6HgF+VDyQ3V\nnaaX7QsSUN3ilk+SKu1o1ESg7vnBWd7CuhboFy/VAqKYTALynSpBJVH8Q3XD\n7wj+fRYj5BrjKQF3SdyyJEIJZfCXUXcxm3r6912yuJNeDkglFzPvIlHx3aqu\nIeBkvKJnQXP/+/L1SuAb1oxLKniU+xUxMyxhCH07lrkEGcl1ehmEmehtN5w9\ngzh1IYFB2bOveF6FkDNfT8ysyr5JM2E58HRKXW+hJI1OM0x+36Xu1pzucL1s\nQ1AJeCJElac9FgDteHR+RttILClbSvRifVCkXCGQbJtIAdnG8rmm0ijPXFt9\nibrDqlU+HvR5Sjz0H5PUesScBFaSpgHDLupNRvHAEGtjaxQDp8VQI3yI0X/O\n/3KpH5Pnwg423uraT+QL1C+9FKUaXEB3vrASdsWr3jCFEMYbeRdSXkCRBwkt\n0XU7\r\n=jlIY\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDW9ioycaMRKYuubhICBnyKWk+oIVF1MOopj8OkBwElPAiB08kuFKex5SOx2G1h0qWpP5vxaknGvPGIo/MCym+ZRCw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-34_1567628327692_0.6188779143324701"},"_hasShrinkwrap":false},"1.0.0-35":{"name":"serverless-azure-functions","version":"1.0.0-35","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"c0c34b214d08da715ba7c9c31cca6d30d6e04c6d","_id":"serverless-azure-functions@1.0.0-35","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-CXu7Ak0wH85VAGVr7b6hIyJBVguFGXFd/4reWk/rATP8XOhWTSqQ8NdemD71ltD7JCMyY+PgjyBpyz6vVO0z8Q==","shasum":"d53773cd12a3dcd58de38ae5415df921645d5e1b","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-35.tgz","fileCount":109,"unpackedSize":448245,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcDLdCRA9TVsSAnZWagAADGsP/1/jGgXVLcVtLdE+5Bg7\np66943hGf4LTHl8LNnfBGjeou9Kn+Ze4i7qq8iCX19C/P/nHcfHm8uJTDk3d\nK1A4qU02DK3YpVbG3u1I3tPjs9prjUghRpSVD2wUqua5TH3rMjpbyUQxTCC+\nBKtza7Yp16vD4OziN2p226bNV16GQIfuzGakBeAqjdUfRjcpqZON8At7aWr5\najoDxnUAlf+JOz2eyCHf0o7mCwyRYVZgD1PYCEepByYF4ISFc6Axoq6ZlWxc\nlIc2vraVBdkloPy8U1ssoLBXKy8qWkLrX0ZwkbwOSsNinBHRUZwQxkK938tx\nMQylKCFcX6PwHqf7wEmliInNPyA5jNLmoSoK3yzRYoliWouckOQcZ3/SDF/m\n2yc6OK9qD8rT2IhKYHGUFLBcYlTQAz0mpOKEzATKWN2aVLb2hUJS3tVDm+IQ\nIecxH9Hoyb0G0mKStHdjdeBmrTaWCVwTc1Su5z+Q3wlUAhDO1o+Hw3qJycVT\nuCxLWVZzdrqlZgwtoVHuUDpEBtds0LofJxpgB7m9GMWgDi4a/9kV8lBEAHe8\n4Cih0gtWKogxJmeFQ0jS9WgSha1j/P5r3QH+ZothO3rxNOeprX3K8uHZUXYG\n1/N/tpdYjXlLMNcH79vdDG8a4B7Uwgo3LNtkpmDOPPW+YX0Ij7Czdx8Wwfbz\nhBZo\r\n=O/Pl\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDpQylIw//9wDVDlH1ZIjARczVPxBRh+tsdnNgtPmHXsgIhAMceYK2X9P+a94TX+3JAdORRnyAn6TkstbkI7vzIAng5"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-35_1567634140459_0.9097568068383064"},"_hasShrinkwrap":false},"1.0.0-36":{"name":"serverless-azure-functions","version":"1.0.0-36","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"609992b6e382c72a5ac1c2fcaa92861dc0e67c10","_id":"serverless-azure-functions@1.0.0-36","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-pKUubOayb9ChKEgI2rmGg5nAGyRcmBCGJGVZu9fzxqZxiktHv5LtoVA7dhoumSMNgkjjm1jK4NfWpIYdz7oMjw==","shasum":"965bccc7075471b1316e6d8814609f37a1757145","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-36.tgz","fileCount":109,"unpackedSize":448952,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcTA6CRA9TVsSAnZWagAAoOwQAJBGrPRVeCrrU9bHRqal\nD/IvyIeU5geMS6Hyn5KfUKZsGf1nXd50jW91l778HmrTHH4MdZ4F7BofMhmY\nX61onAsXJQuXg9L2GBrEZZxcRfFsW/ak3rGuK9UkGPr7kbCCv4uKOqk4tj/C\nXFTfoYWBGkXas89E9qrJeeNTOU/f15e9aoaeZyxm3N/ULcDOcBJNsfdaYFfW\nISJliVhug9P4d4mbjC6kkVmE1f4/+lR+ruQl9uAp4UE67gWJx2rp/tB+F0+c\nvB7AHrY3avLcWGGMnjh5dw/R6so+XnsidCZFmRLjCgAk8yTTyhC9XYPDL3MY\nrVyL80p2gBnb3yeQ3q/67yABeh+6mDQmG7aZLjywTvgq6ZsGqFWA20EnvZRa\nGuufYL7iCuhNol9CMl2nw9e79y/Jxy3wOvlhxXWnZWJBOH0pFq07Y5dDs+FB\nBOAVIWOBJWXUUjRc4ZKGJUfOkRdzbpyJMdAzlFjjsqXUSjnZGUcfkF93xaAq\nNNRY2G0aP+hU5ajTMX0AZpmSNQMX/Re3e7jAi+5GTOqTEBawWOr9LINYLf7H\nz4UcfImHs3sb+NMO6XkAHp8Vzli2mFh4yE1dERrTGH2TCcFog7hOiGVx6JpT\nhbhVQxNRB15kbGK2iGNjR6DSwmepQzI3cehTziVD5lILsnUadaYvehoU250K\nZx5b\r\n=kswb\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIA6Fbx4EuCJl7J5KOttz41LH03xo399LL94xuOQMrGFSAiALopxl0XxxfYP54SxbRWFCr05z4Ct+13xwmXWWaz4VAw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-36_1567699001940_0.023568286072078726"},"_hasShrinkwrap":false},"1.0.0-37":{"name":"serverless-azure-functions","version":"1.0.0-37","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"19a83fa5689978620aa0d0d43c3cd304bca7bf45","_id":"serverless-azure-functions@1.0.0-37","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-Axr5iIYPo32DPcniFlPEN4Dca1dZNe76E7FJaLl61CV86KKNnK2+cEKrMlAin6zK2DTL8XPGKttpxmgmmAzA9Q==","shasum":"e5981e0c3f06cd1c04dc140109d16c4c7cc9f2f9","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-37.tgz","fileCount":109,"unpackedSize":448749,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcYBVCRA9TVsSAnZWagAAmmcQAIPODgYm3qBqurKrNYlJ\nJttlA8UJUFOBKqKCKPOmo6kTQOjBwMa+5e/6DASGJKW5Uz2LoUI8XhYuMS8w\nwEdQ90CW82W16EcC892JMSsP+FfZzDTIvO3vQ7xVeNLLlbMp6SjuAbD9TDM0\ngf+0F56vKGRrbDeI2cCaTtl7so8DhlmBsUos1U4I2QaMp7yiOAAbf4jGHmpa\ngg1l+VI3xh64Dcx+9Hj20TNq7JWnMGMxBGrp3efAN7lXWC+BUIHon91WZ6sq\nKxO5eCkc980dVppohLoxkIeyxdicJnZjW23dijakvzKg99su8id+Up+Pqom3\nmUOetsdc898PQQfy/bFguWmDahFp82kCcXSUVijn7c5E0E/4C1hRwNyGFEd2\n0cxDIiqBjp8sT1AW6Xvcl4EI5rZMj00BWt4CzwYjKPpItV4j68bCEVk7Y5+7\nsFMfb2mOsF21UBHkGMApBX7Ham83n3qeo6Kwbu9Wsr8Bm+Q7AV5N8W1bBlpx\n1CjLp06HsgYw4om9Vt3u2Qb+JQZwWoyieiLqimYwy4kIET0ch6rCBsSpR36W\nRx9b6ETGrJMnMH31CKW0CpQnTaq+BfYrLbFNzyR63Tpqg7OvI7yvBQHmFwyd\n4HyFs1md/GEF1H4c2WP8bWv9aONANgkNTKDHGGLXt1pl7Put5zzC3lnBKrn3\nIcl4\r\n=azim\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHxPlD6n7Bz4gEE9hCsCmKoRzsZ0bN2xKDBYlHFS7NLtAiEA6/dlBYH4edo0T7ocW24DwJYCHgwmSg6TMVhJt2V2kGg="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-37_1567719508530_0.829790068410035"},"_hasShrinkwrap":false},"1.0.0-38":{"name":"serverless-azure-functions","version":"1.0.0-38","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Coverage Status](https://coveralls.io/repos/github/serverless/serverless-azure-functions/badge.svg)](https://coveralls.io/github/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export azureSubId=''\n $ export azureServicePrincipalTenantId=''\n $ export azureServicePrincipalClientId=''\n $ export azureServicePrincipalPassword=''\n ```\n\n **Powershell**\n ```powershell\n $env:azureSubId=''\n $env:azureServicePrincipalTenantId=''\n $env:azureServicePrincipalClientId=''\n $env:azureServicePrincipalPassword=''\n ```\n\n### Example Usage\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"2fb6a418e879e246d4fdc9331c1919db6f5fa4e3","_id":"serverless-azure-functions@1.0.0-38","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-iwah2t+r1VMRV1Hvd8Mwnaf/+PsYfFGbD4KY9r8G879N2rDOlDfoJWuFVbXpxMPvBle9IZTDavXwOCLwylwlbg==","shasum":"81c9af20eba7f39a3ffccfd6d73161a96ca0b17e","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-38.tgz","fileCount":107,"unpackedSize":451748,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcnsrCRA9TVsSAnZWagAAFAwP/j8HlhseQPm5MirItWB3\nP8uHMiznslpCjCKfFwL6UV93WHEFpMCDZPMeaUxC/dCCInLHsEnQ34/C5iIT\nhhneZiGJLQfIFV6ZeaeBaieXuIInK2CQph6smREZINo7wAIsstvUM7fXGxnP\nEOc7Ga08K5tkpWFOaxZIbn0PraFrARpmPbka1bWxdWW37/ydVqhe2qT9LxA1\nDJnWNgngpb9rkHI4cVOosuo+LMQLaY0Igu/GRRqIh0GhmB84sIR9uyE+6U6e\n5Fvn9XeYisT++Fo5ZhDxYkK0wl6Q4mF7um5/QofxJFRw9m1P/mW8YdHIe3ql\n7APuDRfX85Vnw+8V7SdBa9e2BvyqF1NNySpctfqR8d7BzxLWp+wOM0pbaiT6\na4pQ9GheKNiILP665vSUhFgf7O3PuTnEJzdwQyQsjQtxMhczf0M2s0s7mP71\ngwLUWqSR4MSGngXTd3O6DVkSRwUbY8R6tTn5QZsFTHIceOfbxGlNmG/QboIj\ny1aEsl0D2DaSOGq9n8nKxTFvnmUB83CYJ7k0hpI/nTiLaVX9iZiUnCTywJ1h\ngF44Mtcn4S6OHwePU2K6y0Qvo4ozmpKAdsThO8lZlmkaRR6Ja5H4hsNpN4cm\n6dB6V9sIC2gFxfipidjKE9aV/xb8i6nGfBWEfjZil+qn85OG5iMZghciVhcP\nSbWY\r\n=tlrX\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDVGCu+S5GHQx4w/fqzd2h+CbYep7ePowXDZkddDj3wvQIgA1oyy2594f69WnDB097IaEuWVm6i52EwcIqHoT+eIxw="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-38_1567783722625_0.1716246451086929"},"_hasShrinkwrap":false},"1.0.0-39":{"name":"serverless-azure-functions","version":"1.0.0-39","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"e53d49943feba080609188db85e62facc818cf74","_id":"serverless-azure-functions@1.0.0-39","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-sbaB6hWvmsUQT3V8Am9djfbUoCTaW/S1x9vygmCrCPwz+TcbgDPV8OYJ1V5NO72Si8hNrsQucGiGh1yaPbWQaw==","shasum":"d646a917cf606fdf635758e296b6a1be0c21b3a3","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-39.tgz","fileCount":107,"unpackedSize":451739,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcsOnCRA9TVsSAnZWagAAS/gP/iaP410HowEiY3IhCQOT\nKqov6/g6lH8nZL2vU49MM9/1+gNTwdjqwl8gbrYpzMPj+lMxa5hhGr5CCOVy\nsrupDg8AuERo6bG/VJEoOgoOKLoTO27/J3E8wRCQNT3g/9ud7zdhtktoUUgS\nko/1lr/aLX7+nkH2yS0Ug0QhpYa9SjGJRj+sRfp5sIdbAbmTG6RfrpCXhfg+\n/GenQvfEMhixWjyWOcyY3A1Az0Q3BdoMoVzrCmvcqRSn3dT3WU1LpQlgs1Wk\nVqpXbcSZ9hPZM3xTyySucHFTzJH23pPqcZvKyYQOOeuEZC0v2dqkrKHEMWYh\nWVaMlNKpgaStDo/Vx+H7AmvV/tNdQ0SEoTYhmG9XEoRmwVQPF/xD+dANSI5R\njaxqix8oPc2omBp2fgYtV2Kw77s6dAyiP37BZOsNrB3eUHAiDJHWn0vvN6km\nhuLJOi9QuW1RRvGWdumQooeJmuoQgLBdsz6SkyQm7P363QZmBIlmUYwfxUtO\n+V9B4l1LRBWVSWGvlzazdj/roWvsz0WWkcKVAcu0yDhJE3jkiZefgR26x15x\nUHWVaoNSifi8XRGss9IZVEitzVdVu5xEM3yZFgK/bkDzkIPW6t4QHK7Fo5bc\nOJaw/Hba92hT1yCe2ELs2/SvYcCe+ssr7XAXWOj5uzZBlMLTF79Pu7d+aXX3\nog7b\r\n=Gnji\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCICktINVPtp9cANOeDwV7uPv1IgeVPqVEEnvJz1zJwfd2AiEA4w+0eeP+V/L8f+dNMZHhzfRZFIT13av1z57mgewE9oQ="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-39_1567802279180_0.36924980633018323"},"_hasShrinkwrap":false},"1.0.0-40":{"name":"serverless-azure-functions","version":"1.0.0-40","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"69664bbd1d7451269707bd8bc38d801ec6ea3294","_id":"serverless-azure-functions@1.0.0-40","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-vAfMwrGvrlN/V3z6/DPozWG2zHK5UXsHeR6LY0wxJliRwKW5z3dAI4n3tBmUXtJpcnOtSKvyE07qA5JDapReDg==","shasum":"cb6fe10ae7e043274ccd3635e1858447fcc754d9","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-40.tgz","fileCount":107,"unpackedSize":453188,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcs1KCRA9TVsSAnZWagAAgVYQAIU/36OmaADbnGWrUu7N\nxzuwNiAzQCWOG8nV6pU/a0aTSL6m1clDtVTJ3Em55j7gy7LWth33CHtb/x+M\njxj71hu9WMj4QutnpH1TrMiIYJK4moRtBSQ2h6HgXVcX7F1n38lO5E3FPEZ8\nKMoM0sUVWDftM/uFcXMpSAhJuOT3inxH2s91FXkw4P/6AzDXFf6dbUxyt4yo\n6E4yWRF3BKep4UrAIdvm9mUF2zVUt7SKOhDrw7Bsgh9GUhCysVNcgd38McRw\nLopi9Q960Ija343/GohTRboPiYynjPPNFjF4VifThWa39KWdX5TpZJhRXR8C\n5sS/JpWH34QAu0Xbj1H/IUFtPkVPZMPyTGbtuH2toJcBm1d6WkXFlF3UDB6o\nRjN/VyS/fqPXlMUeyQ808TkW2iFug+YtWxT95swEgaBsEKCjjd7InJGTuhng\nT+r7M+7N/lABIQPSGPpR/2xLO2b+26dfqrsrh/LhDe4vBdvIX+SQBoHZki4p\n0BlIRooAdZN5MDAepriK/Hm4x3GfT+/z7xkF8LxPLT1aeeWQOx1IjX/fYubs\nz2rPbSTuJirPB9l4w2psMRbc53CR5c/tpqYHc4bCCKbALzKq+BIMRYMvsMSz\nt/VHtjFm9a2ceBTA31mEgXavvM0e9vGdlOtVJgHefnYtypJHt3PlJGGsx9kM\nXiHW\r\n=MSVc\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDFaYjRtrkXLC8re7lKjsni4j9anFLU+17is+FZeFLzgwIhAJsScL179s7EKDqZc2tutSl7WIQSLCotQbYAVDuCvC2v"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-40_1567804746218_0.496263558088029"},"_hasShrinkwrap":false},"1.0.0-41":{"name":"serverless-azure-functions","version":"1.0.0-41","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"0225527dbedf1d9318ed8b79cdb16d6298054968","_id":"serverless-azure-functions@1.0.0-41","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-YBV0Qjf8h0vCTFWPeC3RjA6QT1zUXUQJprbZo0T/tnVqDR7pe34zuNOy75vPYt6NBCGfufmlf0qBXCd0xmceNA==","shasum":"3e47b18e7c0e35db029b8be1e577243c90f429b4","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-41.tgz","fileCount":107,"unpackedSize":457676,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdcut2CRA9TVsSAnZWagAAMC8P/2F8vfOBnMO3K3BSn70b\n48PHGCwDgKw7WnoBq1TWnbhX3xLJcW2yYQA0MZ2T+mFYQFJpdRpaFsAkKzaa\nmXQq8bw9clvwd5ndYkLjhC55W0S4kN+/6RURLB2PSNk3Zi/l+2gzLYTKDQVN\n+FPwgMHUb75A2gMzs7+A02Geo23bR0Cta6t6h1c9pdJVAHk8Q+O61ehcIyRK\nMDkNkulihqiiwxwsEFKLkjGSWsxSf8z57CWL1p1tnN56uLmLoYRhBFFHOEsK\nZ8Vt5uyj3kaotI51DvLQqb41U6OK+uSHUZclhsE5JyhBWjaNqTrWFBEZsKVq\nkA8tB9h75zsEzu8v80iHjTXQwS6Bmlx9aDm0usHbELJVCv/JbXbgQLKpoSpz\nQyYMi6m8UB3+srHM4U0oAUD72Blgd/VcrNAqcaC1h5e5/xR8Iqk1ZYB3LaJ7\n0cOHmEjn44W7X9XJJOf8cE8Kk/MQH9Ow/xqDeAfKeoAdycPPQI+/3tiCGY0F\nK8rz/UED+BwWf0Jy8nYQ/qC8gNvlHWe+x/wRAHn+cGB89eGurXv889MrAhtE\nNHwPMu2Xc4SZAhFvV6ihCaTbjtza/HT5M7/BcRv3md5b8t4QzFaNQeGcYl4D\nahJb+NIcth9sU2Znu8mIDMjYOQmDeqtiUNVIVQN6SAxw/qyVXzIXc6TcsVp7\nArh6\r\n=1irI\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDplrfXtb6rcdywIA+XrC8Cr5mv5GDr2Hm4lXeAZY8uPwIhAPwpc80l5zwvFsHknWItzKl1ccvDQPr5rfDYYv8/fs9r"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-41_1567812469970_0.5401985658716617"},"_hasShrinkwrap":false},"1.0.0-42":{"name":"serverless-azure-functions","version":"1.0.0-42","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"8ae5a48ca3515d4898d17fc3e3d1b69babab2a81","_id":"serverless-azure-functions@1.0.0-42","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-cwhmG+Xv8j9U+jkAPr0GICjzeFsgdWt4h42oSU1hxCbIG7EdMbJDek08JLitEAmrOav0ppxgqkhC/pWDBlDY/w==","shasum":"fb9e23abd7ec79723e87c6d1a99b04b8e7ad7867","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-42.tgz","fileCount":107,"unpackedSize":457923,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJddrF3CRA9TVsSAnZWagAAqUEQAJIH54mvBQ9LEPBccy0g\nwAlIYtRUn7n4chzA4w8xwn9+S87r3MFqvuVZLImn+8hJ6Cep+0YKRHfQNyan\nXKAMtCbIOIYPhfj7/9EaS8HSH4KYyqvomSBde8kr7nPSGTssCT3i9YwAVWyY\n4YrRMmqENUjKriWZpQ06pVrPAGypCnBVnTO/ahvDCw43b7y6dXdcS0SVOZU7\noSZUPoheOqhDKpa0kMVwTODZ8sf+ZejjYx/8pY8SrfGVhEmKPjZ0fO1wvelE\nVqc4NT1D9OS6/zM8JfQcnNhANk9ZL+5YC6luuK2oFRWQvljm8srDbK4hMTDN\nsdgT5mD1pRL/J69zKvWDxML9aZAn1kodjFd6RHPG9jY192uNaVbMdCPyWurJ\nKm5dLSu4SPIE3f4o2tsRhsgZ1Uz96BeV1NP3MUzcN6u+26WsrbCnGkpseNvA\npfoNxRkrosp9NB8rEfoy+YJ3u8XmeEbwVSmnKzzKzdoAQmV7mNWbq96MFKwY\nYGfpo6P0baXRnDRyeG2rki2UT//vbku1B7wkjtThNTei4gemOsTW9UxENJ8e\nIWi6BxxXEvXGuhsgeu4BJEQKHihB+y9OAachX/yWyS7tLLIZ1cLZ7mGmZQfv\nWCla+I9N4OfKwpYAB0OD5wmxBstoslN0PZY31NL/gAuOzOk6voAWzuBFObRY\nbxGj\r\n=ML8L\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDcfLsnkKI47s8NHOZGVNuRhmbTbJG9VD1okvekTNp3KQIhAOoQIqONWSkn/9k0QR2tLXklS/YGJ1aB6IMz/WQdP60q"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-42_1568059767120_0.3345635403545104"},"_hasShrinkwrap":false},"1.0.0-43":{"name":"serverless-azure-functions","version":"1.0.0-43","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"d46ef413b17383ac4c9f93e0e603134006e9a4d4","_id":"serverless-azure-functions@1.0.0-43","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-xYrwhbjkqtt4jLqJf1CFXnZfdhmMBdiOXU8m6Uiu4OsMXnxZeHVYzHy5wLg/W97FOOsbXJmM+F27cW9OVdQs7g==","shasum":"6a9c274a2563cd8c9d8e0e137bf89e321c0bd995","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-43.tgz","fileCount":107,"unpackedSize":457584,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJddsPxCRA9TVsSAnZWagAAsKgQAICrDx5dDtLpHuHHNznr\nra+gz3EvwaoVyQEKcG9ng5xErxAGZ9uKlQlhz6/iBU7MAvnOpAgf1x3W4Ery\nJkLHQVBSgKS/9wVpkukelTed62S6ZitvVqj0KQRR4NgnWuWYKyfVwmr/Pp+o\naH9OMdUD2B5fy6XFeU9bwK/1vER0ChdyU6F0Lo+fgI+RRpE5TcCvcYyG5jFX\nI9dYrFt/abYltA2xbdujoY1geOWA8zmIDGvAYd9AvDK9SY5yO5PyfB4532Um\nPt4MXZg2wGM00PWwqHIx9VxDPNWoAnjcIWAGz2BD9ca76ZsMbQicdXjOPKzL\ngPynMVVvIG3pRgVn9UP2Q07RYpw8WCNIwJR+KCdE2Urx4Tl8vDhQ5aJTobA3\n43U9gqotsRhunKeEn6KsaOBs56kSL9N6qB+Z5facerrgAAu12O/coJYF/reB\n2a3f74Rg9rxvDxTf97Eimt7DK+815lOG9L/MX+1pWwoLddZlx0pCSKzZslbH\nuFZoOddzU5mAmZ2nXJ0L7D5sN8dUGdaIhJfHImPWdcrr68DVxxms3Nm8cuny\nMlyhYf28uKtgHe5T31/gcpGPzXXP+c/Wi4JntcDP/p6kIti6jV6j6ndb6tbP\nz+b6wKyVyxrbJPJTA/cl6Ya4ZPGPy2iNbhUcNTK/TWrFSU9whXCc9tscezZn\nHZsA\r\n=qkZK\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDFBM2Zf8nvzzJkC0fIs5nNJVdmfyZBuFrs/Ug+I9YUgwIhANLOhmzM8jbUBjah17d0GVnZ1aUGIuOgYITVvYhuXBax"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-43_1568064496558_0.7465212017085752"},"_hasShrinkwrap":false},"1.0.0-44":{"name":"serverless-azure-functions","version":"1.0.0-44","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello '{\"name\": \"Azure\"}'\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"f02049eace695d0d1a51aafc9557a67db9cf8820","_id":"serverless-azure-functions@1.0.0-44","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-8UBAR+1FNhuGRixgmA1WUdJrbtRTpE7HEXJInEMevcV2FeuslrAYJ/BcJ1MA+QfD7mKAypgPxp2TBFKYVqyzqg==","shasum":"09de4a5dd1f95b1ed400c1dd3e68dac8a5090c61","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-44.tgz","fileCount":107,"unpackedSize":457704,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJddsdsCRA9TVsSAnZWagAABpMP/ju2WyhycKSeama4gl/6\n5nOsnbz6Ktrkz7EPRX40hmEPzUr+RvNKcJz+k8B59SykADPA+HyokmhZJv4m\nBo+2bMjFwrvl01RgWUNRfm8mhNk28yKhhHiv+t2XW9ts1nOGRHbdeVkWVMSo\njsQ7whR2dfwzfEtK5WrkE2C2cYGxpZjIGTXE6+ei+SYhxIRuCwaldwFy1E5D\nvUappicALv4xxFgiHtaZxbTzarHVkNyh8XXMWLUzv+Daa6MaRD998VuhkNoK\nCPkeFNAklsUqH1QIEhEIPQLPqdCVbfrFnhSCrSKa6uCTTHnOzLgyUUKIp7Kz\nCLvCRMSHmcGXq73cko0Zm1WkDcl7dOYJTDqPBWtYZbqn5q84J4rqDxBCz/vs\nEafyJVAPtIuwJb7u4HGumXDpUNNQ9ulpHSAbHNKB2opDN85ku1/zW/Lz5D3N\nImKoA0i1FijCk3VyppWvnhBlxxoVbkDBtCRZq20rjP0Q0Rm+sWcN9fEckkrf\n1DUIx7N5w5GwuATKD/pc364ePRVzFsod0hXxeu3aHCLs3/S0nfMAk0RO5MZe\nKy6ZiwAaaiL7i2psH18twVSIgBFHRucvkL+7sCfXd7DlAFf9ZzlbDGie2FbN\n5Yyd3fyWG70VrelwfvV3RZ5tZlnFx6q3LBf9Mj4CQxrD82Ml5jAr0UZoF3N6\nSh5q\r\n=13M7\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCE8vpmaf9cm5CXTbh8rzX00nif7dlJLutfRI3ek/xXSgIhAK6XEZ3zc6KQNNOkxCl7GgaEZVvepl5MfVM+4ZnyXUXK"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-44_1568065388353_0.37106138996724525"},"_hasShrinkwrap":false},"1.0.0-45":{"name":"serverless-azure-functions","version":"1.0.0-45","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"243ae6ea95640b1daadb30460665d7fc351373c5","_id":"serverless-azure-functions@1.0.0-45","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-7Keb+yabFObo2iQB8r0H+8JCh8SFdvIpgvimMsyR3JDkNdLvCnK5dhB+BTSx1BVK1au/hPYSWXiJG2kV4g86Mw==","shasum":"c318c3790616f9481fd926668c2f4d4278755c86","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-45.tgz","fileCount":107,"unpackedSize":457936,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdd+ibCRA9TVsSAnZWagAAZtgP/RhcATeATaZuL2T1LV9o\nGJkTnHWYHxPagvvpjjAttd5AGqAUa8zGm0/Xi7n2GDtKN4n/XpfWtTxKt02D\nMvO/b2EBntgt5u1IOYOVgkdi8iExXjQO3yLij47FwDyMNfCI+EnYyf3HAknJ\nM58kSl7DVj5f/vlEF/9mD6ZJeAlaZxOvrtjgACuVDyROVRUsSR/QBlqjUiYB\no4w/Rbkny8EynUjCptdJTCOMRGGTbw2szwwXCuVJZJiyYdpl4bpz+SdsagXp\n4OOjYu/5yRX7AJwHjcArTKwcnetj9EddI6iUcknqbaf1YL9UZFb7sAIoRGOz\noOrx6fovontK4Sop5dXV/+RaP9LBW/I/8++uYehvOora0MSBxzX3DQGCmvIY\nLZoCGpjBXIzDJ9tEfPpVCukdDHuiRlJcw3gR6udMMvuOYV1/5bnDgQkURvGO\nR5jZ7D5Kd5VHH2ojQGxtcUtzOGg7+g9Ad4PltR7oLhd4P0FhG8FAWBfw7k6c\nwBTa4UwHK5khvMAYoM4I3hnFzBVBmYUZrqQr45+alJ/YI45xG02KGe4sxeA+\nHIkYrkcfmDD1F/CbcQWLTNq3dxLAI4YEmx+BAvguFpAA2SjN1/omjVI4/6V5\nYp/6v1Ua04kPBmdE8fVuxGhu5o9oX7E4A7vW4lqCksRkUmRTuz4ZvF++DJLk\nq8F0\r\n=pWdN\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCHk8ye1S08YszAdKAy0UoeQ3Xr9Ohl1aH8y1yZwI9VBwIhANdRql/ALYXP96GFOPMv8u/FvzxpriWbK8CeYITiTkpd"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-45_1568139419060_0.2813193185144103"},"_hasShrinkwrap":false},"1.0.0-46":{"name":"serverless-azure-functions","version":"1.0.0-46","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"c505c2d145c268aa78ef328fa82792abd5f9079f","_id":"serverless-azure-functions@1.0.0-46","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-14OdSV33qNEiYkkmZsRKkJAIchBWTNQepuQfG5S6/kIoEdA0Nbtl9tDRgLJrS3I52zTWsgAjsVsyAO3SS9W8Qg==","shasum":"01bcedebe3b873a21a86f94062c48c8b527e3674","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-46.tgz","fileCount":107,"unpackedSize":458231,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdeAh5CRA9TVsSAnZWagAA7SQP+gJZvmRdxylN5vgjSuiA\nV4h7wtvHSnwnSgKWafvk+1KA37CSfUEhHHLEh3JuxpA5toDP8MiLXeXuvOSe\nzBpefUsez1NcBDOLxJaylacNOJHUm5eDXMOM20Y8z9fxIz6m5pdd9POcsQ5d\n7lwLBklwTcIkb2iw0BkGOZ1c0tRn+NCt1WTma6tuUfMXWWzJd8o0p9IL/HqJ\nEJ7xx8Mfv6vHQH2Ou/+HWakaSnFt7iZnQQ76ov1HMFZuKeUYuxzwAV4Lcd1X\n9F3ZR/jm/JooCUwf26QG1awCrvCJhlmy/g6LD8QDKrfCzhC/04hl22XVM2w6\nky+a5UM0+JETh0UorMHLXyLQ/0Lj/qWKsfcYeiVBP1Oe5BKXiJ/WPTmGVljA\nnflfd6ZQYsZ4TxSYt+n4YKfKS2LAHjO9+mrDWW7R7WDNkT1K9a7ohW+HPh7b\ntnoQ8NGrMlhJeb6ObOjZUvcJaNREZWRkgkJ64Z9OTdp5+hWuLqYOWHhQxRty\nbCmUbgVP0H3PfG/cBEvnuW8scrovGJL7WQ3774vxbib1+bBj2CaTDzsSiLI3\nyAXei0TYdUI9Ukh3T9GpROXPWPkV6+/ySYqsB5KG4DkvMtetheASOLSzeAQD\n+y8ESM3IIimI/yEDlVC4Q93PyAtAWrp3nwx8n2N5fztM4CR0bOgk7/1waWxF\nfxsD\r\n=o73O\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC+cDUIYWwDn52eafucfaLGcAIhvJ3LR1xMkuHkRMPikAIgOhpQfW/l279yxdYtdGeUtj9jmbXjGpdKBdyHxXegfj8="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-46_1568147576402_0.30946951816489987"},"_hasShrinkwrap":false},"1.0.0-47":{"name":"serverless-azure-functions","version":"1.0.0-47","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js v6.5.0+ *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"02f70167be29a4ef3fcfed87a4d83180f893a7a6","_id":"serverless-azure-functions@1.0.0-47","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-v/RKM21RuLnhddxPQbvBy9PCTq+xkqB0uFXMIWxY8KbkLTGq4YunVpbtaj2Xa1eWn6qPo1bSUPea0nJv56TR2Q==","shasum":"ecb337d0654099db565364542896f8cae6c3c63c","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-47.tgz","fileCount":107,"unpackedSize":458595,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdeqyXCRA9TVsSAnZWagAAOCwP/iJcb/99gpaPnz6B9mtB\nkKAFM8eiUmQaGwHQpgYjYQFPYz/cfYWd/VZ9qQS/eStZhb5T/oPCjIb2NmiK\n6vw7JcRRZraOBHlyJ3pJtjPSvyaQfoyoeY4vA7ATgPwYX2kKGSuYRZqD0Rfr\nHXm4o74DYoY2tslGH+hCW+LbBHtizXX8akBOKWm6WV3rgfXYzDg8hv+bS27+\nDsSdvibD58YpRVGQodTgxa/IrkQ2mxgZLQESKh77s7wHkV5QWd2YyiBx0/9G\nSpBr6MBoVVO/VHVVXyTrJG8EefpvYZBD3bobRmErAG+f12W2tLXVkW3AHnG6\n5P6aEtSiTn88SzBHcqJOz6dlE3EkGKSnRapUhW3T6Rs/Ki7aLttjXD9G9YNE\neBDMlCk9DS+xHzAFQ8I8HQsr952XhoYXxy7YPbU2SVQihp/lp2MwK4WVZAqR\n8ACwE41KSTFClRe1tXgPx0jIMuUqXVATweZUm0yxQSy1xzijH8DMq76hcXzp\nUNEksbUO5UaLVfwnZvpyrRp16s6TwLarrAvSa/J2/2c+vspXyZ9dZ9v1FPBz\n4SCZvRF21GY0dImeNj5BSgxNWFwf9OEHPd4mN/QO5feEz7Cdj7YnBlwt87of\nu0MoomdBhEDWzrX2Z1m0SKrUU1CmJ0932V1ohbwVAPJjVv169c+v6it2Ec+r\n8gHv\r\n=AbCr\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBXS0c3nXys/EAQNAreaQQAYu3pyAGzKxGWXuxhUHja0AiA7jDJx815HUvkOeDvSdXUQFK+ceBSs7U47lUtm49S2cQ=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-47_1568320662835_0.06396718830220927"},"_hasShrinkwrap":false},"1.0.0-48":{"name":"serverless-azure-functions","version":"1.0.0-48","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"796075096888b1c2ce95684d6216b3d66ba7d43b","_id":"serverless-azure-functions@1.0.0-48","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-prGWRRtX3PWaKq0JdPjBtEMyXhx7zm3KARdFxAIWGRnD9WF7LZ0DPdEbYB3QYxsQie3uzG50WX7/b+W9J057gg==","shasum":"f06fb5dc7ede4105c9e70c0658c2e8f3c6d02683","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-48.tgz","fileCount":107,"unpackedSize":458692,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdetOiCRA9TVsSAnZWagAAB9gQAISK3Ai9NTvydqhgO+Lg\njEcFam7q6ENo93ZXAp7Hbp4r1BIqej55+y/EaH+jDr2qtnaUY568j2LEiLW/\nel8+y9/rpgxzSgBMTgYJP2FfcbLe8xcPSxWTRG3xBShWOp4JTKc9cRKA1fCr\nsgAB4gv0kZnKOpwyTSgruWJPJuHm6tTaw4WdefY5+prfHiSL6Ddh3opEG7Bm\nsTlNzIYtyMRTQ64dxja9aDutmwn5fb3ORv1aaVXXGcUOHoqdbKEez+e/dAKt\nUclZDtLgI7m0M55UQ+8WiBVPxLxhLe2B+9hHNcXqHDwOSIUb1t1b80QeUF8c\nKNaZcXnrDTmYROcMIV/Uox6+/pc4TTU6zQTu+A80wVVHs5UuWikbS2IhQS6X\nDDK8oYjfZUOR4ChsYDQyYNL1y3KTExmud81sGK84gonHecUhnHNaoWTAOHZA\nzQjgzVqRlTcYr/MdnO6SGJZoOScJsEIJYHYl0kGcgGsxNZXOhMJak20a/jR3\nehpiGI15VEPF4CcukdDsO8YSGo5CFQyKL6FXiaZxpX3ViAhcOxQSCipypAsj\nMR5bTcsyMiL97d3qIJ6THIGKHnuK9ckMR55iRd6HbVyDFWPYfTXlfel6cTfR\nlF8wVprmFX3Se01gmhQSVqZGVjd3VJ2CH0gLKRPQdH0p0hbQk8M7ZNxHoKsj\n2YGx\r\n=hJlN\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCID0PM6h0ymgWzz7VP5DFMQ2KAKZ3DyeDEAuVFNbHMpk0AiBkad/M+DTC5ppDWrCgnQ7Na3pn3LmfjinsbvW9zLFHDQ=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-48_1568330657481_0.4598243950845142"},"_hasShrinkwrap":false},"1.0.0-49":{"name":"serverless-azure-functions","version":"1.0.0-49","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","generate:changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","generate:changelog-condensed":"npm run generate:changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"03ac787841b8ade619d4372bad0448ab349d909d","_id":"serverless-azure-functions@1.0.0-49","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-bO3uM29dQK1j9bMfYy+1NNgtp6ji9pvAwtnQBjwEJoNTP5tpGpStobau+dq7sbBTYgNcsPZ6VedVARzX7IeoZA==","shasum":"cebdd9fc0c24110d52043d70b65a745fe07c7488","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-49.tgz","fileCount":108,"unpackedSize":459473,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJde8rlCRA9TVsSAnZWagAAIiEP/jt03tXP3/DEq5cY7Dl2\n+7LVDcrS+tOpj9ti8USvIJbvNWZpvCm1hQMynRzhD/iraHVw8GTyTRNCkV41\nwX7vhBa8VnVFjFm350vgLlNizCDoz6RBgNYgpB44/6BvEbq3RiO+AKS4J7+7\nMnLRnFRhv9Y5E7avOatJrOacGK1pWfTD5P43Wa2nFP2YUK5ePGhfeFFGcyoM\nBOGlzjT85366Z5eXWRi9y5qsX+nn+H6xYdX9OxhVD2A2HtwOiRyULCia0Mnm\n841FxmHAsMAEZnpVlOMDeNCpqhioM8RfHJE9/ImuDsvKNpOrUmqOQARcfbIh\nkfWkJGEqWrRRS6ZJP0rXVFOcPvBOe5Fc9WIil23lUv3QiBUCFcXC12IlFcL3\n7y0K8wXEFJjGkLGLX3YGV7hnAGqKjYyo/Fpb+v+laX7DvJAv3R4bhNWd8wR4\ntjRpkPz4EmGf5gVbe84Ic1ogJUzgD+9TkQJYvgSQ4ZVmW1JdhLSm/YitRZzO\nwJKNK/4/cXIjzPjMTMlBAMIzZ1EyZD1RwNVIf2S/Dyr0wIucQ/8znrQzAM05\nQ/DdA8cAehxjzH8pgyQfdFYST3smvNmrWfDB4f9Wg4te5lEdYnPckwsQDJ+b\nVeJvAHJXYqeTCnWb69ykrvsfqMHKBForJ0dqb1/yg7vdaoKmeOn6jdg+XOQk\nVMKI\r\n=Mb96\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDUu5GZxz+0AAJ8qECb5cmCQt/Mu1CWH4GXZEGU68ZsQQIhAJyIzzTqfWbnh8LvO5i1UsFjJ4qt2Z9pz88vSH/Rh26W"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-49_1568393956491_0.3648065566145742"},"_hasShrinkwrap":false},"1.0.0-50":{"name":"serverless-azure-functions","version":"1.0.0-50","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"084b4c1d9ef958ffda4a0f4a9e100a51b10c0906","_id":"serverless-azure-functions@1.0.0-50","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-wjdrkPBxsQOYp2zR3Xg8RpSvYSLDi4U7+MhOYxSW1MbLZCihsTTJnLr2A4qet2Y8GFEK00XXjXTMbKbp8voVBg==","shasum":"75b65ba0fe8428ec9f98409f2b31452c7c77cfe0","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0-50.tgz","fileCount":108,"unpackedSize":481466,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJde/N8CRA9TVsSAnZWagAAHf4P/i3gLZw9R9SYJ3BmK240\nPp+eolXa+VLOri5cWsMJQcRxUY2kA+zy+5OcqIhu+s2XvH8KM3r+wbrq4TDW\n87AiqRYVGbfXXPtW0TBcZHTRX6uDpjAiy0nrb4tmjmzto+IsN1PH1QHRhNUU\nHDfXFayrPO7+2lT2HcNY63gypIl3Aplb3NIDEYoLj6GL3tEr/vSYrg8ErcD/\nxuJrgab+vItuReFN7p8Uc/YbjsWX3sL3MYAKcNXnqhBm5j1kiZ0hnZM0jBEt\n9IazetpcMkN+vfq+MYK2MX1VM0CY9Cs8ZDMDRz7ftdVuNDRXSpi3VU5X64j1\nIgkcFFGmhU7/xN96FjOKpIRbwcDaKtoNDQ/qC7OwJwX8N0aDToz2QHVtASgR\nN5d98RN+tSSsFAK41xbBu5FgnQZ4bTufLrpm+ZUhNUAlNDQ5PImISTdQpj52\nPFnLyJNUofqnjDm6k4eQyF06D8pXT7elh/WFKeXBIT0iemH8R75RCIPI0GNH\nJcHVPT2FgMXX683/7/EEqdAgT24ehzzp6WwDGLBqowcjm7Ig+uMB38eZzi8o\nFKPGaZv62UUiuSuzrwIo4nm9+tLdAcxSv+IXVXqD6aIan1oacaR9iN+Mhkad\nwnIe+M/qkja+iNWFAUue07RclsjsJunCU0Q3dMsJT04c2iDv7G+2H4yL2Xua\nh5tJ\r\n=w+5v\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIAo6R+RfuTm3v+lh0rdVIGlr1V/R0WaaFGklvEYt3A/UAiAutpSpjRQkgZdNGpa1o9PoMu6/zEpugfJEgAPztpUzuA=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0-50_1568404347498_0.7383193926358749"},"_hasShrinkwrap":false},"1.0.0":{"name":"serverless-azure-functions","version":"1.0.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"9c57fa8c4cce853882560c79839082a2ca9dbba5","_id":"serverless-azure-functions@1.0.0","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-FokyzkR+/Ue9h+lpvn7C/yzTs4vyN3Ny9x4DCm7lMUyKaaQqvqrYPlFb7Qt2xNnGEXX52lcWYEGZSAGPETbBEg==","shasum":"83c06115d6e8532923f028112a50be357e61034f","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.0.tgz","fileCount":108,"unpackedSize":481463,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdfAdwCRA9TVsSAnZWagAASWsP/Aymoe4RFxLGp93DTrPW\n7bI9RrCDm8ilKcnMa33sSfSP47tnWPSxCW6ZYc0OrQbPNf9y/OKRoSb0q4VG\ninKJBick1LcA4ajyCwt0cZtrfomalEjYLPWhgKUKb8j8Yik2qF+mYp/tmk46\nyeOC0dWDjQX9+ONfS0PboZmkSA2GB18Lj/Ayt6gjm0BayImPLw2n1EcQmEC7\nHmQ6NcRO25zOKi3rq7qNaFONa5sp8OtXxEPmZrU5UFc+Lrnx3VEJGQks2G+3\nSkVkn2XgaZCKG51nG8ZwP9jsdO+2iKpMa+EMgeLKWXKdTQx+Mz1yaAsmzJhH\nI33AgDQ23IMyKupeknkAJkBoW7uaNaAy27QNbLVsrA/+ydu0PI2GXA3DGAcs\nhBqi/HPvnBNYNYIWSUkWub8KIRxJa/FkQ2gM+8YJANidP6HX+6zipmM8Cx2+\nKrFqaH6yHXiUBPP1ehbt/PK1y8W4nIJmTmShS3ACdZzZqrFtW5k5J8s/MUYD\nzyQHHFZ8VAXw8bqK7xh+Rbygy8Q0mv3oUYE5nsDI5m9URvKnmA0Hhvez5glG\noqlauE5uJKe1NG9qi3zPdjGqmJakGVCJVfhz1JtUsShQ2+QkiRQqMDWUoKkW\ndH2xpsPg6n02YPAhapAnt/0c5e/p6y2vrMmYWQN5F5or9hvZhO8f7YIz8dKr\nQ5qP\r\n=42S8\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCafK0VS/DLOVQ/2WBdTsfk0VFBztFdyE2XsCVUKXTtQwIhAIChaSshiweRx8FanIOk7294ngIaaMADimMUcPisoh2g"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.0_1568409455530_0.29952196019445076"},"_hasShrinkwrap":false},"1.0.2-0":{"name":"serverless-azure-functions","version":"1.0.2-0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"89d7701d93d9d373d8bfa5275e756fff3c09145c","_id":"serverless-azure-functions@1.0.2-0","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-Y1Zh1h28n07AnWYufMRxP4XtyLAxxr++PwCDFPo6Ubai6WK22GejRsoq8zCfKhsPGwTWpSkIZj0UhOT19/gJ9A==","shasum":"7000c85f0e6fb1a795340e385a03a2d8b26f3259","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-0.tgz","fileCount":110,"unpackedSize":485472,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdiTu9CRA9TVsSAnZWagAAiwAP/A1mbqk/Pg7Y8LOf4VvQ\niGRxFcT9rkBuc+HfNcsfqcGXEupX5gczI+lyKt7v/ZsjHyRP/v/oMheeueuO\nJ4KV1udXGbzuxE/Zzq9C79fh9qqdF6xYW8k6JAU7ijCugQGDMfoT5DbFT+IV\nAlb3ZSKWxm5VrVpBkr2JwfFciHV9hXMdlxj3OeVki9BRfikXNe1OcUeb2ZPH\nsu+lKfVpS0A2pFgRZgHbgXJEAtvcopnG5hl3ABfpuGrRCC+GMQK0W6wsCsO2\nyUik2u6C7aDHVGx+6VbLvYj458HGTPlzbWN+xnkQ71eiqKUKTPfAx/XISaDM\n1zYZnV8VP6ULIUfc99xwFc38kVIKJ8/Lmtong9DSht4YYGxvmQLPibHN9bVh\nKaqfnxnwLP9Odlqvo2erllEafj3sWw8dykg2V2nU4qDP6CiP5Z+QCDEq6oOB\nKwgIMV4CX15yH0bzqj4Ib7fI4nnaFonMmk5IWJ11ZKOP0hoIPxUWs34zuJXj\n6lyOtsL818GRVcLfkI7G2OOKOxAiLtWITSzAaNmdQ9ArI8ISCTgGtzMCw3mz\nfdgfw8gUs+IzAvns8EcoK4uZzxglEUMcgG7L7qhijVMsUHLaX4UwCojQyhk3\nt9Rag/sL2VfExYbnPoEkP6hWBZkw0VrFbzslJR/9IfuFukm3Mkx8jrU4azi0\njOt5\r\n=Ajv2\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCpkbomQj0yN1BoPzyfEuM+FEkKigzRoW4+c/EascRsoQIhAK+U7bavupeJLhdutQ5Dwx/Kd6f+fSZW0GBi2B8BAhr6"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-0_1569274812669_0.8033164855507151"},"_hasShrinkwrap":false},"1.0.2-1":{"name":"serverless-azure-functions","version":"1.0.2-1","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"970c7f89c614ce6c0b9c64b54d361738aa7f4d6a","_id":"serverless-azure-functions@1.0.2-1","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-HkI36koCzexmXtrGHKesx0MZin/PjKsi9/kjvNdYt89w3DnzbS6Th2c1I2Eys83d30iOJ6vVC4SgXXodrIekLA==","shasum":"f0e9b688101354df81abd7870b1e9422814af4ad","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-1.tgz","fileCount":110,"unpackedSize":487391,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdi5kZCRA9TVsSAnZWagAAGGMP/jM34TCkvRKPmBqT6BGP\nJcx3GhsCLrDPnxrv/nCGn9Vr1XkiwMlRCovuKz/PAWs8HUHABRe1MgMpcrfB\nlWi1vtUXX9CnmIeK6fxvoyybYT5GsGNUHhYezXtdqcu6bBaQ1Rw525PkZnXj\naHF4pksmI52VpnFunXZAk0d+I3gRgTzPuIQVGzYplnxLZ+r06hTfhc4gS9qY\nijgoYhi7Bnrc/yMhgTTjL5Wr6UZsYLWxXyR2MouY6W4SXEv3riMrYayGu8lm\nqzcmF7HQgh1PK+0fy1iLhJcdW9WnDkf5YJVtmnnVSV5391Ti91giPUIvOk9j\nSM9C4x1t+lKhv6gxEbjmvkGssBbZyf1LlueJfj4XogHX3ASmvrqoqrkLZJir\n94PYdr120iRD1Vx2DVdutmJvmzCeOzAWzL1z525DL5upzt5ZwNfMB+vH7TCK\ncNhJE70P55HCNqiaEN3X2TWg770CkLw06au8Gi77XuDwV3mIxLzATC/kuHcA\nut/3z5EFTRfCwgdkTW98u/1t5GqIh30gpPl4G7o8cO+NjGxaRkf3/4bvwG5t\nt7CVKDIcPkGDW80sME94SgyCiD/72uhC457/XLwzHpIeXc+iCCpWhSpby0yo\nsfvv6MEPEwRIO1k2h0tZsN2+xW11Xr6R7Zw2UUXOH0E4Dd0lILgNQ4zdXyXL\nUIU6\r\n=GJqa\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGr4cizKDMFi7QMMOPK08lPo+fuwEXd7wECKc/byxNUMAiEA8NKHaVTqtrNYd/1wub2agO0xCTlYcMUJBZ7/4dEkEAI="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-1_1569429785103_0.6165557285248036"},"_hasShrinkwrap":false},"1.0.2-2":{"name":"serverless-azure-functions","version":"1.0.2-2","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"a769e4614133a646c8e104d637de99fdb4b63178","_id":"serverless-azure-functions@1.0.2-2","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-Q3TosWQtdZ6FbcSE5MebSvXoYxSiu+iuJRKfbPQ4rGb3/2ikmyeECrXU17wvB7T4GTaaIQ9gcUt9qC070i9oXg==","shasum":"d490f72a4d768d9d2c08af43aa9a9102242763e3","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-2.tgz","fileCount":110,"unpackedSize":487391,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdjUCRCRA9TVsSAnZWagAATaoQAJ1OAEIT1TIhqHkyoON4\naM/H2AjStfUvvKyjCSPt07hunJMj/ixi5d2W0sayT5DdyVa8Ru7zLosAMpld\nMATJfdcGfph9s9hVrjf75I4VL3AEAKQByDk/ikKGQnaGEmwPxvSO6GLJ/VAH\nk+oDm7/pTro7lFqm9XX5NOoRLvFckP1n17qNRScAuaDiNneeLCs/3Oq4y/hU\nLNqencyl6is7QGn2th1P6OXTYQZ9DNWaYlB8p97JiK2I3VRZhq6S+nX8FnCo\nT0thIv1HnNwiRYw3/601V1XC7GVE9Dorq6Bf3wicKWJBwAsBC7qxzUxDAoVx\nEAb++LGGeBCnl/4zORGZrYDEcOUXWKnfAPorhs4KgbBswquseMHHVVqqYgfT\nnIMFME/Ovow+X5GJM5dReWNFx3Nt0HNWc3CWzD8Cy3xvxSKKQ8RUZAoDvwZs\nWfm21ISWf795FjIE75hIogtmpaKVO/JlZ8lza586cg1LPkuuDo68wrJb+yyw\nmM4hUETBjidTm75G2pRHjBt30cRFe1xHxSSRNEGDhGeD7fCxk71eZqsxazZi\n9Xar5781KU4FT8q4mFTcNo4D5wtFvXEgETIzxKTpN7MQQZTYjy/agwwNYBjy\nUIEyVuojR05/o/EewPbZMp/l2FicauYqIpCWIooQiPkqst/i7bqjJt/yZoPX\n1btG\r\n=hUqS\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFMyWa3s2/aAsIcWSzR+MnUiENu96fyDegza8S7I9sA5AiEAtGSTYIihRt/DBJrl2YHBuHiYuAUyZaNwm5jJV8Gqnks="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-2_1569538192486_0.8810741405357176"},"_hasShrinkwrap":false},"1.0.2-3":{"name":"serverless-azure-functions","version":"1.0.2-3","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"8bf704b6d2662898e812b72dcd66ad4f3cfae30e","_id":"serverless-azure-functions@1.0.2-3","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-L/Fz+Nidlw5VOhOusRhwvBHQecqswP7VEVKyD3YRSbhIEm1eQgByMHym27Ekr0nAwNZTVw/FlyyQKt00mam2Sw==","shasum":"4b09188d442f786022221c87360fd900da05fbec","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-3.tgz","fileCount":110,"unpackedSize":487391,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdjiw3CRA9TVsSAnZWagAAHu0P/iENTWQPkppYQnwrWWCf\nRKw96FrPQB0VLpTk00MVBZo8lyZEsD6vAhq5XJg2Qt53j4QxqcJJ4erqQMc2\n0rzZXZjSTk/KG++UTNN+yuM2QW6EmudtJ77hyPVhy0p4i4fmMERdYWhGErO+\npudgu1DNSUhexbZyfhXTO5OZi6zJ8jyz7yyXCWJMC2zlQmqaFV0luZ3diRYL\n5YOigtIuKFW6pCUol0YmGoaAhnl+bmawZ8iITECUbv0fIVYYVetjy5477IpS\nBG5NnsprWdWpNqS8l0NOrBXjt9046SGGH+BOI6MIpCIiWEvHvMXqlRjO0Ebs\nn20pkSisLTf3uhl9q1JXMQOGwlYLJLaG4Dlgd1PlEGshmcxDOatR0xEdZjid\nNRFO6M3SUuFPbhJxwUWtIitJqII7jXGmg3B1QuAErwFXty5fpuaybvY5Yp3V\n6B35XlPoHE5x0iJaCCh+1/2OYjvZpSRsdgzAXby1Ih9J1EQXt54S92AlAGTl\naSHvAAJvCjBnoEB1gsimP//jvVs4BBUwXb6A/yb6ee57JDTBBuX4UqNRdjKK\nOQ2sUDRVlZtu5iuzKh3DSCjEt48iZQjvVSDkMlJxVnsvuNo/JiDu2i5riYNf\nwEDfxwH1a8hbVSe9s98u6z4361nZHKoT3B6/56nBpofkajGKuRLrAjGRsxoY\nkOHE\r\n=aDwH\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC0mWYxEMzO6a8A+Is13YIEDRyOS8nrGdOrnFaAilJCEQIhANrysP9/gmIshP8OYgruqR2Zyfa6EHjIkgsL2WsAwOMa"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-3_1569598518993_0.19973021662773904"},"_hasShrinkwrap":false},"1.0.2-4":{"name":"serverless-azure-functions","version":"1.0.2-4","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"7ae087db0bc2bd145400bad917490e90db1f6de5","_id":"serverless-azure-functions@1.0.2-4","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-L84ea4Ze3cs3+XesuGoL8VEi0wXwLuXfV3uFKdKSKPxKarDwvNxm0lthYAuGrd+CXF0O/evYFepOAOLbklnyJg==","shasum":"a96dca44f06c0e692fcf186cb8610629c25f4d9a","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-4.tgz","fileCount":110,"unpackedSize":487444,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdkh0ECRA9TVsSAnZWagAAQj4P/3W7qPeOoiIMLUX94228\nzOqSOPc++eWuj2FDWzXDsObikBIrb+KlaP+rZ/jYqudUzVpXarDpnrgTNY53\nIjlEGdP8o+9qJ737VfQUmbs3I70i0XicagnwS6Jv3In28wgDopPjmyr7iU0l\n2tP8aR/YAJWILVS0qxY7OmRrezUwzIn32TrDJJcQ7eo1UnoaVGzl/2INpL0i\n845AGbsKGX8ydPWZG4TyV17G/B968Ehhu2rBLnbIXYLXD4CIA6UNzeS7Jib6\nxYqmPfk32LZ/pAXZLTuwVzFALCncwwZtRdF07uY89SjH/2FIFKfYij9N4IeI\n/0Hf9WBEBehGf0ODWZk23lR8IGAY1sMcE199zN5P3XCeqL0W+5Zc5XCaVP/G\n6OgjPZE82+rvlNPqvkFWVWP+upiPiE+8W3EDj6RTOURaFUxNX2rTkxFKz+6E\nSr1LEHuUmrN9Vc537oSHxJmut4dSChphPNDZCfVoimlNNJm3A7DhiuOw693L\noNoBhZhypPq7JRrWdGRrasRPZAdomr9e+7/SCJQNwjYjrQ52VacMp8/tuZaD\nRix7UwdVc0fQA4M8oaVPAA0+QlQkeFUiivGCpfjX4gPl8lajP+ykvLjjlEyY\n9rOEkfdesCKamw5PsP7FzXej0dEOlGeDl7qOuHfT0IriWuLwo6t747dsW2pS\nnxRa\r\n=m58e\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQClCpJv4QtOhkUSq8/LCGTpqwu+jvMiNwnrugITXPNt0AIhALWR6D7oNfdAS8nJc0eo+qEdk3Hslr62NQ0H5eZodQI+"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-4_1569856771730_0.6672629889233512"},"_hasShrinkwrap":false},"1.0.2-5":{"name":"serverless-azure-functions","version":"1.0.2-5","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"90bfc163ba8440d128890bc016f8a84f27b19b99","_id":"serverless-azure-functions@1.0.2-5","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-j6OpI6QCS945nZuC8l0ojTygCc071BypGYefDAvE/Ss7PsH36m6g7Xw2LhVSn3rGKzQfvnk2FFsqxFx+MY6Auw==","shasum":"de59eabaf7a285a807574c7aa5b1fb0ca40cd618","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-5.tgz","fileCount":110,"unpackedSize":487864,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdlTltCRA9TVsSAnZWagAAcQcP/A1QiiH1BsiSdZqZVyCN\n4TpdwjvqTTNb08TA4Q8Kwf4mSlGbfYdmEPUgXb9K5J/Y+a9o5XMG6RC1rh1v\n6BLKS3lbUu1QtfvIXvwrFlB5CclU88n8P77YzW9NtqaN6a4pJszON1llYrVg\nJvNZOJimF2eGQGsUZF1hDT5cml4LchJs1tQeCL5KECDOuDBJA+P2f0Mfx9ya\nzAQUm/wY+5hq1ZqoLCvELo2Qf2JhYxPcpPfvVFwZZxInWXEeRngynG706YXP\n+QFAuiFslTOZslVqGffbV4Trwt2xxiSReWG04xdowbsFvMAQ+luGe99geaRd\n2BUruT3DtNiKxRVZz3TXDM2oQWr6BIfUxz341n3d/gVshOfQtdvm4+Cqc/e+\nKKSxRs2S4YQzZ1pvNpGzm/KQbzm3lV4+uuco7vNv6laWINH0DSB8n1heQhH1\nS4Cgb6VQmVyVR+vl6dXxj5vgRANxWby3DAiyafnsYuIjrzkjWbkDNoQrXrC1\n8kpjwjByUo5zT6NGb3VTdpIMHRYeIr4+EkWv3jB2s/mkZd2kCji58pGEvufz\nZ7LrD72zf2QksTznqDt8Vewu8z+lNY0/H16VuCexymA1Zh+Dp9VbIvknFRD5\nD1tGYBaxEu+X6ud4zkAUaFjM/MLW7B8mF9qZp2p/pQ210jmmvwRPqBzd7El4\nxsU5\r\n=YDM/\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCsraCsAOQiOF3/3PdAReqj3MDMq6Eu725EbzfkvY0r2gIgDdqTVaAP4QfcdGefAIkUEbCl8HfSl8Uh/VY0SvrwTvo="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-5_1570060652713_0.2571709393293191"},"_hasShrinkwrap":false},"1.0.2-6":{"name":"serverless-azure-functions","version":"1.0.2-6","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"9a6f0008c758134b4eb0094b8703022297bd2059","_id":"serverless-azure-functions@1.0.2-6","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-jDHY+tvOn0nKQPgyZaq5Pv6iDbS+Gl6TLcZ2bQ2n1j6qGFJodL97p8qLmbZBex3kqtS/GWbnkJ5xF4fL49Z+XA==","shasum":"b21a81fadea3a3e7289a3e37f157718a6d986e6c","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-6.tgz","fileCount":110,"unpackedSize":488448,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdljCVCRA9TVsSAnZWagAAcIwQAKTaW/y1UJ4Mv2byD6AO\ng7J4+mlvr/7+YmynkEnaFOO4+q3kI2/uJbMggsTynlsFjWDFzvKRphJUWbfT\nu/XOOfgp1/FoxKSNRdz/5ZLiSrSXeXvnTeo0/YCoXQP7n9vFEvzAd2y7P06T\n6ClxL8mHByReGSk+zZkwlrnDJvP8n19QJ9S6AQW8VhvrnuPHRJ2MOzXBhBFf\nwD/t7pevq0orKHlMPMldic8/9yqKAqlVfiYmEzjXjp9/XOEl9DyteKbh843l\nbzMr2SOPtPkCjrxYX9+4J42fQEPUnGJtHqglKHbbdT4qWjUiv/jVL1CZ0iTS\nWJLMd0c68lsVhUi1cLakIGrN6EGrhAy43xByev3vvVYMv5QHl3g9CZshHwN6\nHWdfOrY4TOsCtw1dE3YbwQZIM50uh/H5yDa/0WSASLg+8+GOLD2A8M8qtz1c\nOAk5lLeZQh9su+6DHdfIO9nGjVOAHyBStdWCJJjYn959b7nzfOsX2aPLrZYG\naPjbow3YDb0VeykG5An1tMSFHQ5YwDZtjAcWsn/82ajtY7OsOB7lRf1OhQoU\nrPpbcz/cQyaW2Chn9RxjYcnCnsdx4DuJ13Hsgvay8mJ++iJrPhLY0zpjjh0r\nEVVxIJVGr9/XOmamQcXaMPB44eSBjZKCBI8BrbF+ef9zFLtehpkym6Qgv1yS\nN5bV\r\n=Pg9G\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEcm7XXbEh4YqP/7Y15sDKpBWG/4VdHPtZ37QV0ol/PZAiB41QN8uypzZF/kf8dm/7YiklIDkWrThpX78k0C55S7qw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-6_1570123924547_0.0316897661234834"},"_hasShrinkwrap":false},"1.0.2-7":{"name":"serverless-azure-functions","version":"1.0.2-7","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"118eb9175bf92e103de556ab0d2ff8f9cfa95805","_id":"serverless-azure-functions@1.0.2-7","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-tPNqAMwy3zre8dbrRkX6ml4dxi57KW5ghFnREJyGOujXuoo9qV4Cyc+eZnO4HcFHZRnc20QkWM+dkSZIrSjwWA==","shasum":"04356caa422930ca752cc8b2988306e12e3223d6","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-7.tgz","fileCount":110,"unpackedSize":488448,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdljC7CRA9TVsSAnZWagAAZxAQAKPxhQybWc3ZikJErn+x\nhzMvTZNgD8BoeuZfOMMu8QOJ/KKC9bs6FBN4oxEwKdBBLfrL/hn5EsX/B3P8\nLS1jV/Ku7DurAdkTFTCLwCsaebX1BxRMXlN237Q5ImVZy16rhNt/o6WM6+Sm\ny1lycjKND4PGAvS+/q9QjFOhXsxN4qWpieNaeKvwIfXCWsMXxqOhASdBegqp\noSRxb0ZixvEerS6r5bCG0Rd0GTp/KM+7nsNxyZvUFc/qK9pLAm3MXcL4tRLb\nS1Ym3GFzLbXxbqPYtNn//9DqjKXXsHPX3PWfhY2g+LWrEry6Fmt1HKhAKVrp\nV8tJHcbcWX/DT0fgipmSu3oAGqf4B3Myu1EuMijq04fwgkksfkiFV7MKj0hZ\nUpV8BlcgWiHj7ly0I/CV+P6zyjKDeiwpaNspT+BblWWZJXfsHzWmodZDrAjS\nNC4M0d5zrWLKWGapy4wbjpmurz0nHHUikN4b7GuEX93xECAyACumvKBeaZdt\n9slvrNhmmVHe6HDviJR02id4T5zdmyOfpa/eXE9x6LaxvDOqUPJwK8gOTDoI\nv8vX2TjY/PN5b6HyCR+/NK94zNW48a13KSpJDlkFOp9N6BQHxPPJE8n4eaRR\nPuT/plc5uEKFOccnIrSoW5xH+c0s1Dd0gqpIkDh9fktIh7P2JvRggYxiTWgO\n6Vzv\r\n=Kx8n\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIE3f+UAaekEX8wOTp1JkA+N4EdUjYQtiBcO2q/6vbMYcAiBdrivxOXjotxVWzc8wTH5yJ8nWiLlq2jUETHfV/ZdUHA=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-7_1570123962532_0.060281658523341664"},"_hasShrinkwrap":false},"1.0.2-8":{"name":"serverless-azure-functions","version":"1.0.2-8","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"673008b6cc74f67834cac46a1bdc7e756356b6b9","_id":"serverless-azure-functions@1.0.2-8","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-ysSgieH+whRH9EDMaNWknF5cJejqP4cByOGhJI8EU5ZWxHFeH3tl13SOwhPP+9XO+jqZKLl3CUwdNVvdZjFbfA==","shasum":"436c09b2c61eec8b26e84bdde9a402a5f26c8377","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-8.tgz","fileCount":110,"unpackedSize":488451,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdljYLCRA9TVsSAnZWagAA0FMQAIhGx1hjmdzGJPv7E8ap\nALlcjZkruZI+GiXL7mxJBYsG0xBGuc9Fz6mKQW7QHmQJGCEIJhOwL7vxqGwh\nNo2yGjpLsSzhh5sa04rigi9TqfyWCX3KhoX9E6FRJhC7QT0i/Fjy9w56mp3M\nRsmrJIFafoqp95l9fD28mfAudoNet3Ezfv1fV74egxl1dqQiJDOkUfUtFXA+\n0Prswzl54753PWk27YkRuvKm/R2D1kdZ0hn8dAaZweux9aMqVakB+Ouc/bMW\nd3EmqqhQ48hzehw8wR+6IuAKtFiXR10ETJBEwJ0PkvB28oGkXFegeWANeV2A\n0/NYQQvFqq9JrKs2akAomNr2JhUHRbGuinPC0UGl8FER1Sfbn24ZIfAb8Pze\nFmvHYtenhDzHxYfUyR8xT0asVOu/XlLQOU8Rk3wdllFDhtA6WNyRmuIQqQAI\nbW6RH+IWnhNQu5fhKe49qphX4Plo/FviEU3iLdQ3IleIoocXKN3l2gOYfJQt\nUlTDhTEH8dHKujIhhR97aaCmx6QiapOT5AX4tZ5r4eVKs0iraqQPwzcH711G\n5fc3DdffHxLf+o793A0dlDatHH1b4j5v/6vNikcCf/Rl36fi1z9F8eomtY72\n4nJJqbbzz+nLZ7muhTODmAnvt1AOs/CCXNYFFIj4+M+4R4rJ+HWZJi0RQQlm\nDDNi\r\n=YI6H\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIG1dct5ajdGy6ESgn8szKdBwlZflFL6INh2mFO/wHKwRAiEA7seIqEVA0ffsliU0VCUqQsJKDOcx90ibGNdU659MmBU="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-8_1570125323224_0.484512016621262"},"_hasShrinkwrap":false},"1.0.2":{"name":"serverless-azure-functions","version":"1.0.2","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"af47ecd077605c2ee8ca4f937c4426f6515af70e","_id":"serverless-azure-functions@1.0.2","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-Rz8ijMZed9xjyDMzVlm9PzFdZwwjPQbzJGUwsRVGL2XGz6ARgyTXr5QwoPNUYX28r1ZHy0RlOXFEjXdG/WwL4g==","shasum":"53dd8f080c46fcebeb51e141c86dc2c0986eb834","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2.tgz","fileCount":110,"unpackedSize":488449,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdmy2PCRA9TVsSAnZWagAA3w0P/2nW0ZMxQ08Xj/gsJ8Y0\no+Mhalpi4199ybC7T9tWNC01EpFUVL/sujidp6wIXj2O7Zqmc3iQ9ukcJen4\nfpyIOwcqkOzi8tBqLbujMRfbzVaepbu2/eU+zMUxTBvV/PDMfmyk7q6HFMdL\nYE1TjkYFmrFn5UWFAVs9ByRUqHffhFf0HUeN87YvDuiSFhjwMRGWHI9topRq\n47bvH+zUryq/tEjxOylXt4FT4pjOxeYTfroqRwxMIDyTGSaAG60L6Z2a5fP7\n8Gi2w1cZp28uV4Of4NcSDmCQX02G/5Y/YCX38gjzXp+bOXbzNKKhSgmtP/Md\nJyHpXqOWbiPnUwpR81zLeV9QyRhV+m6zuRsxO4FwxAKavnVT1dws5BAkBu7p\nLxlZsZvIAUrk0gUKPESkdxwyyWWdpaPCxPIgEpsSfNZd3uMgAlmfMwcML94n\nlQ7PxONonovfT/GcUZ48TtYrJJ/6FUm2h/G/p/YnUBvfVOJVSZXdRZyObWCU\nJYg1lIZlxalxuuLI7bqSetkDR48wS7dcik3rJdKsHQ1gJ4K6uqbp+c5+WrQi\n8asJuLyWeqjNOgEZY0sWuGt1erkCjtTgqEpS4lTogqTk/12PLZ7X1wuWsugc\nnjA7mWT5uMAj1d7H4ZKTDPJdKOiSec7mBtPn8lvZrrj6qYzC786oLvBD+ThA\nmgi5\r\n=LVaD\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCID5gJgP0Zhwwk6kKR1UJ9G/h/e1MBMTel+jFhr4++ESiAiEAhTVrk+45Ox1xuSafy/+gHJN9Qi5xSjf7uJ5UCn2v+6A="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2_1570450830596_0.4240473092672872"},"_hasShrinkwrap":false},"1.0.2-9":{"name":"serverless-azure-functions","version":"1.0.2-9","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml":"^1.0.1","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"4f396811d6e0759221b74fcdfa4d4d6aae60ca8d","_id":"serverless-azure-functions@1.0.2-9","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-YyxUQPGln8+2RRneI7U9tQ/ueJBxP87dynBUi/Pwd/2xQyaLW+qq3L1B4mdNjIsqJ/ZKocfVBl43QybkyosCEg==","shasum":"64a82bcb18b9f4cad84983f4a6bf13925db3faf0","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-9.tgz","fileCount":110,"unpackedSize":489999,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdoOtXCRA9TVsSAnZWagAA9SkP+gKsrxKtpp1rgKvl7VUa\nO7P/JiCwDUcM/jCIcXGdyqFtfmkRPSmIR4Yu/jYRgOeo71oW67svNceb2Clq\n05CpHxa9FpwenH3azAecASSp+uSRaI42WRenUNYJDKSBv1a6jqZLztzdqSk4\nUT8sIvquvFC7JR15i4BDV2e7DM1o/41b0yY55ibPEhBZTm4FA/EEDT5qb4rw\nByIzlGt0zbEAKGKG9C9iL2/t1MWcTJJiXeDutyxBWDPPlA7sRFnY2+59xhce\nbraQ3Qzc2jRt7Il15a/jnFlvmwSdPBdlK+yaJq6kGIpxcLnParpHNh9AnLHH\nUG4rq58wJ67dYYYjN/f7vqb/SL9JcdVzhkDWwS5H4TOwLAf5PK3y2d0tFHrr\nOy6tSLu2ra8IlRHYGi6NJ22dcnmhfDL3WPJZiPyDJjoMF3fkfSuo2I04GFSW\nrTMj4ijK202dFNpjZ31HnROPl/xKmF/fEDaUftnm6mFRyn4zQbfjd3TehLSc\nobP5aNNF+s6a3ehS71pRqMK6QOPKDbhqaRi8lcQ5cZU7pRLD3sc6za/xM+yL\nqzCXfTE7Dst4r3YIviAz/CcVEqi/8NPsqnWW3n1W1DPE2Ubndu7MutqmxKhU\nK9Aet+vfCdVx2xegAQKYNwpY/mbtYZHEI7wK+6Bm+/lF9ibtNBU8oFPkYbpx\nV128\r\n=Pwne\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDQ4M/we0DWtdX4wGMKFY20MuyReSV60du1NXyyQPck6AiEAzA956qqey+69r3AHd8VaqOkMZ5eO13GpAAU5n+zsKrA="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-9_1570827094189_0.5877137907651275"},"_hasShrinkwrap":false},"1.0.2-10":{"name":"serverless-azure-functions","version":"1.0.2-10","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"2269dbf2c500dcb9a30eda9bbed14e33f63be1a4","_id":"serverless-azure-functions@1.0.2-10","_nodeVersion":"10.17.0","_npmVersion":"6.11.3","dist":{"integrity":"sha512-CQvmeP4rwwiHWFHxDIID6WFvFmJNGTHKBToGtWNDijHSREkuKdLqBYcyDxPc4oPq9hS12s7BUXioytdSOmJh+w==","shasum":"731060567fe269974f10ee0811209f6eb95f28bd","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-10.tgz","fileCount":112,"unpackedSize":506176,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJds3cICRA9TVsSAnZWagAALbkP/iLJO/q8AgTe+QoJbIt3\n2byS5uaUqU4xW+HdaAb23G+/+SbmmCYLm1xhzr1zaSL7AVcnnggtqNj2eHmu\nGSQPDs2TTReuG0gSE9XN8TtrKnbaAnorjTe77SfeT02lNoTwOVGAuSckFD6/\n3gaXqaJFUWtoZO0RyTQO6YAv2bwm4fmKoDjf5Wpqa+G02aEClDNiJZhvlNfY\nQSUFcxZNlbZYFCyXAws7cxIaXa/IDaocemXohJSpiuLjgISY3euENLTk4cfS\nVmXbRwJp8+NWl2Sy9BAczRUPOtawTNYs95GKkIW84jG/yDFGsw2+EFPQ9Yy8\nmMhchKl5a0b1Vez3+XUMicdDqnqbmASJsgZxu1yb7DDqq1UrnXx5lbEg5NiP\nZ4WN9+u6I7X3oZsCQkM6KbAela6h7NGFPTAEcUltiXeZwYJznHnDkfWPNQwl\n0OR6zde6GNYqdKIF0fHOn0g7K8koSY4uLkzUH+MqDLMPCuR2gC3QtzUZLWxK\nMSi4eb7BB/W5b25f9/f7Oxa0kAVy8xpXwu8eTB0+995xoJArPb3nj0BMDFZ/\nhZ8mSZxFq+AMjE43c7EyR+Mjxa0ZPZ6UrjuewM/ny0u/rLTunviwmk7DkUIj\n4Eg5asmrV76pudm8mvfc+wy326dExHw66yBnR50al/UF8Ekt/jHNsPMn7SV3\nSR8/\r\n=Ahki\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDW/otmnYGwLXd/wej11H0r/23rSBEghqX1nVBqfWdPhgIgUIwjkJnmHY4DnxSPSsYQQxMgpxrmRcK5zIAjAob76hY="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-10_1572042503920_0.32896518087217475"},"_hasShrinkwrap":false},"1.0.2-11":{"name":"serverless-azure-functions","version":"1.0.2-11","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"a1d45f0c8e4f992e3ab0d30799a4e6df7f59168c","_id":"serverless-azure-functions@1.0.2-11","_nodeVersion":"10.17.0","_npmVersion":"6.11.3","dist":{"integrity":"sha512-IWhwCC5W12NI53o8syHSgDHbQDCIsdLKxcJeRDgHIR7bQLkES27e4EXiIUqONTQLjOMFnXQRt787bk8CPGED/g==","shasum":"cc41d1a4cca17c77b632ab6087412137e818bcd9","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-11.tgz","fileCount":112,"unpackedSize":507674,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJds3cpCRA9TVsSAnZWagAArLgP/i+t07olb2NWQPj7yfN1\nEkijPelD7e9VSylN6kRJ95Dk5FXe1WTDbt7qJAy/xQKUwcyQ6l2qQ+3t2oPb\n7LdxUwI20jMAndWlZUMJGc6PDfp0W1UiPV7Zgmks+NHkYNQl9RP9g3rWVeza\ngNiOJ/agMcXJOZNkSE7w1rlYHXwEOg0ZgJxR+Ao0FUMSHun7A5t9CWljV4+E\nhCXaRSfkRCJmv4SiujjdeEUQ3bTfYBKrF9puG64EthFQ0it6ocRmolRYobOB\n8JQ3utDazJCdCJYsa7bi/IH3box09irr8gGmQxxo0ke3wticYjtWyZrrorv9\nZ/dk3vNeEkZhpOIxoZf2OfBNvIa0Wu8s5LrOVG59Iu7VFzmGX4reFcZRSGDS\nwoFZGsRzUdPvMAT8JAgeO9EsMzwDhWkaJizMJJ4tY5qAzop1SME7yluH5esp\ndxvILIdnMzIHumXxS6Qx29ujM1D+Dtyq659haZhaG7vtbOpauB9AjTxwwSL6\ndW6NqU2kvVbU32cGir2qQ1LLSi5tgtLCb6TOuR7P63WtfNzRt7WlSHHpKUaX\n8BFx41lle3nf5bMUI2t3c67C7JVEwoL/QFIXo6C6kY8EoMhzjK9Oc0jp2Sok\nFKg8lYdy/qszVSe0DIjZ4bNjMYAsOqmGOZJO7qwUwPxrT3Z5xRHVlsPLj2DE\nHbAl\r\n=rtCM\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFbBAmz9sAbN7/M6E5Js9qlzfVACfivrjqWAibIxhJENAiApamkTpXNY6c4WFne5pdzpCd0g0mks8qvoYGEOXmUSpw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-11_1572042536870_0.3811994670414509"},"_hasShrinkwrap":false},"1.0.2-12":{"name":"serverless-azure-functions","version":"1.0.2-12","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"832e3b9053d6b65976aa53ad2cbb8111f97c2ff1","_id":"serverless-azure-functions@1.0.2-12","_nodeVersion":"10.17.0","_npmVersion":"6.11.3","dist":{"integrity":"sha512-i9ngcTa/B7EWIJgxD9lUg3Up49Fqfz3a5n0J/ABVm1404FQkOliLujCNaEw9+ZNTaup4JstjafpLtZPtSXtS1Q==","shasum":"14f8431baf5301f2a525bac8c001d5548380f038","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-12.tgz","fileCount":112,"unpackedSize":541458,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJds4M9CRA9TVsSAnZWagAAI90QAKPjaPR8lO+vUDMaabqx\nfMgHJunxSOFM8H/ShIgvQrD34RzaSTgJl/bcGlMn7PGy+hKvtT48oHZXH4Mc\nmAMWLqHOvf8WAF8niO+ywY/fUF/srwST0FODyzCfx23Uz7sMEbbxd+09F27d\nMR6SXzrTptj+rjRTq52OPH+pVtBzUcOLi2d2FeuTuXM5Qt9TjuDTTaUNk0P0\nxD5Se68JAQ5BEc2iLuMDHHtJZuuG/H0m6GapbE0MxV8PfpLit1shrbaAltGN\nC0trfnVeTEhYyY8wwp51wZanTnvKc64pHjpMrzchZBM7XPlMlRdceXuvI3Xx\nj8WhMXuMrIFx8o/atKOvtD++1HKCqDQ6nSb19LPx2FHBBeWVlwZRl7bsLyZX\nZ0bhOCO5L8MK/HCBXGAs7SvKCnfAIMbPiMAvPHrMNO3/fEGWS35t68K+uBIX\nCzMBEYc4YtaJyAiPZeWyjNZP5GCM30wI17l5dbnH7EPhqTfgxLAz8GXvizh5\n+CmVELsXkjBX6uskIOqWPKBtmDLfRpEpcphzzQZyMTIprwPoL0iMdXX/JpA0\n7bK3eyCai3Zxl+7k0Q8qW6DlRfkwvYuSHRAj5mm5T64p3cCk65tDgCZ5etuE\n4XNpwu04rE8/vr7lqXcoi0l8z5rhgYQI71wU6QMWMdhrKCfP/mBDliEIBR2E\n1NVK\r\n=hRUB\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDgN6HP7TcQ8hvS/CHwnQczn4X5l8LVr26gZe/Mc76i8AiEAo/WHdWvNnIS1MuFM5WNNi8c2T4yDjANH0boM//rJ0Nw="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-12_1572045629051_0.9224858350442258"},"_hasShrinkwrap":false},"1.0.2-13":{"name":"serverless-azure-functions","version":"1.0.2-13","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"b106800b15c4d9bfb814e42e75e3706581835aa0","_id":"serverless-azure-functions@1.0.2-13","_nodeVersion":"10.17.0","_npmVersion":"6.11.3","dist":{"integrity":"sha512-aysQe0QKdVELPSBLMQ/TjsjAEiciVquDJzMZ3RSo67ZIPJD7l2xxnMTyGCZQ1VDn/tcfs3yWMOXQ//kVaQb+ow==","shasum":"6e338e9bef465567646d3639ccc47578bab27119","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-13.tgz","fileCount":112,"unpackedSize":541900,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJds4NeCRA9TVsSAnZWagAAE2IP/0Phpy77HflNB/UL/DX3\ne4yCop75Ww/aSaL4Unn8tynxvNsThSCEhVusza+ms7lU1woJn5y3P4JKfSU+\ngw/HNPaNVFjptNuvawh9SJ0JnGWfGhlEsnvMsaFoLt4iBjzBt4dZIQx39b8p\nR2PSZ6te4eiyWxJiYdaYTB48ISNHtc23RiDtmI/I4n0CpCX0D7Lgt7aCs0rx\nMrQWuKJ6qH8PjIcef1+13/p7LrBYfLAu1nA/kfNrIaRSqXYDNqk1YAdOSbaR\niYK0KGlNFdPyuhu832rLmM1VeAihvFcspOr6rHe3yDpEJpSOHmdfhU6E3Bf9\n9c3ZO/A4DDx9mSKj0G8lT5DKrbbT7HYgfwqUUTLHPNM8sg7KO9rYoFHGaDCK\nsyWLdyNdIHfIC+5dcTRrJHID0JuRYLMoLhxS6PPv1t6/ofaMi++fkIG0fxcE\n8yjt7BSsVOt4xVfekOhN4rRJ6IqlSvqIX2TfhKLSkRYPJv0NyiOukV6DL89q\nns06RL7onwDLEKZLc/t70lElMFuB1vl/kbCV5l62mijXIzI/K+805atpVsCX\nNVf5o9Ua4aDvMavsg/tOH6U1/AWcL5+NqpHBbA4V1qpRIxp8GdbvZL35Caee\nAhq/8pq+1NAq9cMW+omrrujZC5MJPTwMWK6E0kxKcrZVHg9qsqH1NS41KJ2u\nJuRX\r\n=QO0V\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCICj3Jo4YYNk4lNTx7WvrrKUTzFbOI8o1pSnVn9udZVhlAiEA9RL+lLWa/Hu4XMaTTXQ0UEOTBF7JB4KhErkAFnuh98Q="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-13_1572045661651_0.5694525337264829"},"_hasShrinkwrap":false},"1.0.2-14":{"name":"serverless-azure-functions","version":"1.0.2-14","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"7dd6eef526364aa55c09a735698dbc7b5da6c6ad","_id":"serverless-azure-functions@1.0.2-14","_nodeVersion":"10.17.0","_npmVersion":"6.11.3","dist":{"integrity":"sha512-c32m4pQjE5c/PE16LDgUDNKXJGAMy/gUQhmJVPS4sBwdT25rvQiI41Ffk7PaTVNUL4C/GrSL+D2WcJ2vEWVDqQ==","shasum":"53246e012bf4e340714301e8962381f55d8d953e","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-14.tgz","fileCount":112,"unpackedSize":541900,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJduzItCRA9TVsSAnZWagAAuPwP/0899+T+BH7XnF50aNN0\nsfc3nFRYPeAahU6nNAbLuqJWWMw74DOBYcoffR+FEp7lcemDCye3i/mMC/TP\nHy5N/mM9l0vX+YyWTJRJonmYJFYNEz0DXya7WtQqXdERFK8f2u5V8v9xr19p\nfjP68FpLaRZCpPDsWPkN8zKFbVkKaocki2hqot8ZsB96xbiweStyonku9Eba\nA+TLJPIJzQUToHmyc99QJrsImWMaOodzt3FgzM5avRoH2wsLZhCspF2bHiHg\nE9cTSmoNimF3UGG/RqUbG8WrapqEfI4ETiyOOgiqoBoj/HxRaHYvCZ179Dwo\niIuMu6EOWW1fsXOxfzn8Rb45QDMkBXks1MQSAjz1gX+YHFUZtwVvF5KjuzKR\nz6M4tLaVGCfaDK3wuqCFmaLnhi9+m9x1lbVzOL6Hnfe4CQUXm0446tdBhZOa\nee04VJZWchL4camhUTx/vvZbuB2X0yZDNkh2GqhdOJd2a7vHQQEd7JTTq3Ra\niGP+laUrzU17k2jpT0BmgQbtMbgUUQjegD2jlATuy1g1ZzHQQ1Ki6A9iLDxJ\nT/b0EbXGSIoLx0xFOn/Vxs0AqjGz4qRDUweB7Z/8YUIz0IAAoLwBRgd2JzFp\nWAQIrdVI/JXM7ouZB3erZIbWxAu2qaAmFQgNspzBygp4xc71zVF1zEQm31Uy\nf1CC\r\n=Ofb6\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDD71mh6WqypMO8sq+BozmE5QFxKFtuAfxibU1ObL7IkQIhAPRxAYyuauF7684SVXidlKk3QXr6e3/Vf3/j/LZJZgXT"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-14_1572549164849_0.7667279544852355"},"_hasShrinkwrap":false},"1.0.2-15":{"name":"serverless-azure-functions","version":"1.0.2-15","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"7819eb14da76e54f7f8033875818c8cab3fda6da","_id":"serverless-azure-functions@1.0.2-15","_nodeVersion":"10.17.0","_npmVersion":"6.11.3","dist":{"integrity":"sha512-v0AYbpR2NrfIq92coR/WSsl4A8GOp8A/2iv7Yta9ZMcrud+8ulbqn+hl0iUFGvwuC263DszXrXAvuZTNF6nxzw==","shasum":"44780e8b49365db51d548b6a5cba55fb1279e8b1","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-15.tgz","fileCount":112,"unpackedSize":544366,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdu0rLCRA9TVsSAnZWagAAvucP/jczOXqAqxg6haw5AZxD\n+4//dXv/0tMcJARmiy8zoI3dh9XVqaHRqwpPawfaNbjNB0a07I+q5uPiexBa\nN0OyZ7PfOpCWXVVCFKiVTTmE2f8jiXNGu/9Qa0jWq9Uk0TFNWSq9PtLdcemm\nlQMj348LMk8LhXYZi+bSrObln0N5W7dxFh7vXsbx56sLBkAk5WQTbisviqqf\n5U2lDbwrsxS3O90fouN4cyErBFz54R0UKazk9dVGDux9Q5XukHm2LaQxm9Ox\nXBRHW48Y5DNUMUgxN5E8UEztXI7eZqJ3mTeCu6oxE/vIe7DU1SLI3gkLE0Ag\nhhxCdvHvKRM7a0P+01sXnSKhLtFp6nZQMa8wqeptj6IwtVHrUBsaaoelw/TR\nTejbuE0tKlWOCbbPjbFzUSHAU3+kPY9e7dKIr4sJq81nkwbwNxoVcWP0bXqi\n5pQfM6WQBCYYTtsYg/IsDaLuoc1+faq6V+OvUmYiMgviR62fd850jvCNreZS\nYIm5SdUwIFibTVssvLG33i+qAoqgx7bvA9A2enNziITu3bbXGlQthGLH4cCW\niwhSpZuFNkrw71so4v7C2Bfnaz1vNN9nSYmulZ22+zA8PK+URz6R4sC29ppR\ndXvRoNK7da7tGWP35/ZLsJRjFdi/uQyROFRIAI75fSqmvOT01dxekRJeQP9S\nadRb\r\n=0X3C\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGNiZ+6HkdAIKPn6lgC9L09oY7U2y3NZ/yNH459scQFnAiEAn7aDMb7WhyZBOZ/cR6OOid8uBvpwAgfC7j5EbZ0alcQ="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-15_1572555465720_0.669964653239862"},"_hasShrinkwrap":false},"1.0.2-16":{"name":"serverless-azure-functions","version":"1.0.2-16","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"e3d18c661a357e3eb428c130ff75e8f1777fbde5","_id":"serverless-azure-functions@1.0.2-16","_nodeVersion":"10.17.0","_npmVersion":"6.11.3","dist":{"integrity":"sha512-Wr1RBHQmo9O1tLdJiEfEHUNHulsUvB2Vm9ZJETcs01BQ2qz6+bz/ha20dirJqdFvoKq5/xU/Y3cxW6wfQTNLBA==","shasum":"74573666562e8787e5bb09a8ef753ecff4f25e17","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-16.tgz","fileCount":112,"unpackedSize":549224,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJd3Zn9CRA9TVsSAnZWagAAyUcP/ifJMT7YnHCpRHPkRBZV\n63Vx2MqSh7umC/VyLSwrx/eiNYjr9dVJAnJaf/0EmeE5V+Z6dUTw7YyGaAlj\nl4PsfHbNnWHmsLSlp091kVgnmnSqpOCjnzKDsx3C1Si49M/SGxK/1zv5lmDY\n1+FcohZ7uIGHkhtzswqCMRpXiqatwlHiOGA1TCtVY6uSjvThsngxqvtcwdDq\nX/GvZOw5jZEkBSG+IBZYiyH2OoDShE20Fd+syuhOCBUi8wioq9LgRKYonPJa\nJdLU5g0xeybiK6wsPz2gNuQJqMZkOrrvRdi7bzO9mFlK5p6eP0Nf5nn99U9i\nSnpwagiNlASUpJMAFUeCJJ6PAxPKk4gvO16zr2uW07UrJWmR2VwiXF5ej4Ca\nFNcG7Qz7xao3eh0JVp1RUc59NnzV6q1ttWg38I6zbkmNv8srccKbLMi7TFP0\nDJAfd3dy4me8hSWIiaBkuT6VF4vEJozpUY3lMm4U2zVysFEr7uN9qRU9BKCJ\nthywStjGrzfEms11v8fRdQxi5d3GBCy6tFpOQ9r80kxO7CUzHwgPgSw9IYpR\ny1N7b8eKPZzci5k0YuP+LZ7MpgZm/5Ls4YcyBX+FnOtoSe/BBcpQ1eNUY+BO\n+1++sNJ3gblUBndt1ovBzTusUdkMyjFFCIH/C/aboSxT8h5dQ09BjJKsUtiO\nISDL\r\n=k7oU\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIH3blP/qVGSD28fw6W3LLhQd1ggJ7Z6R0botjAdugzvPAiBSpquUTxaCPvJ9pgo9KV0qm5rxsJyEgyrZanJnfIiWkw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-16_1574803964661_0.2916942738674788"},"_hasShrinkwrap":false},"1.0.2-17":{"name":"serverless-azure-functions","version":"1.0.2-17","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"46e44f978bfcdbd2e63cf753fe5a7bbd3b40fd2b","_id":"serverless-azure-functions@1.0.2-17","_nodeVersion":"10.19.0","_npmVersion":"6.13.4","dist":{"integrity":"sha512-Ct4JUXQyF/5UGhB9iNPwHgvnouEVJ/0l+jBpU++5OxJjpqps2vKELV0G57iSKzyOFmM2qEtePc0wqmmpzpLu4A==","shasum":"8513430280bdc7c0a35b0b45ce0facc7c52c2fc2","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-17.tgz","fileCount":112,"unpackedSize":549469,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeYBlgCRA9TVsSAnZWagAAFPUP/R6u8CIHcPVZQwYTLmVF\nPZm+r253L/HJuNO+tcB6PyvaFuWdnV69Lfx5wGQLrpDuBVj/NLqopd/dnVcG\nGo9FJLN+UgCH9qJqGuZHKwhjNgT+vI+vfn3zm35dVI2I2vA9iXmSv1vkEYSe\nE9+aUOQPupJaDXMLy1K/LHRrlckgAh5Y/xyZNcjPydlkxLz5bTYeW6jYdDKV\nIVuMfDW6UKUOkt/8Tb6a9MjS8nukJvC3RxJvsrY3o0WfVTxUM+goHCZ3ugGz\ngK/rZZ4FwyaHAaZdUOFJh1Ll5hd579+OeOAFx14ucAg84dR22mTGscbjABCd\nZXNbZaDjW4TDkZ3xrxVav+iUzMWvCoYgajY8YyCbm+hH2omwLlfM1Qm+nuIS\njjDtoU+mGfthcVO2C+cqXFQtvpUFwLAw7aU/ObMA9XWfeG207LuGIqbyTWG3\n0XAaImUbU0UAbGb+kUQZ7Pea3GNQuMLGmjG2PPHyrjn6axqImtd7ZUGJPUuO\n63Zs72Ec+UsboLEMwYBJ47jJdGeJxJUUwnNboME6lTMT+a+gyLaLNU3llMqj\nmkduBIpDo5nOoWlSEeeGyleIxWUF/DWKs8BrABYicehyvmJ5OzOQyPtsVfpY\nI/8JQRoxjgaeTP/AgVhot5dh5p89wFPdQTqJh3bzPFZyHrJKki/CapEiJsM6\nBRSL\r\n=65u6\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFUGwOtC4wZX1PXWrtCBryDhpZSFpCi35uOsRP3xp+0xAiEAqfhkK8Dv2IZ7509Z2a3wvv72TvpHJuLxJxf1P8P91P8="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-17_1583356255823_0.282169857004678"},"_hasShrinkwrap":false},"1.0.2-18":{"name":"serverless-azure-functions","version":"1.0.2-18","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"2c49de534f1b31e56a648bd4ebbccf611dc005f2","_id":"serverless-azure-functions@1.0.2-18","_nodeVersion":"10.19.0","_npmVersion":"6.13.4","dist":{"integrity":"sha512-bHX4BxfY9d9e7inJp/l1CXkgRp9rh1kS+myv2JTGRXFpEtsBlZXv+/FT+591A/B9a3+9+LTdSsuhC1tYzbYQ3Q==","shasum":"f8c8730654cbeed3e3d7f92b25e9033151ed320a","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-18.tgz","fileCount":112,"unpackedSize":549216,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeYYwqCRA9TVsSAnZWagAAAAMP/iMpGJd15NYc2/sj0dsm\nZzEiMiH3kPTpGZbLBW05P9ITXYEnMUhQnkPQ4hkZemJQO8oN6IOVa95J4LLN\nDOF0CX7Ahk3qmAft3ozy8K2JjGpa3/pB2/AcuojVXARLM07C3R+rhV+xcmhv\nAZWRTpoBi28vyw9kpbUEHv7sGBkrnVcBDTc3Phek38+TRb36f62T8HHUDcIU\nnVpAqt9/RzwNjwS6sAgEEcEEGvkfEZCgNBTB1D83+jXaHuIrNJ6PBWNSB4qb\nojrsGd06CKDMSQoB76sP5SMj1PbklIc6MxtvSGjzVjWb9tmEfwSeUOsW3bLo\n1Pgu079wJagmZBPE7TscZ1QzszWXS0Rnh5hw7TxlHWHQAMH7is8i9JmTbo0D\nyOUq7t+c34FMDlBVgrZKKRM/W/FstSYviMb8ypbjw3QIEZMqvCTw8xdUMXeW\ngJvpfqcSConO5DR0LMlQ5ibH2sd040XzbLGZPYUDygjIKSA9UhexJ8/ssEwL\nbx+htZw1qlINdFsa+hHOBE8Ov/BevqhOz644DL4Gqj2ryAixofZdWljwhua7\na1Fs/avrIpCnwJ0QpiIBSd6wcdfCRNJscHCifVpYMei7PDM7MtxmJTcLJKfB\nIfqzSwfPW/wOJxHHkcOtLYBD9F/6irul9d10qOChD04y6qo352oPy394PhUV\ntgtf\r\n=sMjh\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFOsakzck1YFL0epLlsNxFACw1Mi3bZ1qq8nOqWSex9uAiEA/j0s3Z3cuw1ZPBZ4P6YIxup7xDpzdOOIgOoquE0Dx6o="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-18_1583451177575_0.6047594150299671"},"_hasShrinkwrap":false},"1.0.2-19":{"name":"serverless-azure-functions","version":"1.0.2-19","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\nsls offline cleanup\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"561f506f2dd3763a19195e7688d5a7bc35b06e13","_id":"serverless-azure-functions@1.0.2-19","_nodeVersion":"10.19.0","_npmVersion":"6.13.4","dist":{"integrity":"sha512-Ydd9ga/6C246PaZHR2cB2UfAZc3zoBwxTta38DNu5IiR1gHKqIj5ZzIwAt1ZaTLjM/vwgy9qcKX/3gLedESTbQ==","shasum":"4e395f92360f1de4fee6bf3aa25cb9d90cccc3dc","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-19.tgz","fileCount":112,"unpackedSize":549323,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeYoe2CRA9TVsSAnZWagAAxtcP/im4lppl/0FBlxxPFmEa\nc+zwjN/v62aLblSUpDXBNbe6qxbpsA7a5DTb5vp7tO7SfDu/uMdkUJg8AFTJ\n+LnemJuZT1FbzcgimW1uvIwB7a/uBOMdOV+e9V1Zo8y74IBJyFIi92G6MKuw\nBXff1MdrXsR2Tit5V8AoWqcJiwh4rsfsXt2nCd3oSyzux2wbaC7XgxiUvXOX\nH8Ft1hYjFJOSOilOrbegcFfQgVEbGIfCXwxlX6mbjnY+grrFnL99CcrYwEk1\nxl2PFzKcF8knJhJps1ad68ZsM8x6Ne/UhsRngV+nVpyuLQGBrRXvySsLq3bh\nzMmpOIAjZCGCSq1j2e//MFj8nSNDRSYipXxq8H4zGWF3AHjrPy7SO++OqaZY\nilZ3U4he/9b7T6wqOAVNWyWcvjaCSwbf2WxXd+eb75gC/qru7HVDlZPEQoWt\n0YrmrkmR0EwL1unbjbmiOjyQf1okUAgMXNjF819529kNqDVN4BSs55KQGz9q\nA1BKyMdPVpZEWSEYCce9qy8nbgrHwaaww/6ysd/WSQ5mb238MGf+6aKH26fG\n0KmiVJp2it5H/9lli7nlf7nsHssgd2gXW5ECluC8GVHOQisQeBA4sbEKNqTk\nqbcSAx1BTBQbe5hQz8/lkvUT3SsG9JTsfiF5iMTmhXY1AtBvdBwoNsdeTbDQ\niVX/\r\n=zDB7\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFpalcOett3qIQwUjOCGPaYpIdnpJjNutt6xRc3GrAbFAiB7ipPBdyxHbI6EtJ+Cp1cMt1mEXiFPoouc15OVgMwB5A=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-19_1583515573854_0.178094572874669"},"_hasShrinkwrap":false},"1.0.2-22":{"name":"serverless-azure-functions","version":"1.0.2-22","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^2.7.1575","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag (`-v` for short). If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `-v error` - Only error messages printed\n- `-v warn` - Only error and warning messages printed\n- `-v info` - Only error, warning and info messages printed\n- `-v debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"50bebf2a9abc23e32157ec7cd09815582d14d922","_id":"serverless-azure-functions@1.0.2-22","_nodeVersion":"10.19.0","_npmVersion":"6.13.4","dist":{"integrity":"sha512-diKlCH2DN2OjP/j7sfPHdB+DSwJgX5/L175jKvA4ttUbefWmyK9M3Ul4QohOPixnPWhKEmR6Y2AOt69DOP2rIw==","shasum":"c70f856c6a93335395c5b714b2562718d0300f8b","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-22.tgz","fileCount":117,"unpackedSize":571764,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJejVmVCRA9TVsSAnZWagAAX2kP/2U7lJULeXvWpa0APh+7\nsvZsWZ6BqGrjiS+zrQcFqTWqpkuYnzyzx0JJW+FSWvH9GM/Y083EU/ed0ynR\nMFfmOUVYGObKvzPyCnKqZ4mo+BfeG5byJ7aTQcFc3gl6Pls1XbA9vamp1O82\nxCXBeDdLOPOVHyq8LGzHlhyKh8KN0MfThcDSFIn7Ud/A8r4XmRGUVRy9DarL\nhZcens4TVUmtvhYgP57ekt3vMJ9g9SuuLfho3elVa1SQlDS34cYg7ae7PD5/\nmgCogUP1ifDmbj0mn1VWnQFLXC8kt0vHijEeoEZfh2DhAhcIVex2ZCTnn0Q/\nCB7gyt8UwvkqVWrZW6hAHLwI3CdbyImRdVAojMK3hH2+P1/+EP4KYYjfpT4X\nyzdiKgHOGwJEb5e+zjOcbOUbnkUpLx5Jm/t3vKSjykCoJtQX+SglmWMtVJqR\n44RDWBsm8YTLqtGWbmKBccfdTIi3Gywq0Q3Nh6oGBr9eP8lWinwZl3vhuBV7\nehEOU9v4hYbsVsakYP3YkTAZ11cZKUjUD1GkErKHDNLVr8e5VTRV4Aqo14LY\ns1Rky4YjaxCqiaVeXjCnTml1dnrWW+Hm2byDCehkiDmmMpDgrkG77kv5egCA\nUxiBWgmnRidJazkkg2b0nq9c7L2AS2BG/atNwCJUlPXXg2+VYxMRZ2P22aNk\n8w3m\r\n=3e2p\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGnUzMQE6+aM7+BcXUqaC3JoWyFy5rn/wnE7iytWkDiNAiEAsxThYCTnBaZ5ZSGbkRjj2V/wZLhYfOgr8+JbjKd86Lc="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-22_1586321812483_0.0945185514714788"},"_hasShrinkwrap":false},"1.0.2-23":{"name":"serverless-azure-functions","version":"1.0.2-23","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag (`-v` for short). If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `-v error` - Only error messages printed\n- `-v warn` - Only error and warning messages printed\n- `-v info` - Only error, warning and info messages printed\n- `-v debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"e49e9454bd973e5a1ab187454ed4f5d5e19d8f26","_id":"serverless-azure-functions@1.0.2-23","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-oeyhyiDHTyc34KVgUiizRp7xE9iDx4CYOGHk3BF2uRpCF+iCpIYTdT5dvJBsFm6vfN+VDT+faULaFuE8S8ozCA==","shasum":"253525483b220561df2e3b4fd1f673f5d9c032fb","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-23.tgz","fileCount":117,"unpackedSize":571764,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJemOToCRA9TVsSAnZWagAABCYQAJ7EFmxCKulF1ktFUV27\n8Crpcwy2P4oAAGh1yujrAl8ID8KHZJupC4aGlRacstKvpgCcC0b1wt9LqRwM\nDvhKwoYUNJLSzfA6NfAcDGgmLqmyZgLT0xTKzrejzBrgZO+/Xa9JpqPgBj1o\nMFFfvfygoqxyIQ+Fnr49MXERo9yldbov2U1v1pOpwLeRImodbktiGt09+Lts\nRuaexWAXK/utdGGpw/Ys5Ge07R3IzXgRF9qCSv9kDRZVwHZnVApSZ3h95NPF\nB/eUwOggwfCD9Vswa0BrFDe7o1Q4AKq3zj0+jDsvf6P6ydhlijji1HkDZElx\nImIVIM//UMP5EYblZpHe2MRayhXVKIUrnmgBTRBenyBhQQwUhuVNbXgs0q+z\nxmWc1iVb+aMqmx3AckSwlPKgj+qlqsu4xWiwVhi8KhLcey5hPbOL5MjsTG9y\nd3Yxjj3OQuQm1d3tY9r/HbLeGCG1T+ej7DhS/eTsjAOe8e4WpDDNYCQ2hm9d\n+GYR8I8r5+/d6T7y5wqqCY+eUKKXr5kgul8Q0sMAkPmSyREwYQM9fFyjm8vI\nlKLE6JpwLloggpRDJboqx3W9dC0FKj4UZACmX4j4//0MJnFOmMIFFsVsUdue\nZG4ubjZh8VVzEQuGJBDN5bhEpKKU88IvQcrPSHBMWQR1MXx1JHjOdhtJPkst\nzn63\r\n=ogmj\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICqCaORo7g9DVQgthqVFK2AGH4NfgUTUyzAaTOmKsz9mAiBojO6sGmK8Qd/bLTfAotUJWDSwSHzhxUpywzQpPir6vg=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-23_1587078375682_0.9594746679019577"},"_hasShrinkwrap":false},"1.0.2-24":{"name":"serverless-azure-functions","version":"1.0.2-24","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"0cc269e2566be3d67846de2a64e5adb4c4d5b784","_id":"serverless-azure-functions@1.0.2-24","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-0CsDkD8a67FnR7Kc8HaA0sqeUVRNbC56oJ9a4hhXdiS8ngzUWp+GmHM0exbk44TpmMNjw96Q+3tAa70ldU5RgQ==","shasum":"8dc3e1dc8c48db908c8f8e040a1fb3a869e62cf5","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-24.tgz","fileCount":117,"unpackedSize":571765,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJenm5WCRA9TVsSAnZWagAAShYP/j8Gx1HhIWQ9xHCetAvc\nKCMMkg+j3bKlwDLTzET8DcTxPUC5MjTksT9lUCuc+hcs5LCqe6fMfHDpG1jw\nN3ZeqPT5tc390cs9Iv9ggTAtImXZgyqfwMFHSm20YaBYD3t9VmnPOp+e1xBW\nD/6QHljcja7eBY65wJuSlcgDVyruAnWRTsRIXllrDTQql0vbdNUUnrp9rqaH\nXldo0daIdPZ9oRmvHbRspdYzD+X5IXkkpbeqYEc/HHZsIARI+PJccJwlRUyT\ngy52fwk8VrsTeC1BDqcmw3lOPC8szPzhVDjzehyjVRF1bMwshsezSZ4Gdqos\nj/1+cbXBrW//CFqlVBiz84PvDG5xdM+vFZh1VCdxFz6k8jKQe/jKXslVP578\n/ZR5mXX9wf1cnZ+rVhC31VeUDs6mH62kiVJE1v7vwdy739YsvZ9gyIDOEcq1\nPPISqi6OGT8pSJD0gkTZXVi138TRaF3+wEZ+Fu4laZC6/ITVYD5+RZ3f4WJB\naIqDJULWoqi43L6PUbzVKtr/9H6uFgzaV1FFf2D9y02BYc6NAmWuwN7krjNt\nNb4ek7kFjZYfgChDY8/78D9H0UVY9FzgySB+u5Ui1Ovx4LIttlm54/cptgJN\nv238/Z21QUwOq0tmS7rO8F5D9n/4rrAd4/X756LIKeR02fzFDJlppDN8b6Df\n3zcH\r\n=UCeY\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBDvhJAlYi7ns54qQ1lIRSFWimMlh8941qycR7RMEcU0AiEA8UzQBcR3fuFiD7ahAlEz+SwweZ2dUVY8C5bxJtAZZVk="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-24_1587441237720_0.6273332643343414"},"_hasShrinkwrap":false},"1.0.2-25":{"name":"serverless-azure-functions","version":"1.0.2-25","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"fb9c8432008c2ecdfcd8b9f4a7603daa4eecb453","_id":"serverless-azure-functions@1.0.2-25","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-nto2Nx0ffsX9MpaAtJgjm98atZcJiOESDi6kIedRkj8Ye9ENmVTsR1bMVy8l97OxB+MkZ2e6t7z/RKTs1KUktA==","shasum":"088dce96264f112263feafece9993295f45805c4","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-25.tgz","fileCount":117,"unpackedSize":571688,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJenm59CRA9TVsSAnZWagAAooEQAJ0VDQ9zXqpu9Ic0VOK7\nRRyu5Ue3M2eK8cJviY62fgahcIitpeiA79WeBQHnveYYmi5fSzJ/axQA32PS\nQJQBvMtwConPZ0p30TSIdjBn4CUQjXSHe/pWk65pqqaFvgQ7dc5PvGUT/MW/\ns2ycDS2tuYr+8mSTk1SSYYOrTZkatmZ8kQuP6jWvT1JUkqisOpNDwNF6Wzdx\n3RK2V76imRlG7hE4+lds5D+jK7MMwvoVz/dFNaQasbFyJ4PwyPBNHeVsEDYs\neERH6E0fo7BUxBQUbK44J1z68KBPOR2RV7XLAZNXYZejyK3BVkcKttyiQY+c\ntbSZw6lHnpI+V8F3myXtnXxsQxSNVDQkUfeBRqpoW7Kk2wz0zSNNHvuvv6NI\n/u/DK2v7CzYzUTyWcAr9FBVZk7tbyGCCBV8Chjl5ymP8Qf1Qt4E81QLTuIVz\nOze7y/7Wu687We1mgHCxsROww5sRK4YyVniUo5F9VdUEVjwYva2bN8rO/n3K\nOf5IT4Fkn5DTQv6byvcDOld2neOvrVpaCaZXEr/PAQshyJU8ocVNO+CR1swD\ncSiKkdsCJz5wHbG6OiT0hbdBW+URtcgaCu1PvaySYfKXVCOCKrpQo8uMzBfo\nm0VntoWGzOfsECgiRDx8I5C1PH4htQYVdRZlAqrjvbAUnch14et1p7bgsHeQ\nAx92\r\n=qubU\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD15yJUm7tNHLmboy5mjgmJikcgDoIcoNQgWGmUeERQRwIgf2Xy/ry1FlTXgv0Mawc5bYWeNc62QnW0C2ZJgDJZCFU="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-25_1587441276594_0.07380800900644569"},"_hasShrinkwrap":false},"1.0.2-26":{"name":"serverless-azure-functions","version":"1.0.2-26","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"7b4d353bd7db16044b086c145a9f942e35230bfc","_id":"serverless-azure-functions@1.0.2-26","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-B06vAYkQytB4qiouoPg0PvMU9OVkNLA2ubUEOJIMZTEoai2pdhi30CmSEsQCazMqfFQ+PfpXxTUnb+ojsr0BKg==","shasum":"3b65725512ebbd6a3aeb1a3645ebbd6c3b0968fd","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-26.tgz","fileCount":117,"unpackedSize":572116,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJennCbCRA9TVsSAnZWagAABvQQAItMBHWVDYXgBQ3ZqQAp\n2f1m6ySFyZZ5oB2VSzJRQxbvf2j7+/LfL+r0EI7pZFRpNXmSFL8FdwMypPCV\nNEvp+PniNkdamtj+htWLHeEqlN9Lvv+XxlshFKIW/c1Q8dEfQYhrWzCnkg89\nIraReGwRYZ5aFWqMNPiIUPkFs73qXhzzzclkK/+B50ln1dwRoFEaZmOGI0JH\nmx8v5tmCZ8sh1ElPnXq57jWUbbnUmt1z9feac6EZ5al1QjsAw8mqZG07PTSY\n3opkQHrn9Eyh/P3MBV8UXOypm414Bv42hp91rso9muYpMuix9n4lS4dVN0yg\nWnGaJ/KpVnGezX3JzqOIzB2w8IPQ0HpW80/RuvYVutg3leXvmgjENThYfD+t\noyiD7LtekTCZUCRJUB03wDdKTmQyvMuAFc/xccg6HDJ9/TgJNy2HImqcFgUJ\nS55Ot3NbHXKJynYl3bJ9MavESeWT7d7lxUHIMh8a8L1CNskHzpHhCwgqUFo6\nDh9yOph8upeWiuWlm+3ABkOJIEY/+6fpem+VtfvEKYqtcect9jvgEhSL7vFG\neOloD7uZHAdbtkuNFtUpv067wD0DuH3NNRRsirhwsQY5EM1oaJOvmNbPyVog\nVI6I8M/fmwdpsLvmGTY7dKjQ6i1Rq9Ptp5zOmOaWpe2M3ggLxqSQClVWaGJw\n/SiJ\r\n=ws1C\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIAHMaJUT9GoJWHN8cWXq34IedPm6ZOYDFG74HXVsWJqBAiEAjJbckLVQMlznQQC7p03WxK18kIpNyeXaLxbwHutp5lU="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-26_1587441818653_0.8967968594318014"},"_hasShrinkwrap":false},"1.0.2-27":{"name":"serverless-azure-functions","version":"1.0.2-27","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"efafe9a6d741f2997c0fa2012116cb43867d91c4","_id":"serverless-azure-functions@1.0.2-27","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-QodRg2f/E/kKZAQsZ54JgbhnGCHo6QoUt+XFjKiRtnLAETXfgi36ujBGlD9AHoWEmUhhG97qwDLUZYNeutBq6w==","shasum":"70e1a4dc04459eda5b09fdb2e98fe601c9be5084","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-27.tgz","fileCount":121,"unpackedSize":597200,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJennD0CRA9TVsSAnZWagAA1FkP/3wBb8ieggaizxZORntS\nKQwOKuGjPvatqmpye3CGqrqK/ZVnUP+IwByy+7ftbbGf/DPBSORTCnXdq/M1\n0fRtYye1/xhYu4VXSUnWiZHdxH8L3x87cm7ecIO43vpX2VGH8o+yDnHXUogR\nF9XWTzEs0Y71eG1xcAgFBLEmnL4l7BnTec9EPoilZ24+/ENcJmio7c4jeHwJ\nClPowXhN7+XTUNHfmuMahEY/QeD4hrAvhJp7vM0mp0s1JGxwZA8Ezs3KyEQU\nv9wQ+EWFhi+zl9Pwf9JpbHrwc7g4AWPL6JnKj8jr/JIGys17BYsY3DMMt3gx\n3q16JewYJcWLCLsHznojhwaRFw0nQkz64T8gDfytFeTBnELLrK16WrrSweEV\nyb8C8+d54KHj5pccCxq6wovY8bweuM0t/JsSpfpm6Pdnh7gbMD4tQgrMPOjm\n/P6rkH5B9V7Ktyp0vjisX+rmvScl0DL/ofFYi42VhVKpk3aPlHAqnSuXy+yg\nOgoA3pg2iSm714LrFFe2zhbjK9WilQMqm5C/hRkom/oV6FPf6ldMtW4A5rZI\n3vNjVc7gj6K1ZgIuVi9/r1bR9xGQLWh3/2DZzqjaByXTC/C+yPznuxC8cv5O\neJVKA+LTF7FqoQiHyOuJgp+Rnxj0YbhNNIVA1Ahh6CDvKJKmwKOPFaknJJ3y\nju+q\r\n=mX6i\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDNqLJOIMEFZCnZbx4FpiOTCryZ5T/6PWZ8c9oc4fvJZAiEAmQY7vkKvoqfzeeniILfKXdjMGsE5suce8J41/ZoKFLI="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-27_1587441907570_0.6349615304469269"},"_hasShrinkwrap":false},"1.0.2-28":{"name":"serverless-azure-functions","version":"1.0.2-28","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"1445de300660ef1edb779a6fd9ad1d550a488699","_id":"serverless-azure-functions@1.0.2-28","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-ylAp/wciGfbxCghHz4b29inITYCDW2P7CocPIsayur3zrO9rTeKKr2W205dUIx21p/4t7I05eOK5Ni4M8qX4MQ==","shasum":"6bc253bfa3322294f7abb75615fe24ab31315f63","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-28.tgz","fileCount":121,"unpackedSize":597229,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeoyhQCRA9TVsSAnZWagAAahEP/jxuvkyqteGjyhEuCcmP\n1W9RvQ3z9BBqbSW7dm+W9f6iDWfAy/lkXdTo0nY2e5aEY1M1Mx7VtE4d/bZl\nsSyX/ik5KjlEy3lRmTvnCW1UAh9P1UXoGCBnKUZVb+ldx2joZUpUyRLqpdNl\njguFN7yk0SV+NtvbuL1M0kbAo/DYYfJMJs6jXQaJCf62kMkvdiWBAR+UcEqd\nKVVka+mE19TTtmU+frBbhU6gBUueAWr7cMy/hcDRaLUj5AaOaM+8fF974CNG\nlKEKwzZmbHb6NL/Dj8vBUtqHf7o50h2dFYUTqkH73zTvYx6agcsXoa/a/pJJ\nmxya3Mw3M50zyF92xCe3Y3FJAX91Gz5niO85eM0driggDnrk40BVWl7nBzFV\nMtsrG3x3ClEUrL+98Kjz51CxFDkw8DfvbKKQJivqwoYSdGT33scMsvkgCQjr\nFjAmr64ANFnbyQP5y7qfq6o4e7o6gAe6nGz1ML6O1kP8813ZAsf2UnE1qjlD\nNd5m/RR1nF4K6iT/dCcPdRVxClROfwCGReqQCh6+gKYCUBQnCooCmVLucoNx\n6F92hYVt+XkRJO/dFS69osZewq2q6CSQGzSq4DGKBA3Fj7e+BGkn/tYCBj6F\nYu7xCfuWKv8mWGBtrWf8njHNXxQajnveHKrE17yjQtjFojm4BLXjSIDVCRUp\nBdK5\r\n=ASy2\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCMXdnHn1s9kXt8vA5MtMDdh8wlT89s5xcXtzIK6jC2fQIgOnA32TUIfjWGTKct1FLzXSP50IUoOUTl3LAQ8EHY4fw="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-28_1587750991863_0.8235851785342958"},"_hasShrinkwrap":false},"1.0.2-29":{"name":"serverless-azure-functions","version":"1.0.2-29","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","pretest:int":"npm run clean:int","test:int":"cd integrationTests && ts-node run.ts","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.3.6","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"98a3d3ef6f7d39d53f0f203b17da0350654ab92a","_id":"serverless-azure-functions@1.0.2-29","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-NpsCEgVh+kl+Nsoivpi7fQPVbdYLBHvdyCd+ap/uvykuexzzUMxmpbnS6O19RP+iENpyWLwI2GinivwSUEW7hA==","shasum":"edd271420022f5c17e9956154c3e51be79b0542f","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-29.tgz","fileCount":121,"unpackedSize":597550,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeqslLCRA9TVsSAnZWagAAs9UP/1YusoF7lJ5lvo7dkDiO\nqvym5oLoI5oqAElh7i/oswlrsSijq/aOOJ5sdSX0Wt+05rF0A5IhmXgxSHM5\nYcBXqsG+BL371H0czfyGozobh9t/Fqes992+z3VteItvJQKW6mRxggXyE/rO\ncKdbizRUzKgJe/Ot+97T0HLCvb8HEAYLZAGsb5MQvf7fJeRWHWs/xQNcjiK/\n+pOleefLxkaCcCSwuHCq/Sej2ZJ41wdcKnQYeplxVgJhEMqgxIsBesCy8OvJ\nNTehHQFlc6Y18wCDRRGetMbIevizJ4ZsXTHelSEwuPKTY8Iiarf/ftLBhJAV\n6lXSiaA3SAi+Ae9h2CkfD3zJ+mKAgvDB4j9gInSc6uvO8W2u1cqhKbx1MCj+\n09GEHIS0LiD/eHGxyXbnvVOi/C9QBYfHogGzhPYGEralv9XbGbroOG9g2EVu\nWdaYkNJRHzKSI0mg2RRwXbM5zTJbSRQggtAOBPU0/NQWe9hJSG1O66Qs2lnQ\nQr0PqbtrJhSnIuAxoe8X3lWZaa85gNn07HA2sf7NlNMsdly9M91mChFvONCQ\nMxoTuoSXwTpTxkZ3aj4vJ9pSpEug7YGUDo4hBxdgHR+kHziwL/wxzxbwpbH/\nj7lk+/YKRHvanGPHcgT68ZAx8Shv/urWUCJSiqKFQ4U3nPat+a7EX0f8CrBb\nfkFM\r\n=gFU0\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDylKc2hAfpKJw8gPySn1yuVYIRKhBP8perTeHuepGE9AiEA3N9dZ7wozC1X1ta7snAILSLekwwdyl87Oxtlp8Z7e7E="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-29_1588250954764_0.08273789581728996"},"_hasShrinkwrap":false},"1.0.2-30":{"name":"serverless-azure-functions","version":"1.0.2-30","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","pretest:int":"npm run clean:int","test:int":"cd integrationTests && ts-node run.ts","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.3.6","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"3220cca79d883a0bd29cc51876fa2e1904951e73","_id":"serverless-azure-functions@1.0.2-30","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-doQM8G4S4vsucRSe9lSY4uXzxXlU7lFgFDeSk0ByjmtJxEd2AMTJsJoaD9IvZ3rMVWl/Klwf0Xk13LLc37t07A==","shasum":"82ea9f67fe711092988ad3b8b1d8b3251a25f0b0","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-30.tgz","fileCount":121,"unpackedSize":600082,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeqsmhCRA9TVsSAnZWagAAisQP+wcbo5YRnKhocwOMceI9\nzEPC3HlRpXOrwVb6vlTLnwUoUZu8OwbtW3PXYK6qJ82bVtcBKdObZRaQi20j\nrX/wCRkV2fqzjwzvWQ2levhrzDQ804wrUAELSntALcqTYR1v/Yyv2Xj7OwtQ\nAmBo5+M/VC0VYTFQLdooLiNIcsizSfXqpfDW8+pSCpcGC5EJHykjDaat+8+m\nHArGVnd6ZiUJ9GM2+fc56v0M6KDJ3vC+zNvUdcEIIpA7dc9TWLjTKw1U3+Qu\nC3BEAPdOfptyBSukEST0oIzJKiODVOmBxIdp7LU3/ZpCMeL7JK/v6QpxS6AC\nO73qIvRz1GISsNlqbhDRFilMH6UGvmO/+xDAoddTM+URQKQgxKPuwmv+BfWQ\nd72gRtZu+iYC78Al6Rn+stu4Fabe2CQYzJSKj5rJifsjy8j3y009+NtjxRv/\nw2V2jsCwpSveaLR0Sg5H4eszm+A63YCtwX+FYQw5YBwvZ6oNO7SqYrTFWneq\n8yVb8B3n9YQLrLPWCQKb/Skh3v6pElZvubElflw7VMxbxySznIUxM8XGOci2\n3/0MgBCW3pBNGMzErEj7d5pp2hhxvoHcI7T3Pn/9i1jo7O/wyvvV4aMjJSAR\nrd1XvtBY7pCEPta4VD1lPO3rc/zqw0it0yEApEO+nv9oftQHH5JzyEwVurtR\ndc9E\r\n=m1kn\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDesYq6vpYx+gcOT/jRk5REjuR86d9dbFHiStaHYjBJtQIhAK65AiPS6I7MgXnyVjQWz858Zu25So7IOSV7+JH0xI2H"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-30_1588251040606_0.8651944543646533"},"_hasShrinkwrap":false},"1.0.2-31":{"name":"serverless-azure-functions","version":"1.0.2-31","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","pretest:int":"npm run clean:int","test:int":"cd integrationTests && ts-node run.ts","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.3.6","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"9473fb68b5a59155aba3b6b86b071893512271d5","_id":"serverless-azure-functions@1.0.2-31","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-h6nfH+ksC6i7TIr54dB6qrIhRhUPd4626i2rzmg8B1Hn8aW0OHPoU9WiH5bB1h3vXDYK50eKQVd7kHyYDfQxlA==","shasum":"43d937138319d033e4c72ac3ddd03b616e723848","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-31.tgz","fileCount":121,"unpackedSize":600409,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeq2O+CRA9TVsSAnZWagAAWHYP/R/FeI1KcJIo4KkSf/aH\nbLWkUIbgh3bdr0PtDpiWCMgf7+aCKH2PUUHn2EJ07O6CRtj60jJxwbOYpXFD\n/pZS41Axd6CJf5U1oyzRCM7gYFTI2DTWrrvuA+oovZd59L+49cdNuU+krcFX\nHmlvJp59GQ4lSk+ib6PHt+QuNCz2hjPDWFHfCbgSjrb2JaYt6bDlelZWy79T\nDCI3BPWYBmoU1AKOMIhmp8Hhx5SJMvqVqi9DtTXGK8nJiR92ZxpJxuzI/+Dq\nIuQHaWaqASUSBENqthBUwjyyiKJwNVOUKOzYlhgd2kw1mKPaFDd0elovlN6C\nUi/CtPgSF5BGDQO3pPkv3Iy48SzqbwIdrWxtKVppjVliNTJzQbPDDspityfm\nu/zdKAdEOgYyzwt0ho0n7I9/5ZBRDDsjc/RuHyB98FIf/vyNWq78r+5a6H2n\ni+VowakmHTmDPa+D4WB+fCfDEouMX8t6+D9Hpxy1YlKKY1yDATAerW2qT5Os\nU4KjUQzZYAhsyc5QxKqmU0wHhALu55/2L5EuuIUG79QJpuQG9hu0yLRHsbr6\n4mlcXuGiiE0Q9Oc9bq3dhiyHzXq5kg7w6Ev8zCSUxW+sssTOCL4t1oEzkiVL\nCxZLBvdpss3Hai4VInNbwIS03FKEGWIWCAoSIbrLbSq5ggot5u++a2vQXsCJ\nFq9u\r\n=aHfr\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCnCz4in7W1ZUu6vMHPTpLVP6CCzmnk+mrKAYD75vB3cgIhALxrxWSmvBkVB4PegN2p+DsRvwYBXMWFgp//j71j4mbe"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-31_1588290494207_0.08050159861739647"},"_hasShrinkwrap":false},"1.0.2-32":{"name":"serverless-azure-functions","version":"1.0.2-32","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","pretest:int":"npm run clean:int","test:int":"cd integrationTests && ts-node run.ts","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.3.6","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"1f98ec3ed4b88857eca331d291c45736ee70471d","_id":"serverless-azure-functions@1.0.2-32","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-OlazIjBxdThs51Ww/X2YYQodHkjRKywnyQYjMMn3NEDxo18zGJ1aoesKyT67ciR6xBZiB8oTzhMG17VJqybkUQ==","shasum":"b3a91983288ac8117133184a1ef1fea282220acc","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-32.tgz","fileCount":121,"unpackedSize":571770,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJetqUrCRA9TVsSAnZWagAAiSsP/iK6xwjK1tVRF649Ir6D\njbK5pwmypgQFfAIl8tsQbbUCBZ9X/r1o3H3IM4MILR340IN5KqY5WTCzPGSw\nZmEKFB9G7No6QJ9ZmU/KuN6g6jq3/Zus3bZaU2cJ8uMhaWfH7kRR8TEYDwR9\n0tVOylDNNP12JA3stUwhr6ZiKY0bqQnwQWjSpuGc519mC7lP3+baI3LBoM/y\njsnIE9m2YoqMwm1NcWr/69wGj1Am7qghmLWo0UKA569fQbjtxCby6/Cs8rF3\nyaUGFohX91UcuTLYiWLBrqfD6soL+xzmHSyiF0SUokcdoYDE57ReoWOQNTRD\nNXcoKDUsjZKLzSP8X7xtwg0IRdm9E3TQN+JPIvRB7cDyyYUvkRPZnKO7A3L8\nFyAmuZNDhPWR7jfUrGWtqFjojxN5UHNqXNWDKA5zJjfhLbmOaWcGP72bGfeE\nHPYDqvpCjDfvAyU+TdR3ET8IgBcnN2v7AJLJfPQPowRHDOB3G49tjgw3T+e9\nUdFR2qUmrgCL5JPuOFVr4+B6r73k/yLQLxwXMnKTKTJDO1nzjQa0qLHnbRGl\nT6agy8643W0dnxg/1E2pWm6vuG/rEnIuuyaCk1GCI2zo8TlITwJ+bM9aJ1jP\nxulzGNcFolguR2J3lKnfNR8vE7/oV3Fkb4dqLWrWX4iC764H4XNo6GcOA5TN\nGqIh\r\n=KYXb\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICEX1sz9yHV35F4EsZIqFfWP8hIQJ1PJAHr9SeyflauNAiAdErOC7rqAfyFOoqhoHg5LfukbsuN5sR0FnhPfhrawYw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-32_1589028139496_0.4541237746200375"},"_hasShrinkwrap":false},"1.0.2-33":{"name":"serverless-azure-functions","version":"1.0.2-33","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","pretest:int":"npm run clean:int","test:int":"cd integrationTests && ts-node run.ts","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.3.6","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"c5c44c9d419de90d3bbd0df75c2237cd8bfdd534","_id":"serverless-azure-functions@1.0.2-33","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-qMqHUHt/fcf7loLoz/4uSq/CNO7NquWgKOt2ZJ0VueRm9Pwow9yOEBG7S2gf48kHI6SbAA267nfS/SOtf4uG7A==","shasum":"1a2075b7e71fed1a5d2aca74c559871048493c5d","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-33.tgz","fileCount":121,"unpackedSize":574577,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeuXDNCRA9TVsSAnZWagAAX2wP/RsDIYJ+Kl0imKFy/tJO\n7tJ119ZZooXoCUoC4cZKv10f1ZgkiavLpnifvTnqokAPcQOx0+MOelLanCeK\no6AoX0EFsRi+UR2rXYU9fg0wzAFAJ28fRafbTXOJppF3fdq4B8DFQTEX+Th2\nwDi451Q6L87UqpxBCkUe8wfqu7O+Tqw4ZLyNCVONOxLbqTSjCz4uRlZMr6Mx\nMz/tYgU4aisWKmJAAn4DdFw7aR8q4XkfrkeV1XblRk8r9+Ca9QFzzEmgDoJE\ngjH+PXjClHiETgO99akQielAjyM5kbWi3fjBlnSqYT6t2AFCH4s5lsbDttb8\nfbpzXI+r6DGVDWXCVtuUqQkdBz8F+qOI43ZPuqgE7QlcnUX5DLMhV0Pm9tPi\naxm5EUhLlOXNGkz+VT9UiqZap4btXPSUrkosLd2vrZ0loOMjpfdz90t0KAXL\nOR9HpmhFiVOVow37WGMoiatiHv7rPbE3CtHlD9fPfDKQ0BbpbVx5GwuvN4om\nvWQ+F9qLYRxEol5mZto53gyQsTOTMuTw6KuWGm9ZKPjJ/zb5jmC9BAjWzLN2\n+znCJotDnOw5DslVp+aRXBmTlR12IYH9SJwtLw3pmYPQqLL/6hsNhiaBE8fd\n9URihPfmkPQFCeStfvEvYbYgsEQi71sN/cffoKMwEoRWXkAWxSuZJCtsvh0t\ntICL\r\n=BelG\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDNtNGmQI89T/3UkgSplC2wL81Xt4jyAbX8kmh93WtSZAIhALvz2JEaYaVKuJeVuIWWYfo2onvKALzV9gYrDt5E6WA1"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-33_1589211341102_0.22735057333034514"},"_hasShrinkwrap":false},"1.0.2-34":{"name":"serverless-azure-functions","version":"1.0.2-34","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","pretest:int":"npm run clean:int","test:int":"cd integrationTests && ts-node run.ts","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.3.8","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"129b386d5b9988d46bf59b4e76f468d0f632b217","_id":"serverless-azure-functions@1.0.2-34","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-Cv3OCwvr0WriLwBe+bVthyOL7m0XMGyuIQTDDOoeiXtNOtNT0vATyy3TSR3Sexwuw5q1BbxvVqOJgo2YxTi5Sg==","shasum":"f129dad6c6925d02560c873c138064cf41e81aa4","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-34.tgz","fileCount":121,"unpackedSize":584050,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJeuyLICRA9TVsSAnZWagAAww8P+gL3fd4XU5Eso7lhiOYG\nGbbDo21wP5jkCCBAeIJl2vmAmDjaPzAj9gC5T7WS5oZoNX8699BVArRkDC9f\n7+z1Aw0EhYIrI975dHwGec1XSlwJIIU6NWe63i96x1acr545Ez72AaI0MV2+\njDJ+9WbNVbKS7XjF2EZyz6e3CWMFZKW24a51iPFEnQHASjHHbpEM4mmhc9QA\nolQWP1cJo5QtOgjN2B6SBmxSNBc9FiWff9g+SWOJIWLdLMbxcVp61k8cdTqn\nJ/qnt7HcROY5O+E/Swg80wR9CjCAROljZMcCznL8GqRLzX/+YIBYyky+P4mu\nm3foSUJi6Jh0zTQuLjQdoCcSXMmlQg2uWRzxWy7KaQy9g7DnKRdZQ6wEYK4k\nVCOiNbSgkH/qJ8UtkzkWFjoJaJgVSdnHEYfBo7sQ/t7KosM+4G6jouXkkx5w\nazXvi44vnclmqMZAHlKil9NEWBrL4ElVNNEefi7FUZE/rb0LfrvOjXHGypWB\ngx82Z3hxshW8k011eU9gDVeZxfr/ggQTI4sEPnB32yOXaRLr8ITyC2RRcUMf\nbSUO8qMBSM3qjVvNZpdMuoWgOPlusQ4ON3tWxQmTFGgU7ehqyPw9zQ+CAdY/\nlBMhEjfv2mOlDjVXhCp69re7gIy3ou1apXtvsatd0rLCN/V+Zv4ytIUn6hDd\nfRQU\r\n=BWj8\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDp7vbNT3OdC4pWVUGJEV08Rl5Bpdsfpo1GkdZLy4q2/QIgfQruH4jgh5Ism7I3hwAPSvepqo7W2q3UyWhpC757fNg="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-34_1589322439504_0.37943594294407545"},"_hasShrinkwrap":false},"1.0.2-35":{"name":"serverless-azure-functions","version":"1.0.2-35","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.6.8","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n![Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Integration%20Tests/badge.svg)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Integration Tests\n\nWe run our integration tests twice per day from our GitHub workflow. These tests install the beta version of the plugin, deploy a function app (with APIM), re-deploy (to make sure ARM template deployment is skipped), invoke the function directly, invoke the APIM endpoint and then remove the resource group, making assertions on the output at each step. While the number of configurations one could use in the Serverless Framework is virtually infinite, we tried to capture the main runtimes and platforms that are supported by the tool:\n\n- Node 10 on Linux using remote build\n- Node 10 on Linux using external package\n- Node 10 on Windows\n- Node 10 on Windows using webpack\n- Node 12 on Linux using remote build\n- Node 12 on Linux using external package\n- Node 12 on Linux using remote build and premium functions\n- Node 12 on Windows\n- Node 12 on Windows using premium functions\n- Node 12 on Windows using webpack\n- Python 3.6 (Linux only)\n- Python 3.6 (Linux only) using premium functions\n- Python 3.7 (Linux only)\n- Python 3.8 (Linux only)\n\nWe made these configurations as minimal as possible. If you are having problems with your project, feel free to check to see if our integration tests are passing (see badge at top of readme) and then double check our configuration inside the `integrationTests` directory. \n\nWe use [Clover](https://www.npmjs.com/package/clvr) to run the integration tests, and they run 2x per day in our GitHub Action.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"db4beb4c6d10141dde5aed6cf246ca47c6e93c31","_id":"serverless-azure-functions@1.0.2-35","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-jL1Va/Mwn4/1gQzcITLUD4fqMhrdwa2iucviNFEkK9Tl3PBgzlu0fYiD9GsijFsBLxbBBsLKp6bFDoDcxlCcww==","shasum":"dcbee12055a117b58a44bce68f6bbc83eeb1298e","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-35.tgz","fileCount":121,"unpackedSize":585609,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJevwlHCRA9TVsSAnZWagAAmsgP/ibQ15W9iamXpd9ZW1c/\nQstiSneHrO8hwnnxcwlTBlSMXR+PpAxJNxXPN6S3coTc2NoGrinHtOsLu99T\nwFSXm0+XKTYpactC8Eow6pOrvtLxZUho0ILyZeCTwlbNiEI76MZ9kYnE7KTp\nIacYOCHWr6SdtypmwW39VWYHqaHM8VvHqrxETLbNT6pTRm/qaZiYAUbxLuxa\nHHclbiSgQ6nLmtc0xASznK4S9a+6HgVpqYIIheBZbY9pbbIjeIrjxaVq3eJi\npAnKIReVpx3v+CPquow6EKgfXSTj1suNN9l+2CkcYjKnplhQIwu0SVZ/J3c5\ntZrcmLbHmH13ikUjvaHS8I1v2mA84M7KzQNHF9uhnQw61ndRAvtpCzV7tw63\n2D7yh4PyXZO9tyL0dhp1TZP79mnXZrlbPQBkoOJ1Hd0v07JXEieEYi7CrFzI\nVGwODLcHQkuHNSVyWsN2EUjM83dx+ptSR/KuUalwCJkt3gLFf/w5cKFv+q8a\ndRFVz5J7dwJF/z85pVrOCEU748BREdqgjZ9DfM71j3oC3pnfL0dpJFlqybRG\nNw9Fk1NOFhQRWjqrWaRp1dhoyDsHd308mU3/OFLux4IgOUENgB+jNaCLEWCI\nR7ej6hxJDAgWErWH7Sv1EdRRyHhfCOJgYspCAzSs6nE4+MJb8JYn6gX39973\nS9CE\r\n=L2Ln\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFoyw6Dq6JBZcAUt5w0Xwc5MqsuTfhY82rzUYdrYJlw4AiA14vnlPdYMaf4Wg2f+HPv8A6EpuVwsijGFRGU7B9wgtQ=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-35_1589578055015_0.9735635471432484"},"_hasShrinkwrap":false},"1.0.2-36":{"name":"serverless-azure-functions","version":"1.0.2-36","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.6.8","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n![Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Integration%20Tests/badge.svg)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Integration Tests\n\nWe run our integration tests twice per day from our GitHub workflow. These tests install the beta version of the plugin, deploy a function app (with APIM), re-deploy (to make sure ARM template deployment is skipped), invoke the function directly, invoke the APIM endpoint and then remove the resource group, making assertions on the output at each step. While the number of configurations one could use in the Serverless Framework is virtually infinite, we tried to capture the main runtimes and platforms that are supported by the tool:\n\n- Node 10 on Linux using remote build\n- Node 10 on Linux using external package\n- Node 10 on Windows\n- Node 10 on Windows using webpack\n- Node 12 on Linux using remote build\n- Node 12 on Linux using external package\n- Node 12 on Linux using remote build and premium functions\n- Node 12 on Windows\n- Node 12 on Windows using premium functions\n- Node 12 on Windows using webpack\n- Python 3.6 (Linux only)\n- Python 3.6 (Linux only) using premium functions\n- Python 3.7 (Linux only)\n- Python 3.8 (Linux only)\n\nWe made these configurations as minimal as possible. If you are having problems with your project, feel free to check to see if our integration tests are passing (see badge at top of readme) and then double check our configuration inside the `integrationTests` directory. \n\nWe use [Clover](https://www.npmjs.com/package/clvr) to run the integration tests, and they run 2x per day in our GitHub Action.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"0117ce3e704be047a215f2fba853862895774ec1","_id":"serverless-azure-functions@1.0.2-36","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-nv2pjo19Wm5u43ggkRW7+d2+8Q1J3PuCLULc+ZNsvB7KZarMIuyDILpv3YC6KU8kkNQZgwZaTzns0jDAi89BoA==","shasum":"55d64ec6501f335d8ed40245c48edba83d2f1537","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-36.tgz","fileCount":121,"unpackedSize":586268,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJewtEjCRA9TVsSAnZWagAART8P/19aBgyNVESgFR+c5Wgu\nMALX+o2Tdrk4A+cbodIPPEpzTW2SDfw0F73ArZXS7a79Z2Z4O0WI3J20Ns4K\nf0Ru4eULR3cpDh9Rotzg0BGDo+qpSsgox+Lw7n6ZqIZxJM+RRn1LlLBCE/Bx\n5F8NC7U4ke+G8lc0W+xxwRgSwQHLIAbTUnulxFFf+yytqN/NG8O5z99sCKfJ\nkWTuQQFeuVzfZVQpst/Co18cR7uAmGI0izZPVaqrQ4i9Kc6s8IYjU4oZxiZK\nGmjc06ahJYZKCNS8FWARCf8t04B71iJnPYPR64l9k2l0at1lOCvBmGl4z3MC\nPw3vgmqsPVAhtWQ0AuJ+9JCQWNscHd2SNLlxgXh1GbTTUcPeG64enCO7B8fi\nDTeZ0QBtjcngmnkt//QDyCXJo1RbLma6hZJxvUBTFMo13JxvvZSGHJ5l/CPW\npr3wv3EGqN2C4W41YvvTJo5OTmlYdf9SAB5S+/TKhpWRK9PWGKo54uWBh1W9\n/OqyyrQODKrunskUZNaZU2CRedHLFdxgC6kqrFst+VXPdmetFv5jfSPehFLL\nTSSOhUNZoyt9VGyBPaLrH46HG3DoEHTH/LZ6uKIoaE22coKO0TkYJSdwQOkd\nKT2ro9p1Rlx5OxTdItXXZClV/iGgiiv9cptlSmfmoi5JuSfw2vXaH4qDyqq1\nnUFM\r\n=h3xY\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICjpuARHzKmcruLgp+C8GG8GAzQVF3gTVf/nm6RDDYmtAiBxBOGXhYMVZbCeX2rXDxQwUD0BMwiDLNy+SOeUUapmMw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-36_1589825827059_0.6377476734350103"},"_hasShrinkwrap":false},"1.0.2-37":{"name":"serverless-azure-functions","version":"1.0.2-37","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.6.8","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions)\n\n![Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Integration%20Tests/badge.svg)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Integration Tests\n\nWe run our integration tests twice per day from our GitHub workflow. These tests install the beta version of the plugin, deploy a function app (with APIM), re-deploy (to make sure ARM template deployment is skipped), invoke the function directly, invoke the APIM endpoint and then remove the resource group, making assertions on the output at each step. While the number of configurations one could use in the Serverless Framework is virtually infinite, we tried to capture the main runtimes and platforms that are supported by the tool:\n\n- Node 10 on Linux using remote build\n- Node 10 on Linux using external package\n- Node 10 on Windows\n- Node 10 on Windows using webpack\n- Node 12 on Linux using remote build\n- Node 12 on Linux using external package\n- Node 12 on Linux using remote build and premium functions\n- Node 12 on Windows\n- Node 12 on Windows using premium functions\n- Node 12 on Windows using webpack\n- Python 3.6 (Linux only)\n- Python 3.6 (Linux only) using premium functions\n- Python 3.7 (Linux only)\n- Python 3.8 (Linux only)\n\nWe made these configurations as minimal as possible. If you are having problems with your project, feel free to check to see if our integration tests are passing (see badge at top of readme) and then double check our configuration inside the `integrationTests` directory. \n\nWe use [Clover](https://www.npmjs.com/package/clvr) to run the integration tests, and they run 2x per day in our GitHub Action.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"ebced108402b863c7d3dc4bec440c5fd6311c4b4","_id":"serverless-azure-functions@1.0.2-37","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-Bo2KparfKR+nfC1B3DOpYJKZ+fA8jNz7rUKmSOZDMCfc0zg/zBBp+KlBeODsTazwBl30W8dMd2bqeFv5itBPUA==","shasum":"530900a848a665e623a10c4c235514ba4a9b949d","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-37.tgz","fileCount":121,"unpackedSize":586972,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJexFTeCRA9TVsSAnZWagAA678P/0ENbsp7xT65GNq1FH23\n5p9/S/43IZVEM0M/Owp3M67nfrHoxCIjMVMpjEW28yIbrhH5nlM6NWIDy6NY\nN18gwZjoY9KKiqmz7yeKV+6B6ZBlO/5cs93dmzwfQLjC7FnYzFnBP6kwbnRy\nbK4h9dplfu4oYgIKZX9ah54mErMGFqufKv1+M4SKNP92fDE1ChpU6X2RctxO\npmvPOWSTbwld53noRK2fT6+egiwH0cS9W7fJcb0fCraDe7DFMnYKocLVVQ/a\nCoCsaEEjF8N6b+TFF4L6cTe5zhboQ49BOqLrwZ0T4ckD4Ck4U/58kZeXUZ8M\nmOKCUlgyod5crrMbun/egxu3LyuYz1SzKnuSitvy6y2/z2EGq+Fw664K0ZbH\nIHPcg4gybEqrCalh20CYWaSd/3XFemZff7SnbWrPb/tDhJTAs1UHGDYMnTdE\nq872N06v+m4Jtvzld4vKjrHsApZ8m3Y2mwaaw76JN+WFaST/nWbWcjGbE50J\n8aGYepNAJOhx/WFX01lGGEeUtppDbmbqueO2O0OiRPR08VW463wkXLSGLJAR\nGrvhArEhAPDrd52t4gMGpBEhDreYziEh75V5mKNPTlRe7OGN90zRMHEJKHjv\n5/KZeOlUlthwm+LoxAYaHhHddkOx4u6zv9NHRfHqexHbWjuPm7JqIZwzqNBp\nYglF\r\n=D3OV\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDQROKq2o9HRTqB+mrR5TrSpFLY+y3tN9px3yDg+b10OQIhAJ+fdkPb9NtxSRd+a4CK/cokZBSHMd0InULPJmLhdHp7"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-37_1589925085777_0.19280467462095263"},"_hasShrinkwrap":false},"1.0.2-38":{"name":"serverless-azure-functions","version":"1.0.2-38","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions) [![Node Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Node%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Node+Integration+Tests%22) [![Python Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Python%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Python+Integration+Tests%22) [![.NET Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/.NET%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22.NET+Integration+Tests%22)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Integration Tests\n\nWe run our integration tests twice per day from our GitHub workflow. These tests install the beta version of the plugin, deploy a function app (with APIM), re-deploy (to make sure ARM template deployment is skipped), invoke the function directly, invoke the APIM endpoint and then remove the resource group, making assertions on the output at each step. While the number of configurations one could use in the Serverless Framework is virtually infinite, we tried to capture the main runtimes and platforms that are supported by the tool:\n\n- Node 10 on Linux using remote build\n- Node 10 on Linux using external package\n- Node 10 on Windows\n- Node 10 on Windows using webpack\n- Node 12 on Linux using remote build\n- Node 12 on Linux using external package\n- Node 12 on Linux using remote build and premium functions\n- Node 12 on Windows\n- Node 12 on Windows using premium functions\n- Node 12 on Windows using webpack\n- Python 3.6 (Linux only)\n- Python 3.6 (Linux only) using premium functions\n- Python 3.7 (Linux only)\n- Python 3.8 (Linux only)\n\nWe made these configurations as minimal as possible. If you are having problems with your project, feel free to check to see if our integration tests are passing (see badge at top of readme) and then double check our configuration inside the `integrationTests` directory. \n\nWe use [Clover](https://www.npmjs.com/package/clvr) to run the integration tests, and they run 2x per day in our GitHub Action.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"528fb1961d7f13aef21989acdbe02a06a71b6b21","_id":"serverless-azure-functions@1.0.2-38","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-MvYTjSgIVWDi0exhHndhZ0zLhKynAllcXKt8P1p1Wkq5nhVgALYPHBpKPdpUP+j+zKiXK4/iekxbNlTCJpEHDw==","shasum":"a54eea212c84c6b468d37c81234b5a64d7783623","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-38.tgz","fileCount":121,"unpackedSize":587593,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJexFUiCRA9TVsSAnZWagAAtxQP/0iPOXn1f7hXC7Rw3CMT\nt0BsQb4rTqbA/C+oMtV20u4IkUbB7qCmToi8fecKsJo+IshJh1bw7oroBwOH\nEH8XNy+X3+BRUr/r6onW/T5qiD2e8Ek+U/UO+2Rvh81qG80dpmWQcXPvz8za\nRLR28KnMLt8boJggz3t8fhYWmetl9U4I+/I+B+3crSzkRptWJjk1vwKFstf6\nF/k3zZOyKvdspHyLWs0WZr8qDsV39ZQjNJGfWSSfRPAfCobpb+SA2c0jrJcv\nhbzpGOAz4It1NRwBY9WyRU6Nu6GMOwTKP/7YQu4LGM7C6mlQ9Xio4nk8bVAW\n95QkQuMtq8P3vx7bo8crRp4RlgDMaJi4nNk9ZOL0vfcJoVbaHOAb4w7VRvTh\nQ5JeuK2QaL2xrPF9I8I27J9PJeY5ABfYsawUklw6QAx71sOxBJer0DMYmaOD\nM7rLYIcBVx9NH04o02mgfX0iJvAgrEkFfcUxte3RfeqLFKNYoa+OcNP//XlE\nnna52X6zdGM+k9COSmO9APKfbNaHduSdIW73u5bnFL5zL70U+rJbcy7OAKMN\n/DxP31YFpVbU/xeWhrZaFOI+hRI3FAkEqrl5+ZRPXQnxmXJY4WxMiucL65Em\njVy7aCce04VehGcKlVx5dZsMHQ+AyWYdQHdlrPdX15l7FQiqPqmRSp3Z7A9H\n5cMv\r\n=YddU\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFpIksy/PSC6vIW/KgH3oRCOZBMTlgwiFTNM23NmsSMbAiApWW35kCQeHhgF6HgKntrdBSXCja+hRGPsq0fw9OSWMg=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-38_1589925153651_0.7189979549277026"},"_hasShrinkwrap":false},"1.0.2-39":{"name":"serverless-azure-functions","version":"1.0.2-39","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"readme":"# Azure Functions Serverless Plugin\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions) [![Node Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Node%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Node+Integration+Tests%22) [![Python Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Python%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Python+Integration+Tests%22) [![.NET Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/.NET%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22.NET+Integration+Tests%22)\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or 10.x *(this is the runtime version supported by Azure Functions)*\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nIn order to run a Azure Function App locally, the `azure-functions-core-tools` package needs to be installed from NPM. Since it is only used for local development, we did not include it in the `devDependencies` of `package.json`. To install globally, run:\n\n```bash\n$ npm i azure-functions-core-tools -g\n```\n\nThen, at the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Integration Tests\n\nWe run our integration tests twice per day from our GitHub workflow. These tests install the beta version of the plugin, deploy a function app (with APIM), re-deploy (to make sure ARM template deployment is skipped), invoke the function directly, invoke the APIM endpoint and then remove the resource group, making assertions on the output at each step. While the number of configurations one could use in the Serverless Framework is virtually infinite, we tried to capture the main runtimes and platforms that are supported by the tool:\n\n- Node 10 on Linux using remote build\n- Node 10 on Linux using external package\n- Node 10 on Windows\n- Node 10 on Windows using webpack\n- Node 12 on Linux using remote build\n- Node 12 on Linux using external package\n- Node 12 on Linux using remote build and premium functions\n- Node 12 on Windows\n- Node 12 on Windows using premium functions\n- Node 12 on Windows using webpack\n- Python 3.6 (Linux only)\n- Python 3.6 (Linux only) using premium functions\n- Python 3.7 (Linux only)\n- Python 3.8 (Linux only)\n\nWe made these configurations as minimal as possible. If you are having problems with your project, feel free to check to see if our integration tests are passing (see badge at top of readme) and then double check our configuration inside the `integrationTests` directory. \n\nWe use [Clover](https://www.npmjs.com/package/clvr) to run the integration tests, and they run 2x per day in our GitHub Action.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","readmeFilename":"README.md","gitHead":"57438aec37833877a7152a223dad33c607ee523d","_id":"serverless-azure-functions@1.0.2-39","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-YRdkTr6ykSGvjZn5o0Iaqmrwecgjv1iU2gh5hIMIwqWIwDBfZXXME6mr/Q9liqNhdooia+VZRVfiaFeySzWDUA==","shasum":"3f6b643973acb65a2422bcad2e701e4ef94b3b81","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-1.0.2-39.tgz","fileCount":124,"unpackedSize":569066,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJexWf5CRA9TVsSAnZWagAAHtsP/An/G/ZE0x2VPcMSWOMq\n2OZlggHyrKLS3NTVDhuG/TzYpSavxCjEytmbF1JOUD0kQHAhCNo8CSi2Zic/\nG7XO0iVX72l6yuTiSeI/HGxrNomUSQPSMOw1xsJHLgwo4AC3h3GmKEr6vCpK\nE6A/jH/P/Yp0vILiZjVvGMFs+5em6/OWv/NENBydf5oj8zCCgGYaYyNm/e20\nxjosYzSMKqiuAv+cBVMIqV0W16rtQtJZLbwFV8Vf9Q/oxPTtAkJ4EIjw6IaM\n7rJCelrNeEKLmG0vL/WYkzG++iTgLcZZNVaLy7+k2ZeZjKnAtjfY90YicgHD\nhRYxdBfn6g0rgg1JFpMIbzveCZqhjdIdcGAB9qATGVRj8IDeriGU2+/fa/Fo\nVHVHsO94Xi8YvyY/boftxuip0tdZfbW/SA9uHCxVm7nbyXwXtlLE4RIvAy+K\nq2pXb6dhoHr42m6fnzPWiI4k5U2Dyp33ufMn5Jwja7MXSCG03PfMN6IsjdAZ\nWqqYNz/QwZJeK0+wjHi94ZubSSQ/lUIp/he3ZHv8NG8t2duwOLBkfxnypBYC\n1a8pts/PJdRBnO7R9EMuPOSDMwKoQhD3sykQgMWz6lJo2yGt/pfWGAonK6EM\nqVZZ3Urzcq7aTKOERDsdDtx1lshaTm8ZfpctTIVZISe2qoEX7zmJa0c3guer\nzH8q\r\n=1pxD\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCS5AYxPn/6d04+D7rqcg2JgY+sEqOdRfiYFOugKKlH0wIgbCIGL/6S+b9xiaRCJkXTMK8/stM4Z2GAHSbDmPJ9iqI="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_1.0.2-39_1589995512657_0.6609093321173061"},"_hasShrinkwrap":false},"2.0.0":{"name":"serverless-azure-functions","version":"2.0.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"6edcd92cd4f398efa202a9a20da8ed0217cf4c40","_id":"serverless-azure-functions@2.0.0","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-wxHPksGBcuk7iyRAB2BtFQxrbgYgydCVtVyHtt1cV/MkHb0YmWxqXZ/f1kCNAxtHKIBNXWhe3QuuNEONom0Xug==","shasum":"fbb1dff7ef7eed05ecae9ec3e390da88867e6af3","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.0.tgz","fileCount":124,"unpackedSize":569124,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJexXHUCRA9TVsSAnZWagAAKskP/3JFZLZWdjYjOLDItgWf\nFASbMBgMCLdnajukMqMTvoibkf5wwojPp4lvrWqCAq46Pe6otyRUxm7sRdgO\nO60nBE5BrC78jtEf0j2qyqBrGQ4ZT69oLFwvrrtdZ+P1H8uuxcSw3YN1e0dC\nHZG2HUrFehENRi5aaBbL8kpvRkTMS5W3nk4+y8LAQLWqqfZvtICYvloUhXZG\nAkagKs6lGDsMqTzEHJ8fKubB50NIZAWHPJQpRO4Xd3mPfx9M70t5TRrjtaNK\n78ZAmlTggPnSkaAwBIsJ/7JbdVpDkWFvBVsM7kjvFnvzqTksJdq1ENB4sSQD\nu/7tZrrnwCapSGFXXRihnrujY4birCOfLjTfJ4JmToeM4rGNImM0Kur+umu+\nSUJXRIFHAxU+W+pZVEUOsdCaKRZ15cs2R5BMkULLcEq43FxoumOGzZKOdesl\nahmKNWYmXWPwVVoaDTuXsdbQIeGsO69yQQKGkRrlokW2sFvmkolSSu5INwso\nndV9e7DKkx3SKQ7LY33RJta5NcmpY0VYFfaGTNuybujIb6gYZouo3Ut8SJQm\ntxf4YzKNzKSzgth+tJCi1GTcu6ujt+g8Mp2Hsrc5LPpFxNVO4ZsnvDNZeY1v\nNgBMrBAXfXlC6b3wkaE8qkhAIqlZx0+6JxfakoJXOH7yBCfWAGzBivk9BmyL\nbr8p\r\n=szZy\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIAN0i9Jfxj+HZ3+YI1iwlFRSj8WXzxItEyICrAV6ezvqAiEAsPvsiRGNtD94bFGk4wlMZDw3jkA++VQmhKrAuDVJAr4="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.0_1589998036090_0.940771232467795"},"_hasShrinkwrap":false},"2.0.1":{"name":"serverless-azure-functions","version":"2.0.1","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"e1a4988b1e6edd923be48686cb024e6ded9e3891","_id":"serverless-azure-functions@2.0.1","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-ku2FSp5PSPUNn32BM1uGGFh7NIgkfHBoAcPdVRo3pnvRM1cnez7uG8e85et7fs4SpbvEA+BMFQ8tI7jeGCDpUg==","shasum":"c58cc73af29d97758c025953a1f2048522050001","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.1.tgz","fileCount":124,"unpackedSize":599789,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJexYcqCRA9TVsSAnZWagAAmHMP/1yCM4sACBJUjzJ1a8Ym\nxPoLr9cOct408gPCiI7bu5C0Ld+ML+F/csT6RHoPVKaFkchEMEqx37EjDy2s\n2k7PeuPL0F7N6A8wLFbpALEs7vGblahEES35xWjOm3SqtxGq2ReiLm3I/vXI\ng3C0UfJaXRzVsPOhmN2g5dznH58CIR1EJctC7JkWXoapcFPeWWt6hDn4RZUY\nKWgb6e+t+PlF5ZUclikZbYC6HfSUrKBVbOPCYyrVs6UEGPK7IjC+LUcps+IB\nsFm1VAo7wWVRCsom6+rQDy4DTYZsVZYqgYe56OEXvvgqjRzGIwh9tK3r8pkm\nG5Q0z8JqNhQ0zWuqjJqWbIWrat4Ow17uNX5ktyHFjxdGdz+ctpl1csKvmdek\n2hI14KIku2yNniKVY50o1Mqc3H/LBNtAbcFYZR+HEdhjJ9jYExg+R9bxGHXs\n6N9wnEiL4FP4Dh9Pgeyx6KCCvI/aczMdnCke6rRLYdcV8qG4G7bt6nz58Xit\nd3OVDGmax4FG10bgzZu0YKXA/eyv5qq5CVH6K/YMACo4LE5wvg0sOG4et8Ec\n1UDJzLdN95gFOL8HEzuudEPn46Y+I/TlQrNlQr3p8OaI+mP67K2U6GO/q+lS\nqShfKaLe4oYnqLtJhHbm+KL30x3+zmlr92OKYUx+sBmz28ir1pha1vV5CAqr\n1o+b\r\n=tOYe\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCOwHoVjC/b4g5tcXB56VLw+sVAHId17FRSumLmZXYqFQIhANEGiJ5TkA2ov1JDxaluL5W5Ho5kNivFXLpEZm70e1h4"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.1_1590003497640_0.28510285802018287"},"_hasShrinkwrap":false},"2.0.2":{"name":"serverless-azure-functions","version":"2.0.2","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"c292becd210e87b2a5798bdc02aab194865df03b","_id":"serverless-azure-functions@2.0.2","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-UnSuyzUw9C5IsHpC4qr5SwWVQos5/r3C0TRDNujcQOA5ww8GKScZmukMKc2aG2ZVvp0hCvStpvy08TFp8p6uXA==","shasum":"7436305613dcfd36e90e94523cf4e65741473999","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.2.tgz","fileCount":124,"unpackedSize":599995,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJexbcECRA9TVsSAnZWagAA+XUP+wTkvA6EmiQzNUgQGOfn\ndVwUpAnMnPAVYOPPOvpG4aKXsVN+f6Slxlwmj2MOuRUbawd1vjjOwW2+NLTM\nBh2nlf0Z2yaHhuMJt0ngRxTi/BQb60/OnKtKRtbZodi9GkzIwPDgiSEk9Wgp\nucHGA45twvAw/eIrjS0iNC5cPj2p4cZpT/RNX4mMl3tvYZoauxeWssEG7KxO\nlJftE4C3wNd9QrR31tjxplseao5Iw2C+CTl1krf+gV91TTUvpp1t1mQlTDWy\nxim94zQR5lRPaIyZhsmZdCMZUzRpfoHa9uVLl25LwEfqZ6N6tNczT3fnO5zB\nouYBHMgq24liq4+D8uCfJqfCsmaHkKY1Pv6QxIn1N2u9MaWfTzOlbOVKKmYK\nwLiog9BewsKB8qILPNXaNpeJzC6cC9/D4LA5RP9h8dGRTDeDOHpPDNHzZZgD\nCXXoJ8FefGxtfs/8f6BI8pCNQN3/BPa2SaEaIe0i8bt2a1Pa5qejkGXN15SK\nGvqQniARv8DBG9OCCRbufsnbxkkzWlR3jX2kSUO4yC4+o6gr+iTAVnrY2A3v\nSPU01kDRI/Tdn5vh8y57RsmS2i1vBRe9YykNZiDjWkrDjBRsX9Cc1EWXlIrr\nGK82AEiaX1DA+MGg19HobiaasNehIuP1OCSey2ak2Gd1w+lkbfYfnSAE9Lg2\nsXQF\r\n=KySp\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICcBQGWUONe59VuXwHsJlYsR9f8XdXVHZnFtj5AgSAMNAiB2zrKECoSdX0TvoGSf0fziI18AdRZc+B3xPbJH/Dj7Fw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.2_1590015748206_0.5580678787181617"},"_hasShrinkwrap":false},"2.0.3":{"name":"serverless-azure-functions","version":"2.0.3","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"1971d816b91599dde99acd7e5a2c8d623f140667","_id":"serverless-azure-functions@2.0.3","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-ITgoHEbq7SOKej3o8YuAWniXLRlinqoivrL4wmH2MVSr/AXEsUvWQyXFtpbX2VoF7gy9WzrXPIrG4HMw1LbIRw==","shasum":"f1abb32ece600868a0a2648d0bda0e46bf5129a5","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.3.tgz","fileCount":124,"unpackedSize":599937,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJexnVOCRA9TVsSAnZWagAACDYP/2Sxd52Ie7M6Qy94Mz9R\nLIeSWwWB02XA3W5zEwfEbQSYEZrnIqm2/4tyB5PDSAvFA/5/J9FLLjVVIvTm\nW971iSlT/9VF/m6yE35TJU8XlJ/2zhiHvvMshuWy9/N/9TKp9oBt7KgWGeIQ\nM4sMMj1Ih8V3dvWXolcvNwUZxAdKy5o45UwUL4eDngB93TMhM4Z4ZTrAPd+q\nDfrTTBSLxQCId+WrAyXlEN05w7LjXVp2TbAF+VW6AtW5Ugd9Cd+wwWbrhGgg\nwP7myRp2hggP/nA9kaNr7UeBE5fqwtncQWoZEJbc7mmCZtLGcTUtniuZe9Gt\nat0+o9eLHcu/fRyA67N7zqohXAa3K1CbhwqU3gdsORE/IPsG1tdFKN2nN7w7\nqNGysDzYKPI9h8bACdWu1bwr8H1BkWDcuF1PwwLfvOmnxICJtueaY6ROlq8v\n1OGKsiqWE6+5pTFq21IL+dlNoVjkaVG23DEyLwtbnX7IELVXHa3xCB1xHeVG\nhqkTRKFnCrb8s/yhjVLZcUmsf8sjSe/Q7F57kutFUe0VFP4PKDFzGSoO2EU1\nUAy718jfw4CV/uFJncEOK1keZZjphcaia5Jy+oKJIlNGBvIePNEPaOCABNNH\nSwLm7NvFPA4iBWfBZMIlgty1js6EBsuevaK3H3ZxVYrBx0rQpSlYNfBvmaD5\nBbEf\r\n=IQoi\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCkKWZxNYfRN95vrfXnwOQ5lULdtoaxux7po998dFzk5wIhAP0QO7N9cNf6B6QX9kaOlQlPogGtEp8PYLti68HOoMJq"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.3_1590064462296_0.5488218442394366"},"_hasShrinkwrap":false},"2.0.4":{"name":"serverless-azure-functions","version":"2.0.4","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"743fc42f1b40c2ef665810403f0fdc8d425cd895","_id":"serverless-azure-functions@2.0.4","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-heJmEjHmINANS2yt1pjPIspfpSEL6HjB/HD1N341HIwsfo8rd+6tAnhrlkLgj2HDRe0QGdc5DVA5PWSe+ZV1Gg==","shasum":"198a085e50cce3a913e1443e02d6ecdf5d222653","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.4.tgz","fileCount":124,"unpackedSize":599709,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJexq4JCRA9TVsSAnZWagAA+2gP/1roHVBNpHTlpkhA1/3d\nuRefWONDkb5Ht4nDzTuDcEP5PO53SQ4YNVflvI1zvmHw2aD7nbSbRO6RfsW4\nSoEIBb98GZmbMDBs13KFnDXd0Dn4n7TDPPjxMLA1fTCPat9QTMz/q+6vrUFt\ntL1TodLR/iis0UyuMqW2fUqiUfQikAKu+cyapW+f3RAsL4zmJ4HJLBrQpWEh\npdgNC5hR0M1SsWct6jSmLghY20+4WF+RfKptyMX6kQ7zOe9Ar+yCYzNGbunW\nWun1YhCJqHJzGjlsI/eHKnKbjAhwj1cIiczEPBeeQoLfvEKjhBg8T0bmSxd7\nsktH+ds1FVmNCL5uANPXlzlg684DtQbAuLPpoUvapBlxKZFaE+Y+ePlDOIiL\nVOhTcjkM6aLMMNtp3QABmi5OAcfpdPLtxXAx0pUeRimvzDAg/81voZ56Ttq0\n7VkZictOxMbry0uKrhxoMrm8RiCBJaqiF6KL86dO6R8rBpSGBIdLsBL+K0hw\nr5m13d1c7pOB9v3hRLHGb8FLKBx16XhMAbB+S+oPI44g6pwvb+uw2yEtE4CN\nvwNeU0OICuIhXpUh3K0aiEEJzFv0AcF2tRBrgeSySHWCLz0n4nPB3kR1mP3D\nVtgJ02C0nYLDzwEaZtUGd11Nh6x4YKfF/jXq/qCUpPGjWO4IaGJvf3ZHp03/\nf0EM\r\n=cBZ7\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC2I0DL20OTfKZlE5T0g6XOaoqfIOUnI+ES31aMMJ4hEwIhALJ4TF5aDePNgtbSFw+SfyGdk7l+Jd9jzofFR/AdWvne"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.4_1590078985164_0.9755106587558062"},"_hasShrinkwrap":false},"2.0.5":{"name":"serverless-azure-functions","version":"2.0.5","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"eeed97a48e4c857134c3905d77a4555bbc44fac7","_id":"serverless-azure-functions@2.0.5","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-eZi5EgXonwumLfExkYi4Y8VBa7mhQ7pg8jiZPAcB6+3wInH7QAIutDgVKkDhiWvfwOzW0DywYTgbZlPSfMX09A==","shasum":"f12dbd41ebbf32ee4349c19b0e5ae60634fec2fd","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.5.tgz","fileCount":124,"unpackedSize":600034,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJezo4SCRA9TVsSAnZWagAAnT4P/1LfTx1nMzVRhO6kQS3s\n13QkZsR2l85YJ3SyADawEfIJsUVMfKlwLnGtyi2/bYYs/1xIK1RW6higfrau\n48RCzuutBUQ+SsNl9YLWsD+IWFSkiGbidxAcLAKmfA8frs+tu8qIyGCA4f2A\nBCaDND19w6zcXtTNEG89q7/ztNnuh07l1x7HOylWrHdK9uQ6j0u+Chm69xms\neJUCMDu2JnPS7ulFoTKhUoBna9/YXhovFlZ+wdiPEUR67n3MjlEqh59Ir9e/\nSbWjI+HPeGnoIlvFnRTt8sq1Zno+eEZik8ikoK+G4ez1SbvXwpGINm14IXeH\nllk1OUHnP/PmkJ8pmUfYXUS7u6BtwsQIdRsiPVMQB67SlQmFiGk3aiIxZqlr\nHjIxvWtyBrOjkG3vc5bxfvWZtzW6qsINPfeP5HJWvO0FvvhtfIijQBOpVryI\nQXstpPvtQ6zJC74SGifioZ6slt9XT8f00DM3ybrUOenqhU0rjHs1cxtAUlBV\nCnVCMGRzV2OHw7mlrVH9hs2pNsWczenLSMH6wfKkD67GCvoO2HPPSTZxgoBG\nJnnn/zQ+hWz39gnYrqd0GGLavaFizgi/wfCki7lWtupHbbhW9qH3O8SayR0l\n2ffsZXtj3X4FsjaYXagOPeBPs5X1hE5a5vy3MiLABFVg61F2dSicaNcl4L47\nQOUk\r\n=7qsb\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDae/GbJzDIJu/LNrArpW2uIYq6QMasPUdCEpucs+pMOwIhAPys8sRG6HZ5J8vA2Je6Uk0xcVW9YzjhD76oKI9ekImq"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.5_1590595089586_0.8588224146478327"},"_hasShrinkwrap":false},"2.0.6":{"name":"serverless-azure-functions","version":"2.0.6","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"ae851fb0e07a8263d2ee75a601494d45d9a8fde4","_id":"serverless-azure-functions@2.0.6","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-dIYARIqLpyY1uEnRKM9IwMJ0PhvFIYmDTKBLvTx9glb5cDDTOjqKOEqh7k55lc9b9Syv9uwKxJxrpt/zlh4vpQ==","shasum":"f30a27859ab44dcb3455a86f9bd07f2e24d1ac49","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.6.tgz","fileCount":124,"unpackedSize":600062,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJezpChCRA9TVsSAnZWagAABK4P/04I4D/i+2Gv8QG04l2Z\nSVZgsc7ot4nu7Ur974d6INkTjkFUhfScYEhirO6wZE1R/b6q4r34aJLUyeCl\n+b0sg6FcIf+74dYB2SqDp1047F7cdRN0A+obl9Ug7ftbOh4QVBQhAXEvplFx\nrI0GcLdEt/HSptkHoGDP39NPqOsUOvCLzXMimQWW5S6ajQHu8z8Mo+0p0MBu\n07zRcW77smD7QKsSGQCnIW6vmot6MbvvyDFAv/7CiXNNYyHkkwgQbiGuv54Q\nX2c1MCGQ/Ya2VwRLlValxtKryTnq97laQLa1bAtNjAf8TkBvvNbXXXtx0Kfi\nUHfMvy2ZDFCLXJUHluhuGntpBeSEm70vmEez9GzArVC8l5tj6vEl1HLpJvtE\n0a8ktvcogLk8r+1sAkg896grcHdSsmfBLotdYHEz9ul2JmIGuy/MFtphev5U\nnIK6N1HSJDCRZ6TrzYMX3YMia/JWtkF5JAV5Xey1AIRTCfDvEHhw94cuoMRE\nvGEDNvhfauNjf6OKOQUuFd5ahgBwFLiHOeBpmoay9fkyAINyJKb02Zznh1ut\nld410sNSQY7DQfj/upWL7mB64QcF6h7gG+unZyRiQouK95iifWuIHWz5MIWk\nPoUYgTMC3U3yrJPvQTy6bhlMpxXzOXp1tuzuehkUl+7+6g8sax6gOATinsie\nFgzH\r\n=EXLJ\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCID56IRR4ao8jFFbq9IzT7Ub9MX0WMQAd56tAjcvJoKJrAiAb0pwHgrySWFHURSJax3hE7PaoZv6uvEOoy/bZ0m/KUQ=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.6_1590595744921_0.3472298090632895"},"_hasShrinkwrap":false},"2.0.7":{"name":"serverless-azure-functions","version":"2.0.7","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"17a6bdc811fc1f9e17998d028e80ce2532b9f8b2","_id":"serverless-azure-functions@2.0.7","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-C5mnyapYMr261QQbecodtmVMFakr1juQsrSLUevNd5ZRPp7HlI/zpHlK578Z2Fmen94i6CsMPp0TkurddggwDQ==","shasum":"379661a430de5d33a2234ee68ded898b7cd27b5a","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.7.tgz","fileCount":124,"unpackedSize":600512,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe1bECCRA9TVsSAnZWagAAU9UP/3p6k/oJ3vyVJ3NyAwIw\nMBvR/SJ/DV+3GeJEaCHkTTXsIsZqAOvFLNbd8cNpsYROn3oDMzEtQhCTqaXl\nTTfdvCJNOyVF9NFgul8kqYnk+wAYeBWCqewGHH823OzQlLI/80JWBl3RYPvr\ngUL4xRj9yKkpbrBqjJRJlrKGyl9xDPf+NoElvpHegNWSgPKkxATJAKecO2kp\n2sEtUGa1BVR05JS98d+Ngv8JpqEuFiS4nUY7qwyYiV0j0H8l+V8nLULBXOB4\nrYxXXZtm7MJbvxF5fQBZM192sGno/4fSLsqD5dZXD7R1Oq6YVZu60ZMECUOz\nXvJ6oFclviAdUXWYbq/NZi+43Iheft2kwZ9aRRNFz0HihRiAYvOaKAR2gNoq\nu4FT7zd4fXDW2XDqeFDau/CcpYeAtRXbQCUC+8wM+j/xmVMRKqHJWOdQLPiK\nijHVRR7bVMqLK0J+MviRsHX48Ysu4Zfikc/woAtlRpTKIc+p8ddzX1qzn1bZ\n9/oD7zpaQKJNrgY/jaWXG9VM33Sb70Ni6pdxziSFi5rzS6EBTwJEWnigrsYS\nje2dMzJ81x++pDF8jjquuEGc71v5nXQ8/5yAgPSQVEoGtzLyo68gE2QlNQLt\nyowbBD4wVaWknerja+XXjADBExTejvnYHzzgpuPolOEZ9MYk0tL8lHW1wjNI\njh/f\r\n=Hu1G\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD1YKJeSesVjZQO+ZiPsAya2KAwm+5S7gFhqKAoWgGwgAIgAQ9SvHWJxIF/15QtKMF7EBpBMW+P73EDpNn9s3G8gLo="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.7_1591062785470_0.0595472348539523"},"_hasShrinkwrap":false},"2.0.8":{"name":"serverless-azure-functions","version":"2.0.8","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"f9065e646067d2f90cabca6f39ea6b94f8a1f30a","_id":"serverless-azure-functions@2.0.8","_nodeVersion":"10.20.1","_npmVersion":"6.14.4","dist":{"integrity":"sha512-xbrAqJLW9Qg5538jEOpSYBM30Zu04YkqAidPK6SE+x+rrKMZMIwVT9+/26CmzxYACaVBwznt0viWWA1qUUIqDg==","shasum":"860b3785a1304a5e9e656a3784a080920a63d468","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.8.tgz","fileCount":124,"unpackedSize":600512,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe1kHUCRA9TVsSAnZWagAAy2EP/i64b6Z0/GzWEfnJ0wid\nMEkIqhFg2arQYoP2qff9M71OFSTCjqkFd6qQ3xHu+1k/Iiu5zoIP87LEvPdE\nBEB/lB4rlOBLAbD7VrqXvaNJJkZ/K0VOTm6AXeVIHYSYikwKdkIGlYBpBGvu\nnHAlf2v2+qV7lAoxydO+/As9tlI5EVFxDsJ1KNJTaSHt1GSOTrfe9sRswIH8\nP+JJcd/UEFJOfQ/gI+l1j91kdz0tSZN7fKiNcPd9HDnZOl24iVP8T/YGzDN8\ntSoYl6VpTBaJgZo75kmE8EyKZfaMabBZu8VTD6VZvXTPVsluPpa8kJpzg60t\nMHlRboeGBwOFePITfOIspII4WyaPvtxt+T5uJ1ir0jh2Fex7hAHAymArzIgO\n3G+YNkAkDzCZSVUKBArW7Ecvlj9aLTym5um9hS/HYEBpzOeszu8lzOPxQyfo\nVqg8hHutdym/jSxDatpGoEuyjWXkJV5bDv0/KrpjUyJeRK3wDLYySFUJXFSF\nCgqXkGpKB+geBwAZA1ke5y2fF7lzbdMogN0GGpOyo1ugUORWTPRPph5Sn7ta\nIgoI3VQRANmKuPEC4FdFQSxntlzVp/vBC/7c+lkxqFR+92G6+DIedXIWFXDY\nTSxIB+FzitBhnAtKj1+beVt6XpOf5TyPgCD5m8QVzpfiMaqi2Y9NgcJIIWXE\nWWzO\r\n=XfYt\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCgcmW3qWcnZL1TM3hoPQi6CfZwSDFt6mwNS18p36unkwIhAIEclRUCNW3cmXQoGhlyfUZTKfMmbnxHXuheHlUgYWDo"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.8_1591099859102_0.4319589412635172"},"_hasShrinkwrap":false},"2.0.9":{"name":"serverless-azure-functions","version":"2.0.9","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"5d9fdcef582eff91827f7e3264bffe0e29e78465","_id":"serverless-azure-functions@2.0.9","_nodeVersion":"10.21.0","_npmVersion":"6.14.4","dist":{"integrity":"sha512-FsKhcgBBqhYdEubJHfpidZMs3wqOV+lsJMxRYixt4jeP6y1+mMzmHadRBemjcg7jevW35umPMrfD51A51Z3+7w==","shasum":"5ebc3cf9024c63c0ceed5327e7bbd4ca4e66ae39","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.9.tgz","fileCount":124,"unpackedSize":600759,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe3v/+CRA9TVsSAnZWagAA66UP/2EVUY+PpeTs4OpznYhs\nFsO5SuP6RCIyXM1yY8aod7+MVNrNDJukgp3UaByu7AdbJCi017fhr6YuA2ie\nBGZtMgPS54usFoLmwpr/qwP9Vl8kCiFMgoaChVEUUpeFtwyih2Ub5ipp45NY\n61P+oDtpTP9sKv55N+RTzeQ71ijKaYdUfIBGexoZbcfTC9V/4e/gdVrQml4W\nMCmIOQzLJoxf874g2KhRUSyt+Yd04tgxpkwvcKNoxnEC5SKTeBv9dySXrhSI\nweYna6ohVO2C6u0/ylqq2mHlM1SUDf+qj+SmzHHNgTzZv65Ej7t9kWGxjdEV\nOfPixpLIVSGEuLZqpk4fpFfPbRYJDpi7qgyivUnmCQhy9n2uWFkKk+Lp7tDc\nrrjE81CME2su9i31iW+eem/vK4QmglsPmj/id6dKK3fUqh9vFj5n6NsViO1l\nTPyFN9LivrbTfRhbiQXJbM8ZDj7zfX8UBfC+P3s1F7c1I5ytyjZzQqHgU2c5\nQ5R8S1B8Z/mGWVpOGTBbZfPg9fLrBt3jcS6ZR5ZEg2LBMvXnw1GdCTDtMUpN\nhvaZNA2tyIAauvkt+Ff5NiSKTOXJg5/Htt7bl58IYt5v8iGWmxoKwZVf3L8r\n2lDzijtCw82mJrFIRd7QqkFbJ/CndTny0LFnFHpUBX85HqIROT364z6vzM/s\nQZMM\r\n=RRtO\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIHQeksm47GntzNm1733adzUXiQMlVFu7Y9GYtlsezS/WAiAUVv15/C9cTo1kbsAhQkXP1OAI+3sMplCJZSXXYRiBpw=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.9_1591672829703_0.26203165896763525"},"_hasShrinkwrap":false},"2.0.10":{"name":"serverless-azure-functions","version":"2.0.10","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"7ea0e1cbd31a4b1fa302b086c0edca38c6910600","_id":"serverless-azure-functions@2.0.10","_nodeVersion":"10.21.0","_npmVersion":"6.14.4","dist":{"integrity":"sha512-eYmhDYngWUNyeoXUOzLwqH53vSLpFVHXX9B+A/OSnjEYcraZbsLbFtv42UmIuS1SFHjNrSTLAEsoBSTZ/JBVDw==","shasum":"25645944e5b757d784234f24b870fe8a92536548","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.10.tgz","fileCount":124,"unpackedSize":600760,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe+naNCRA9TVsSAnZWagAAPT8P/2hBfme9XizD8gpxC3oQ\nkcygHyQe+46GJaazmKYw+YoB2oznWhCTsU8juZ2TyFzqeH+yvj4RLQl+XVA1\n8aObDRnp/yKeQxRXGhMkOfgUCqsyxu6+OdZSPJcBCiR5Jij2eELpeFS1FxrB\nx/gDHsgnPEGJoiFWKum1G9Vs/Z686bboz26ajFucnSVWpwqmSGuZX9JxzGqi\nfbKmyuOGK7unVy40c/RMpqZJ295hAzZw5vLxlpxqJrfTAej67f2C0pbrsQIJ\ntpqC5OLQUpQHqXxx8hKP3siOK6lWxsNaDDR5tT+M+TadMh3SPEKxy+rNkUrh\nlaCMPNJGhANHZ4JI52T617MZ4/1wFEpd87N6klJwxHTjgTHiEaMuLeBKOnNy\nwY2bV7sLkcGzDeeLfI10WyQPdczETLWVVsMGwvWFuyghBInn9KQMZIPl2GH/\n9SoiaSqW86457+v3IjFMf2c0obaITk6f1dGd9HcK4YoDd4SMaxXza2guFTCh\nbDrk90CcmIQlYG+h6Q/8ierrDIhaFcoiNNzeQh+EMQt75K4mGjgVKI64u0JW\nFXyiB3SmEWHZIXVaxKKVie542JGtY4thHtmv1hpx7Cb7zh2PlVTDySPbL8ZD\nV2wdOP7Wl8aRC+mf/HqzQeXOusV1Ywfiq+3ygD2r9lPAw+ho/yv4RG0xsuG1\nfWKF\r\n=Cr4b\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDGvZ8MoiPz0lvyGy4IZoolAb/UAuvw2WT6Sy6H4NRJcAIhAMIOXelN20NZs7FqDd+1q7Oh8QBHcKV2+lvC3NOOv56C"}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.10_1593472652514_0.6773931489719929"},"_hasShrinkwrap":false},"2.0.11":{"name":"serverless-azure-functions","version":"2.0.11","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"82ef10e51b2a36aa06a1ad95f54a079bcf804bdc","_id":"serverless-azure-functions@2.0.11","_nodeVersion":"10.21.0","_npmVersion":"6.14.4","dist":{"integrity":"sha512-ByAa01Rgp2T/e2rdu9Aqvs02ibIMBWW7mZSnjpzChzQaTUaD8n25luNbJgKD21vjgjxIZcISUK9kKNZpWboO4g==","shasum":"79720a28d0a4be7546bcb3b7186d08e88ff8e924","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.11.tgz","fileCount":124,"unpackedSize":600760,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe+2LyCRA9TVsSAnZWagAAVIQP/3XCD4P3nc/GbMxsOPMP\nUvhJXSAPYRtyvjhwYq7NmEinIRmlHLbKFdnIDFJxTp/m/Ua7lo/04cpamgf4\nMt3rkaTnlYQ9/Y8nhxRcCORpHaf/2NgI5FlovT9LMJw/Sd8NPK0jKEONFCzo\nNT+xm5jMndEhM9fXXRAZFCWtow1ZUpxr6Fo8ASyJwozYth3ZdL1fnQnKeTkX\nn0+Ui2n8PQT95j/7uPxhtfVjtdU3mQuspSXON8uWZn39HipKU3dmodXtSsw0\nQkKBS8Ipd69MIR5+GExJ6zoZ53tJNwBZrh2zYr5DpPQxkEpWA4dj6wRJumCU\neq4wCPWVykC98KCzR9BaldihiPDfO98I/H+i54wEooIvJ8zweSEc/8ixLS1R\nqbchOTVRMGFv1tMsX1SMU47llsTXgqmXYXmyP2mXxbRqgBDdqdh+LSq7tdtQ\nRLsDb1/uvKMvzX9oEHbwFtyh0cIAhZ0mENsOUzNuIO+s9qeGYeQie18g+9r1\nHAEIGSZw6zAgxtxKf/NJK3112/jMb83WFLXEvmgDwOA8Z9rmS13c5jB/8RkS\n0dnlChzgn8KcZHQDrUtS+0E0wF5IR1c4m+5g/2VUI5CjqFD+PrPj+EYdNNUF\nz9k1H8wQDJ/fru9R41iueLlUUjSJiHdYjaylas+hu6ZaJkM5tOyRvwrLuyZE\nfdd6\r\n=2C5u\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGL/Rwe2/pkRyQE1ILcBUR4sfnRUr95Wdsomcj+dJImDAiAEtv2k6X+NVtgbXnM15EWGqsrpxnqbD+Vy9wy2nOxY3Q=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.11_1593533169826_0.8274759480771168"},"_hasShrinkwrap":false},"2.0.12":{"name":"serverless-azure-functions","version":"2.0.12","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"d0d90d32183d34f6df4f640b4307c748c04cb9ea","_id":"serverless-azure-functions@2.0.12","_nodeVersion":"10.21.0","_npmVersion":"6.14.4","dist":{"integrity":"sha512-nfNGrB+hjDLUsHhi8vMsibzyE2Lz+Onhq31u0fXVHliJXjuAB7XQL15UJI/c8dGWVklYrM1ykMv5z8PzfAa9KA==","shasum":"55744408d30aec233a748424b0135e194c0ce590","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.12.tgz","fileCount":124,"unpackedSize":600867,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe+2VsCRA9TVsSAnZWagAA2cgP/31ajl2BrL+K7XyI6OH5\nH1N3t3ANudP6E7GW7onvnHEVnhseyvcwtsTesj4YDfqEotWXSJFQOfSUSXN0\nZNct0I0K1RbJO81TTaNMod8EbWzuQcsa+Ml1JdN1CTmdB87R74s5q9iO85vy\n4hVdF0hY5V5SgeFatht1EzLyOqUVAIigLUsMNt73q3YPy/E4oRqA+hGts/Rq\nQmCzCS/fTi9RmoQjBX3y2tRioT6tZqhpamFe/t7v5h1BXfNowEOdhHZwuE7x\nEO+CZ8b6OJ+5p5c1+or6O8HSUwjhhZICXxwSKwQ1xdJBrumEQq1F/IJ3RuPB\n2nnSNrLjh7t0IasGsrsnwDmvsm8IeI/NDgsEegM8UkAnTO0o4TvB0IqQna6g\nlJUE5AGkOz6yyMKIjTeN5JZdNwdgiCH/wAn8lCiBUrwvq6vVp/sbRK9MRbwM\nc1RHTMyEWI83iCpxN4WtUs4IYqMxskTzEfqyDROYzIQ395CkPuZMb8ghWIxn\nXC3Jm6Qv6fs3K4AhBvzCzr/ufEO+vGbpIbFiQn1I1G8NxKxAAPj7tpJUrME7\nSfgGIcElSESgXo5zF5EsFeqXe3/k7fCbHKOd7DxyCC64IXiiEo/mfcjrScGO\n1uuZ57VanbpFOlRkv7Sdf0cBeFZCx1T315ber2WKYTvjjdOPDfAFwWsAmdpN\nOl79\r\n=ZPmV\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIC2L1vym949t0W9z54xuNKnXa8/eHchoylfLfLSSs1+4AiAquTcNYm3IA/4m9nMlCXAmir9ru1EYRDwo1ndL8t0g3g=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.12_1593533803990_0.6494221970473073"},"_hasShrinkwrap":false},"2.0.13":{"name":"serverless-azure-functions","version":"2.0.13","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"37cecf642223dac11864edac8a78d43d53f755b0","_id":"serverless-azure-functions@2.0.13","_nodeVersion":"10.21.0","_npmVersion":"6.14.4","dist":{"integrity":"sha512-y6VR3s6bcdgVsToPhyjwz8C20kwZVDuBJOV4GF1E7nKyQu32UMS3o4V6uzo7rlLVkEj3xJ2F3h/U49oWHAgeyg==","shasum":"767c5a5969ff9aaf34c82dcb3a6c2040b8166f5f","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.0.13.tgz","fileCount":124,"unpackedSize":600867,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJe+4P9CRA9TVsSAnZWagAAO7cP/jJ/Om5g2+VtbDHQV8rc\nckhmQM5SgtOZ8vTBV4EWMbVfjiODtfGTOhB6j4gk4qTEMkV3LdeKChP4wvqV\nK9WIVcYb5oFnPCejKAgpfPfa78IGHI1j88MmFnRIZ4YSR65Udp4bES/eZPm2\nNaIG5u2+IDTLXRSch3Sh9dTqaWDMBzQZBA7uSa9x5EDdOoHUJn+BqtUyPqmI\n1U9pS3wcd3sjYtKQIrCNpnCz9YjwI5sgwhXgQMVEN00mjQpos1Ou6Y2clqrG\nGhuZTtWJOzmkMzwQ6mHvrw5TgyqRc/tok6MKtq6MfHOBF7117fbsXkW8RBJE\nlhzl7z09P0oXBApSTYKk2LWhE4JPfyB8aMFsCTYfUFu96L/acggpLfx4NThR\nHVAMJVXeGMb4K2xO5smXKwtquqpf+lWsQmY/yZEUzzGa2eStUuklOoXHa9PF\n7BiPUb6pqRudN5kLdxXzsgKkmke+vdQ3qkgFvnaP7Fierr75cleys3xKe6gi\nn9B0Ov719XAUfVGOTdyWgyeRX4ZnHxBD2dLN3ik0FInWvKQAjVTTmDA/Phbg\njpYGHZ1SieRGcjoGjhYaJSh9a7K92J9YbJWftJz+cB0du1TlLxoRLGK8FwCi\nBLG7+w80jvuNrSLY8L/GxDhudO5VV55X3HVT0P4cBknoXQrjQRL5ZjCgQA1V\nffV8\r\n=QoVh\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCz3KdKcYFSeBiazWL/Bmndlq3aPSIOP3NG6njlmofZqAIgcwRYAfeDpW9Y6dg3xJD/YcKJXeaRQfAEv6+Srb/fnyM="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.0.13_1593541628922_0.5193618308760386"},"_hasShrinkwrap":false},"2.1.0":{"name":"serverless-azure-functions","version":"2.1.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"c53f535204c467339e8ae1f6edb985c3280bc32c","_id":"serverless-azure-functions@2.1.0","_nodeVersion":"10.22.0","_npmVersion":"6.14.6","dist":{"integrity":"sha512-G6oVxok324y/c481IQL1VnW7CWskWdz6SST2Z/bQq+hxKowNuXpTIKLSZSKI5yGoFQbytSTx3XY14yDunrsPPA==","shasum":"377eef76afc21f0dcf4cb4f1ffb3c683f65ca13f","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.1.0.tgz","fileCount":124,"unpackedSize":601132,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJfSTdJCRA9TVsSAnZWagAAIhMP/0cHMAEEj2wt5a5R1BBx\n1N1ETSQ7eMELFFcqtw+k/6RPlq7VNPSZzkotO6lNTlqW+QwvwhtC94bcYnRF\nQpKQyHjKCj7dKpYI/DE6+jQrj7bhsPVkjxZQWAO3AZzi0zpAa2RnUJb4b7bo\nOQRjtTCbs61LO5HLVq0q3ZHvPRCtFX1LkGh3ABoDbu5SxDJOym2WAqfjEEb0\n/IBh3bN9XnHtNj9uLvvko9eaRm5wZcKGMeKuwUDyCYb7IpiaLk/c5lHZwaUF\ndH70/WsqPUqxgp7bY+kwhNS68HQic3P3YBgTlibChzo4VADoG5GAiU5WNieq\nreibkNYM8XmZxs/W7bYZNbJzw9FozvM+8gAr8XEYLpfERaHa67clbJCXVVWo\nE0ghDwCJqzRzdVJTwuXuM+lCItVzZvYy+Agls7VDxPdAUJNSN4ggbCkE66Fx\nREO72JYtiOB2f89970BiXMiGlrtg0ejcyfP/8p9NEt0wy3IJvs/qGRl1GGrZ\ndVcHYypvas3UEAnuMUkwZqRZGRnVWpTSu3OcCfjpAhrJZnq2WfEiCCzfLWzP\n3m1hQtgE7siUjjIEFrztxmXkr46LDaejjRplIlK7YDbbnuBRjxgP0bqonafg\nEbGVgoz3yvZ+AGaOyQgXUxXOeKe5BC8scrGzthXyaeI39YF1K4A+bGTENXZs\nthM+\r\n=gCdP\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDaMsgE4isy6MJX/npFyEf64G3SHthx3vggL6PwZfcS+AiA1E6YHGs6wx/v8xO/JT4Fb3YiwCmSODjXqXwDcV9w8ng=="}]},"maintainers":[{"email":"chrande@outlook.com","name":"christopheranderson"},{"email":"maherna@microsoft.com","name":"fiveisprime"},{"email":"jc@trl.mx","name":"lostintangent"},{"email":"mamaso@microsoft.com","name":"mattmason03"},{"email":"pgopa@microsoft.com","name":"pgopa"},{"email":"services@serverless.com","name":"serverless-main"},{"email":"tanner.barlow12@gmail.com","name":"tbarlow12"},{"email":"azuresdk@outlook.com","name":"windowsazure"}],"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.1.0_1598633801212_0.6178450569281373"},"_hasShrinkwrap":false},"2.1.1":{"name":"serverless-azure-functions","version":"2.1.1","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"b837f6c520c276ca630c686813ff31d0898d7424","_id":"serverless-azure-functions@2.1.1","_nodeVersion":"10.24.1","_npmVersion":"6.14.12","dist":{"integrity":"sha512-rBoDLFRWMFxT0Aq/G/8nQdYzQD7CQox5GadNUAA7UG9Mfij2WYN3fA0usoSedbHEMPcYY6VcSGn4UHktmVD03Q==","shasum":"4f37efde615a34a82eb2faad9b21992a3346e6f5","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.1.1.tgz","fileCount":124,"unpackedSize":601360,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJhI26TCRA9TVsSAnZWagAAecEP/RKSaTlgRpSN8exvQh5m\nTxVADrnxOf1NNbi6uneUSoVk4MjX0zGToetchT1hzH0te7BLhOg8xsBqUMM7\nVtYnNz5vXrxQVq1A+qN/i25rXoDsU/KqDdOpPxOkVoHflsKDq3fX2YlymFE0\n9V9//cEvl1i3kRSbDbcyP9ZBjLq9EuoK+oRdLvSQuR5xKkkEsijqdGg+AWln\njUphfxkbWvBh+GsIQ2fiFSr0N+UU6nSVusWt/gBj36/Rz3cPmewH2FRWlFzi\nIND7O9MQAu9qg4KoUAMaVhm40QxjL8k95pdor15xQLcFfFvT5egpVk0N9fF3\nBFJ3NJhpex7mrWcHzf8loeqjEtyVj78KuMhyVdOW0EgkVVwcNBIZGENzcN5W\nqDyaznrJ/a/cxIYj/0yeYGI2ViR9yihFgwFuu9Ajoyb92urJ6MZgy7l/PgJb\nZVje6I/HP7mnN3VpwH88M+VnAGqeTlnMrBTWkMj9qjW78ri+EeZeAVnP0qvC\nuSO0ZmfmUSaXL7z0+jwfaCOSwNQwy5JyrzD6E0BYGUtmRDtu1XzGk0/UQyPA\nIYvxjl3swZZojcDhnxBf4J7HfF3lK32RvSWFXxLubvTVgmNcXhjvEJZ1u/gE\nAi2tPJ0NDXwiEEZ1KL2ALg+90yjO4zCb8ZA/nJfQSSOQ1VG4WsZohcPmCVMC\nhBnB\r\n=QAXs\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFcR2FwKxyuAC90CzzUufdT7MKeNwuGSLp6EZtXeQtzPAiEAjrsM2PdUGY+oZHio0gw6E8FPGIOQvkPfx5qwiNYkJrc="}]},"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"fiveisprime","email":"maherna@microsoft.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"},{"name":"lostintangent","email":"jc@trl.mx"},{"name":"mattmason03","email":"mamaso@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"tbarlow12","email":"tanner.barlow12@gmail.com"},{"name":"sls-az-func","email":"sls-az@microsoft.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.1.1_1629712019278_0.5143233171131338"},"_hasShrinkwrap":false},"2.1.2":{"name":"serverless-azure-functions","version":"2.1.2","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"74f033c965eba8b81f3d830d3072342981b206a3","_id":"serverless-azure-functions@2.1.2","_nodeVersion":"10.24.1","_npmVersion":"6.14.12","dist":{"integrity":"sha512-7MEeCkDBu9EkcGBrRwhywt9XxWZGW2gUoSLASPnfg+iyEbxTO5vNMoMGzxmAQNYwxWHqFoG0Y7Efm3tpL51zgg==","shasum":"cdda9c6523bb8eb5a95f33bea7e54869ace040ce","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.1.2.tgz","fileCount":124,"unpackedSize":601370,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICMuCoMeTrKMXyw5+0jPBN8fEr02pmnGR+l6eFLoQ/LOAiAR5IEfvsYW8gJvxWp5v7B479Q/PunkEyf9NpnAp9vzrg=="}]},"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"fiveisprime","email":"maherna@microsoft.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"},{"name":"lostintangent","email":"jc@trl.mx"},{"name":"mattmason03","email":"mamaso@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"tbarlow12","email":"tanner.barlow12@gmail.com"},{"name":"sls-az-func","email":"sls-az@microsoft.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.1.2_1636059370650_0.43364787071468824"},"_hasShrinkwrap":false},"2.1.3":{"name":"serverless-azure-functions","version":"2.1.3","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test -- --ci","test:coverage":"npm run test -- --coverage","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"f1c480f65d2cbe4f4682d2a154e755cc651bf7d6","_id":"serverless-azure-functions@2.1.3","_nodeVersion":"10.24.1","_npmVersion":"6.14.12","dist":{"integrity":"sha512-SPp10wUPDZ96e3F0RPKSaZaBjcaZ9J0o8uC24kHtxgflSxPP1zrvYnZcUmrxJ3p0FjHu1jRXnceeWNdTAYooqQ==","shasum":"e27c7f1a87eba0c59b0c037d07debb1c94e1be4a","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.1.3.tgz","fileCount":124,"unpackedSize":601516,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJh26vfCRA9TVsSAnZWagAAEAwP/2WfSMiqjmbxk+Dlvdw5\nRbj9YqeDn5UmnEDuc42OZoe4WL3P8/dL+vnagfMpEP9nM3TsHhpQdC8k5Hbo\nzvSHiCvWpW7n3HqsgR2Z9FKnHn/3GM4kktSWJDWs9c5SSe9pOf/a1MiLKKlL\n36jYvoz8sUx3OMaFb9EaLASxhxk8wJomGzr1pbSEEsPHT6NO9Bzs7FeUHjmF\nhoK+2zl13vp20RSYeFW4OvAcvvq7KVGBNVmQpgjCip9hvcpouhyBoOkmbP4o\nh/J+D4GDoYZEXpo+kCNdgrVJWTmyNGp4cvglDxk0ta/f/hLds9rW6qlE8ZvG\n7l1igWeMeRaP57tH/SjppHHOpImQiaAJ2QWOeRBUhVE+1ahtiHEHJHCnq1LC\nB4YcpUcRNLYGVy9wxNqlpR+UAefquNbw1bR9oqZQ3TwmvZ7/7av0H5R7kA3S\n8Pmhsgl+tawoMvkHYLE/Uidl0h0FE8c2Eptb8PNMV3C43267jrQSBmQ1AdWw\nt693HnfbipV2FoX7eSnP6nseFnyUuIzJEDriO0Aw2eVb5B09RPGHRQ0hKI0h\nm4a16ckTgyq2X5zisH2TeNbJvqKTNmt1f7bZWAYuuLOUNHp0sD0lVqo74oa0\np/QG9fYnOYFEMhBEjzpYd/1LBH7oMjFa0TtavRrv38ZZclODE7pIDcGKKxBX\nXybH\r\n=Dnjj\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIH1H4CPMHmClkWaHlBP9o1UeeGYF299unilwM9CtG3qqAiEAgyV3oHMbI16JJDvR8gE51ot+Z+O7+IFBoCdiaUpskHw="}]},"_npmUser":{"name":"sls-az-func","email":"sls-az@microsoft.com"},"directories":{},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"fiveisprime","email":"maherna@microsoft.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"},{"name":"lostintangent","email":"jc@trl.mx"},{"name":"mattmason03","email":"mamaso@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"tbarlow12","email":"tanner.barlow12@gmail.com"},{"name":"sls-az-func","email":"sls-az@microsoft.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.1.3_1636061997741_0.5881702532985447"},"_hasShrinkwrap":false},"2.2.0":{"name":"serverless-azure-functions","version":"2.2.0","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test:coverage -- --ci","test:coverage":"npm run test -- --config ./jest.config.js","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"dfeb0c5cdff19fd5eb38f35c9fbd3b423bda4af3","_id":"serverless-azure-functions@2.2.0","_nodeVersion":"18.16.0","_npmVersion":"9.5.1","dist":{"integrity":"sha512-Byq3so3WIYQ+uiFIySntspR3Smd/mP4eWkMBHL0+hvzdFN/rxhkfkgPDzVpc7EmuOGmj1bXlwWD2LXW4KfTEGA==","shasum":"c61b3690e396c05b73bf40096ca5e93c2f0dd042","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.2.0.tgz","fileCount":3,"unpackedSize":18633,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCyX4NsiOUME9LDbFGDtIUtJ2lGCncth21efVlgo+nvmwIhAMszWCttYtQVfg2KfmXV5KiTTwyTZ9Yh11MpOWF+ULfb"}]},"_npmUser":{"name":"serverless-main","email":"services@serverless.com"},"directories":{},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"fiveisprime","email":"maherna@microsoft.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"},{"name":"lostintangent","email":"jc@trl.mx"},{"name":"mattmason03","email":"mamaso@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"tbarlow12","email":"tanner.barlow12@gmail.com"},{"name":"sls-az-func","email":"sls-az@microsoft.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.2.0_1684262194286_0.19721589384360083"},"_hasShrinkwrap":false},"2.2.1":{"name":"serverless-azure-functions","version":"2.2.1","description":"Provider plugin for the Serverless Framework v1.x which adds support for Azure Functions.","license":"MIT","main":"./lib/index.js","typings":"./lib/index.d.ts","author":{"name":"Azure Functions"},"scripts":{"start":"npm run test -- --watch","lint":"eslint src/**/*.ts","lint:fix":"eslint src/**/*.ts --fix","pretest":"npm run lint","test":"jest","test:ci":"npm run test:coverage -- --ci","test:coverage":"npm run test -- --config ./jest.config.js","clean:int":"rm -rf integrationTests/configurations/**/.serverless integrationTests/configurations/**/node_modules integrationTests/configurations/**/local.settings.json","pretest:int":"npm run clean:int","test:int":"clvr","compile":"tsc","prebuild":"shx rm -rf lib/ && npm run test","build":"npm run compile","generate:spn":"bash ./scripts/generate-service-principal.sh","changelog":"conventional-changelog -p angular -i CHANGELOG.md -s -r 0","changelog:condensed":"npm run changelog && node ./scripts/condenseChangelog.js"},"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"lcov.path":["./coverage/lcov.info"],"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"dependencies":{"@azure/arm-apimanagement":"^5.1.0","@azure/arm-appservice":"^5.7.0","@azure/arm-keyvault":"^1.2.1","@azure/arm-resources":"^1.0.1","@azure/arm-storage":"^9.0.1","@azure/ms-rest-nodeauth":"^1.0.1","@azure/storage-blob":"^10.3.0","acorn":"^7.0.0","axios":"^0.18.0","azure-functions-core-tools":"^3.0.2245","cross-spawn":"^7.0.2","deep-equal":"^1.0.1","js-yaml":"^3.13.1","jsonpath":"^1.0.1","lodash":"^4.16.6","md5":"^2.2.1","open":"^6.3.0","querystring":"^0.2.0","request":"^2.81.0","rimraf":"^2.7.1","semver":"^6.3.0","xml2js":"^0.4.22","zip-folder":"^1.0.0","serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"devDependencies":{"@azure/ms-rest-js":"^1.8.7","@babel/runtime":"^7.4.5","@types/jest":"^24.0.13","@types/jsonpath":"^0.2.0","@types/lodash":"^4.14.130","@types/mock-fs":"^3.6.30","@types/open":"^6.1.0","@types/request":"^2.48.1","@types/serverless":"^1.18.2","@types/xml":"^1.0.3","@types/xml2js":"^0.4.5","@typescript-eslint/eslint-plugin":"^1.9.0","@typescript-eslint/parser":"^1.9.0","axios-mock-adapter":"^1.16.0","babel-jest":"^24.8.0","babel-preset-react-app":"^9.0.0","clvr":"^0.7.1","conventional-changelog-cli":"^2.0.23","eslint":"^5.16.0","jest":"^24.8.0","jest-cli":"^24.8.0","jest-os-detection":"^1.1.1","mock-fs":"^4.10.0","mock-spawn":"^0.2.6","serverless":"^1.44.1","shx":"^0.3.2","ts-node":"^8.8.2","typescript":"^3.4.5"},"optionalDependencies":{"serverless-webpack":"^4.2.0","webpack":"^3.10.0"},"engines":{"node":">= 6.5.0"},"gitHead":"3f8d7933c1451544a6acedc0f2565474bc86d8d2","_id":"serverless-azure-functions@2.2.1","_nodeVersion":"18.16.0","_npmVersion":"9.5.1","dist":{"integrity":"sha512-mNwh5iTPJwbEa+AoVzHQr1/wtaDP9pz9K4ESHLgHqbrJxyXBeUno76pqrBiR5+yJDwHxP/6qsjk+6PbpGqtA7A==","shasum":"e299e2578ef8003fcda062913bd3164df3ab5802","tarball":"https://registry.npmjs.org/serverless-azure-functions/-/serverless-azure-functions-2.2.1.tgz","fileCount":123,"unpackedSize":571042,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCSbuueuLt58y6uZwcXGXuiBCVoGu1NUGdcImqFSODwvwIhALbM/zuFk7nNt1gWbRdU2ZB/Cghgl9avR+SBEvM1kbnw"}]},"_npmUser":{"name":"serverless-main","email":"services@serverless.com"},"directories":{},"maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"fiveisprime","email":"maherna@microsoft.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"},{"name":"lostintangent","email":"jc@trl.mx"},{"name":"mattmason03","email":"mamaso@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"tbarlow12","email":"tanner.barlow12@gmail.com"},{"name":"sls-az-func","email":"sls-az@microsoft.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/serverless-azure-functions_2.2.1_1684271252849_0.08383191547611002"},"_hasShrinkwrap":false}},"readme":"# Azure Functions Serverless Plugin - *Currently looking for active maintainers*\n\nReach out to [@medikoo](https://github.com/medikoo) to discuss becoming a maintainer if interested.\n\nThis plugin enables Azure Functions support within the Serverless Framework.\n\n[![Build Status](https://dev.azure.com/serverless-inc/serverless-azure-functions/_apis/build/status/Publish%20Release?branchName=master)](https://dev.azure.com/serverless-inc/serverless-azure-functions/_build/latest?definitionId=13&branchName=master) [![Code Coverage](https://codecov.io/gh/serverless/serverless-azure-functions/branch/dev/graph/badge.svg)](https://codecov.io/gh/serverless/serverless-azure-functions) [![npm version](https://badge.fury.io/js/serverless-azure-functions.svg)](https://www.npmjs.com/package/serverless-azure-functions)\n\n\n\n## Quickstart\n\n### Pre-requisites\n\n1. Node.js 8.x or above\n2. Serverless CLI `v1.9.0+`. You can run `npm i -g serverless` if you don't already have it.\n3. An Azure account. If you don't already have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/) that includes $200 of free credit.\n\n### Create a new Azure Function App\n\n```bash\n# Create Azure Function App from template\n# Templates include: azure-nodejs, azure-python, azure-dotnet\n$ sls create -t azure-nodejs -p \n# Move into project directory\n$ cd \n# Install dependencies (including this plugin)\n$ npm install\n```\n\nThe `serverless.yml` file contains the configuration for your service. For more details on its configuration, see [the docs](docs/CONFIG.md).\n\n### Running Function App Locally (`offline` plugin)\n\nAt the root of your project directory, run:\n\n```bash\n# Builds necessary function bindings files and starts the function app\n$ sls offline\n```\n\nThe `offline` process will generate a directory for each of your functions, which will contain a file titled `function.json`. This will contain a relative reference to your handler file & exported function from that file as long as they are referenced correctly in `serverless.yml`.\n\nAfter the necessary files are generated, it will start the function app from within the same shell. For HTTP functions, the local URLs will be displayed in the console when the function app is initialized.\n\nTo build the files *without* spawning the process to start the function app, run:\n\n```bash\n$ sls offline build\n```\n\nTo simply start the function app *without* building the files, run:\n\n```bash\n$ sls offline start\n```\n\nTo clean up files generated from the build, run:\n\n```bash\n$ sls offline cleanup\n```\n\nTo pass additional arguments to the spawned `func host start` process, add them as the option `spawnargs` (shortcut `a`). Example:\n\n```bash\n$ sls offline -a \"--cors *\"\n```\n\nThis works for `sls offline` or `sls offline start`\n\n### Dry-Run Deployment\n\nBefore you deploy your new function app, you may want to double check the resources that will be created, their generated names and other basic configuration info. You can run:\n\n```bash\n# -d is short for --dryrun\n$ sls deploy --dryrun\n```\n\nThis will print out a basic summary of what your deployed service will look like.\n\nFor a more detailed look into the generated ARM template for your resource group, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls deploy --dryrun --arm\n```\n\n### Deploy Your Function App\n\nDeploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the `serverless` CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.\n\n```bash\n$ sls deploy\n```\n\nFor more advanced deployment scenarios, see our [deployment docs](docs/DEPLOY.md)\n\n### Get a Summary of Your Deployed Function App\n\nTo see a basic summary of your application (same format as the dry-run summary above), run:\n\n```bash\n$ sls info\n```\n\nTo look at the ARM template for the last successful deployment, add the `--arm` (or `-a`) flag:\n\n```bash\n$ sls info --arm\n```\n\nYou can also get information services with different stages, regions or resource groups by passing any of those flags. Example:\n\n```bash\n$ sls info --stage prod --region westus2\n```\n\n### Test Your Function App\n\nInvoke your HTTP functions without ever leaving the CLI using:\n\n```bash\n$ sls invoke -f \n```\n\n##### Invoke Options\n\n- `-f` or `--function` - Function to Invoke\n- `-d` or `--data` - Stringified JSON data to use as either query params or request body\n- `-p` or `--path` - Path to JSON file to use as either query params or request body\n- `-m` or `--method` - HTTP method for request\n\n##### Example\n\nAfter deploying template function app, run\n\n```bash\n$ sls invoke -f hello -d '{\"name\": \"Azure\"}'\n```\n\nIf you have a JSON object in a file, you could run\n\n```bash\n$ sls invoke -f hello -p data.json\n```\n\nIf you have your service running locally (in another terminal), you can run:\n\n```bash\n$ sls invoke local -f hello -p data.json\n```\n\nIf you configured your function app to [run with APIM](./docs/examples/apim.md), you can run:\n\n```bash\n$ sls invoke apim -f hello -p data.json\n```\n\n### Roll Back Your Function App\n\nTo roll back your function app to a previous deployment, simply select a timestamp of a previous deployment and use `rollback` command.\n\n```bash\n# List all deployments to know the timestamp for rollback\n$ sls deploy list\nServerless:\n-----------\nName: myFunctionApp-t1561479533\nTimestamp: 1561479533\nDatetime: 2019-06-25T16:18:53+00:00\n-----------\nName: myFunctionApp-t1561479506\nTimestamp: 1561479506\nDatetime: 2019-06-25T16:18:26+00:00\n-----------\nName: myFunctionApp-t1561479444\nTimestamp: 1561479444\nDatetime: 2019-06-25T16:17:24+00:00\n-----------\n\n# Rollback Function App to timestamp\n$ sls rollback -t 1561479506\n```\n\nThis will update the app code and infrastructure to the selected previous deployment.\n\nFor more details, check out our [rollback docs](docs/ROLLBACK.md).\n\n### Deleting Your Function App\n\nIf at any point you no longer need your service, you can run the following command to delete the resource group containing your Azure Function App and other depoloyed resources using:\n\n```bash\n$ sls remove\n```\n\nYou will then be prompted to enter the full name of the resource group as an extra safety before deleting the entire resource group.\n\nYou can bypass this check by running:\n\n```bash\n$ sls remove --force\n```\n\n### Creating or removing Azure Functions\n\nTo create a new Azure Function within your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of new function\n$ sls func add -n {functionName}\n```\n\nThis will create a new handler file at the root of your project with the title `{functionName}.js`. It will also update `serverless.yml` to contain the new function.\n\nTo remove an existing Azure Function from your function app, run the following command from within your app's directory:\n\n```bash\n# -n or --name for name of function to remove\n$ sls func remove -n {functionName}\n```\n\nThis will remove the `{functionName}.js` handler and remove the function from `serverless.yml`\n\n*Note: Add & remove currently only support HTTP triggered functions. For other triggers, you will need to update `serverless.yml` manually\n\n### Advanced Authentication\n\nThe getting started walkthrough illustrates the interactive login experience, which is recommended when getting started. However, for more robust use, a [service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals) is recommended for authentication.\n\n##### Creating a Service Principal\n\n1. [Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)\n2. Login via Azure CLI and set subscription\n ```bash\n # Login to Azure\n $ az login\n # Set Azure Subscription for which to create Service Principal\n $ az account set -s \n ```\n3. Generate Service Principal for Azure Subscription\n ```bash\n # Create SP with unique name\n $ az ad sp create-for-rbac --name \n ```\n This will yield something like:\n ```json\n {\n \"appId\": \"\",\n \"displayName\": \"\",\n \"name\": \"\",\n \"password\": \"\",\n \"tenant\": \"\"\n }\n ```\n4. Set environment variables **with values from above service principal**\n\n **Bash**\n ```bash\n $ export AZURE_SUBSCRIPTION_ID=''\n $ export AZURE_TENANT_ID=''\n $ export AZURE_CLIENT_ID=''\n $ export AZURE_CLIENT_SECRET=''\n ```\n\n **Powershell**\n ```powershell\n $env:AZURE_SUBSCRIPTION_ID=''\n $env:AZURE_TENANT_ID=''\n $env:AZURE_CLIENT_ID=''\n $env:AZURE_CLIENT_SECRET=''\n ```\n\n### Example Usage\n- **[Visit our sample repos](docs/examples/samples.md) for full projects with different use cases**\n- [Configuring API Management](docs/examples/apim.md) that sits in front of function app\n\n### Logging Verbosity\n\nYou can set the logging verbosity with the `--verbose` flag. If the `--verbose` flag is set with no value, logging will be as verbose as possible (debug mode). You can also provide a value with the flag to set the verbosity to a specific level:\n\n- `--verbose error` - Only error messages printed\n- `--verbose warn` - Only error and warning messages printed\n- `--verbose info` - Only error, warning and info messages printed\n- `--verbose debug` - All messages printed\n\n### Contributing\n\nPlease create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.\n\nWe're still in the process of getting everying running 100%, but please refer to the [Serverless contributing guidlines](CONTRIBUTING.md) for information on how to contribute and code of conduct.\n\n#### Local dev\n\n1. Clone this repository to your local machine\n2. Navigate to the cloned folder\n3. Run `npm install`\n4. Run `npm run build`\n5. Navigate to a folder where you created a new Serverless project, run `npm install`, and then run `npm link {path to serverless-azure-functions folder}`. Running `npm install` after the link command may override the link.\n6. The npm modules should now contain your local version of this plugin.\n\n#### Unit Tests\n\nWe use [Jest](https://jestjs.io/) for unit tests, and it is expected that every Pull Request containing code changes have accompanying unit tests.\n\nRun unit tests using `npm test` or `npm run test:coverage` to get coverage results.\n\n#### Integration Tests\n\nWe run our integration tests twice per day from our GitHub workflow. These tests install the beta version of the plugin, deploy a function app (with APIM), re-deploy (to make sure ARM template deployment is skipped), invoke the function directly, invoke the APIM endpoint and then remove the resource group, making assertions on the output at each step. While the number of configurations one could use in the Serverless Framework is virtually infinite, we tried to capture the main runtimes and platforms that are supported by the tool:\n\n- Node 10 on Linux using remote build\n- Node 10 on Linux using external package\n- Node 10 on Windows\n- Node 10 on Windows using webpack\n- Node 12 on Linux using remote build\n- Node 12 on Linux using external package\n- Node 12 on Linux using remote build and premium functions\n- Node 12 on Windows\n- Node 12 on Windows using premium functions\n- Node 12 on Windows using webpack\n- Node 14 on Windows\n- Node 14 on Windows using premium functions\n- Node 14 on Windows using webpack\n- Python 3.6 (Linux only)\n- Python 3.6 (Linux only) using premium functions\n- Python 3.7 (Linux only)\n- Python 3.8 (Linux only)\n- .NET Core 2.2 on Linux\n- .NET Core 2.2 on Windows\n- .NET Core 3.1 on Linux\n- .NET Core 3.1 on Windows\n\nWe made these configurations as minimal as possible. If you are having problems with your project, feel free to check to see if our integration tests are passing (see badge at top of readme) and then double check our configuration inside the `integrationTests` directory.\n\nWe use [Clover](https://www.npmjs.com/package/clvr) to run the integration tests, and they run 2x per day in our GitHub Action, split out by runtime language.\n\n#### Signing commits\n\nAll commits in your Pull Request will need to be signed. When looking at the commits in the pull request, you will see a green 'verified' icon next to your commit. Commit signature verification is discussed [here](https://help.github.com/en/articles/about-commit-signature-verification).\n\nFollow the directions [here](https://help.github.com/en/articles/signing-commits) to configure commit signing.\n\nIf any of your commits are not signed, your pull request will not be able to be merged into the base branch. You can fix this by squashing any unsigned commits into signed commits using an interactive rebase, and force pushing your new commit history. More detail [here](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History).\n\nWhen using Windows you may also encounter an error when trying to sign a commit, stating that a security key could not be found. Ensure that you have set the path the gpg in the git config: `git config --global gpg.program \"C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe\"`\n\n## License\n\n[MIT](LICENSE)\n","maintainers":[{"name":"christopheranderson","email":"chrande@outlook.com"},{"name":"fiveisprime","email":"maherna@microsoft.com"},{"name":"windowsazure","email":"azuresdk@outlook.com"},{"name":"lostintangent","email":"jc@trl.mx"},{"name":"mattmason03","email":"mamaso@microsoft.com"},{"name":"serverless-main","email":"services@serverless.com"},{"name":"pgopa","email":"pgopa@microsoft.com"},{"name":"tbarlow12","email":"tanner.barlow12@gmail.com"},{"name":"sls-az-func","email":"sls-az@microsoft.com"}],"time":{"modified":"2023-05-16T21:07:33.111Z","created":"2017-02-21T21:08:00.221Z","0.1.0":"2017-02-21T21:08:00.221Z","0.1.1":"2017-02-23T06:53:12.273Z","0.1.2":"2017-03-20T19:10:23.340Z","0.1.3":"2017-05-03T16:59:01.077Z","0.2.0":"2017-06-01T22:50:03.334Z","0.3.0":"2017-07-20T15:54:44.592Z","0.4.0":"2017-07-30T00:58:52.875Z","0.5.0":"2018-03-14T04:28:18.791Z","0.6.0":"2018-04-26T15:17:47.030Z","0.7.0":"2018-10-18T22:28:21.740Z","1.0.0-1":"2019-06-18T02:21:23.793Z","1.0.0-2":"2019-06-18T02:26:21.194Z","1.0.0-3":"2019-06-18T02:40:48.948Z","1.0.0-4":"2019-06-19T22:31:21.113Z","1.0.0-5":"2019-06-27T19:34:39.934Z","1.0.0-6":"2019-07-12T20:40:30.982Z","1.0.0-7":"2019-07-22T15:32:17.319Z","1.0.0-8":"2019-07-24T15:43:15.017Z","1.0.0-9":"2019-07-25T20:00:02.488Z","1.0.0-10":"2019-08-07T06:40:37.426Z","1.0.0-11":"2019-08-08T23:17:11.334Z","1.0.0-17":"2019-08-28T17:59:36.556Z","1.0.0-16":"2019-08-28T18:02:11.108Z","1.0.0-18":"2019-08-28T18:48:31.156Z","1.0.0-19":"2019-08-28T22:01:43.236Z","1.0.0-20":"2019-08-28T22:06:27.055Z","1.0.0-21":"2019-08-29T14:09:54.555Z","1.0.0-22":"2019-08-29T19:40:34.162Z","1.0.0-25":"2019-08-29T22:40:35.319Z","1.0.0-26":"2019-08-30T16:04:42.721Z","1.0.0-27":"2019-08-30T16:11:34.881Z","1.0.0-28":"2019-08-30T18:41:05.829Z","1.0.0-29":"2019-08-30T21:05:14.422Z","1.0.0-30":"2019-08-30T22:21:32.361Z","1.0.0-31":"2019-09-03T19:58:02.522Z","1.0.0-32":"2019-09-03T22:59:01.879Z","1.0.0-33":"2019-09-04T19:59:50.196Z","1.0.0-34":"2019-09-04T20:18:47.958Z","1.0.0-35":"2019-09-04T21:55:40.651Z","1.0.0-36":"2019-09-05T15:56:42.055Z","1.0.0-37":"2019-09-05T21:38:28.689Z","1.0.0-38":"2019-09-06T15:28:42.749Z","1.0.0-39":"2019-09-06T20:37:59.294Z","1.0.0-40":"2019-09-06T21:19:06.328Z","1.0.0-41":"2019-09-06T23:27:50.400Z","1.0.0-42":"2019-09-09T20:09:27.341Z","1.0.0-43":"2019-09-09T21:28:16.704Z","1.0.0-44":"2019-09-09T21:43:08.474Z","1.0.0-45":"2019-09-10T18:16:59.225Z","1.0.0-46":"2019-09-10T20:32:56.574Z","1.0.0-47":"2019-09-12T20:37:42.930Z","1.0.0-48":"2019-09-12T23:24:17.687Z","1.0.0-49":"2019-09-13T16:59:16.614Z","1.0.0-50":"2019-09-13T19:52:27.632Z","1.0.0":"2019-09-13T21:17:35.671Z","1.0.2-0":"2019-09-23T21:40:12.822Z","1.0.2-1":"2019-09-25T16:43:05.262Z","1.0.2-2":"2019-09-26T22:49:52.637Z","1.0.2-3":"2019-09-27T15:35:19.204Z","1.0.2-4":"2019-09-30T15:19:31.903Z","1.0.2-5":"2019-10-02T23:57:32.896Z","1.0.2-6":"2019-10-03T17:32:04.689Z","1.0.2-7":"2019-10-03T17:32:42.688Z","1.0.2-8":"2019-10-03T17:55:23.417Z","1.0.2":"2019-10-07T12:20:30.802Z","1.0.2-9":"2019-10-11T20:51:34.363Z","1.0.2-10":"2019-10-25T22:28:24.053Z","1.0.2-11":"2019-10-25T22:28:57.048Z","1.0.2-12":"2019-10-25T23:20:29.220Z","1.0.2-13":"2019-10-25T23:21:01.772Z","1.0.2-14":"2019-10-31T19:12:44.968Z","1.0.2-15":"2019-10-31T20:57:46.895Z","1.0.2-16":"2019-11-26T21:32:44.851Z","1.0.2-17":"2020-03-04T21:10:56.191Z","1.0.2-18":"2020-03-05T23:32:57.744Z","1.0.2-19":"2020-03-06T17:26:14.038Z","1.0.2-22":"2020-04-08T04:56:52.733Z","1.0.2-23":"2020-04-16T23:06:15.938Z","1.0.2-24":"2020-04-21T03:53:57.817Z","1.0.2-25":"2020-04-21T03:54:36.760Z","1.0.2-26":"2020-04-21T04:03:38.783Z","1.0.2-27":"2020-04-21T04:05:07.674Z","1.0.2-28":"2020-04-24T17:56:31.964Z","1.0.2-29":"2020-04-30T12:49:14.974Z","1.0.2-30":"2020-04-30T12:50:40.802Z","1.0.2-31":"2020-04-30T23:48:14.322Z","1.0.2-32":"2020-05-09T12:42:19.664Z","1.0.2-33":"2020-05-11T15:35:41.289Z","1.0.2-34":"2020-05-12T22:27:19.663Z","1.0.2-35":"2020-05-15T21:27:35.179Z","1.0.2-36":"2020-05-18T18:17:07.256Z","1.0.2-37":"2020-05-19T21:51:25.971Z","1.0.2-38":"2020-05-19T21:52:33.837Z","1.0.2-39":"2020-05-20T17:25:12.850Z","2.0.0":"2020-05-20T18:07:16.181Z","2.0.1":"2020-05-20T19:38:17.887Z","2.0.2":"2020-05-20T23:02:28.328Z","2.0.3":"2020-05-21T12:34:22.478Z","2.0.4":"2020-05-21T16:36:25.303Z","2.0.5":"2020-05-27T15:58:09.695Z","2.0.6":"2020-05-27T16:09:05.108Z","2.0.7":"2020-06-02T01:53:05.683Z","2.0.8":"2020-06-02T12:10:59.256Z","2.0.9":"2020-06-09T03:20:29.833Z","2.0.10":"2020-06-29T23:17:32.673Z","2.0.11":"2020-06-30T16:06:10.023Z","2.0.12":"2020-06-30T16:16:44.108Z","2.0.13":"2020-06-30T18:27:09.211Z","2.1.0":"2020-08-28T16:56:41.409Z","2.1.1":"2021-08-23T09:46:59.458Z","2.1.2":"2021-11-04T20:56:10.809Z","2.1.3":"2021-11-04T21:39:57.979Z","2.2.0":"2023-05-16T18:36:34.433Z","2.2.1":"2023-05-16T21:07:32.985Z"},"homepage":"https://github.com/serverless/serverless-azure-functions","keywords":["serverless","serverless framework","serverless applications","serverless modules","azure functions","iot","internet of things","serverless.com"],"repository":{"git":"https://github.com/serverless/serverless-azure-functions"},"author":{"name":"Azure Functions"},"license":"MIT","readmeFilename":"README.md"}