Copy Function Project content to new directory #43

christopheranderson · 2017-08-28T23:17:02Z

It's a big issue today to have the built output of the pack tool touch the original source files (because you have to unpack). While in place modifications can be useful for long CI flows (like the output from a TS compile), it's not ideal for normal JS scenarios. Not sure if we should actually support this, but it's worth thinking through what the workflows should be.

Related: #38, #35, #1

qs-wang · 2017-12-11T08:31:45Z

I'm actually working on this by copy the bundle, and the functions folder structure to the output directory.
If you'd be interested in, I can contribute the changes back.
The default folder is as following
dist
-- host.json
-- index.js
--function1
----funciton.json -> pointing to ../index.js
--funciton2
----funciton.json -> pointing to ../index.js

…zure-functions-pack feature request. 1. default output is "dist", can specify via -o option, 2. create the funciotn folder strcuture in the dist folder, 3. copy over the function.json file and makes the chagnes there. The orgianl funciton.json file keeps untouched. 4. Copy over the host.json file to dist folder. In summary the dist folder contains the structure which is redy for uploading to azure. Node: unpack has not been tested.

christopheranderson added the feature label Aug 28, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Copy Function Project content to new directory #43

Copy Function Project content to new directory #43

christopheranderson commented Aug 28, 2017 •

edited

Loading

qs-wang commented Dec 11, 2017 •

edited

Loading

Copy Function Project content to new directory #43

Copy Function Project content to new directory #43

Comments

christopheranderson commented Aug 28, 2017 • edited Loading

qs-wang commented Dec 11, 2017 • edited Loading

christopheranderson commented Aug 28, 2017 •

edited

Loading

qs-wang commented Dec 11, 2017 •

edited

Loading