Skip to content
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.

Issue with SCM_USE_FUNCPACK=1 on Consumption Plan #55

Open
ad-ab opened this issue Oct 28, 2017 · 0 comments
Open

Issue with SCM_USE_FUNCPACK=1 on Consumption Plan #55

ad-ab opened this issue Oct 28, 2017 · 0 comments
Assignees
Labels

Comments

@ad-ab
Copy link

ad-ab commented Oct 28, 2017

Hi,
I have run into an issue I was unable to solve to my satisfaction.

I am trying to run azure-functions-pack after gitdeploy using the SCM_USE_FUNCPACK=1 option.
The issue is that after deployment the azure function doesn't work.
Running the pack locally produces a different set of files in the ./funcpack folder than on the server. After inspecting these files I have come to the conclusion that the issue is with the altering of the function.json scriptFile property. It is set to the ./funcpack/index.js which contains only a require for the original (pre packed) function index.js.
Once I changed this to the other file - ./funcpack/output.js the function started to function as expected.
I am sorry if my description of the issue isn't perfect. I am new to node and webpack, azure functions.
My azure function implementation is https://github.com/AdamAbonyi/bobr-bot-scraper.

If you require more information please let me know.

Regards,

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants