Portal file access is confused after using this

[SteveALee]

Feel free to just close this as it's a pretty unusual use case but I'm raising it for the record.

So I installed and ran this in the Azure portal Functions Console (because I could) and then wanted to look at the files using the Functions Files UI - mainly to figure out what had been done. I had a single functions

When the Functions panel is opened the .funcpack/index.js is open which make sense I guess. However if you use the Files UI to explore other files it is impossible to get back the .funcpack/index.js

[christopheranderson]

@lindydonna - any idea why this would be?

[SteveALee]

File viewer only allows access to function folder and below I think. .funcpack is in wrong place.

[lindydonna]

@christopheranderson Can you tell me the layout that funcpack produces?

Note that the API for listing the functions within an app is in Kudu.

[christopheranderson]

So this produces a structure like:

-/.funcpack/index.js
-/foo/index.js
-/foo/function.json
-/bar/index.js
-/bar/function.json

I think the problem here is that you can't navigate back to .funcpack/index.js once you navigate away. If the file's tool in the portal let you navigate down the root of the Function App, that might help with this and other issues like shared libraries/node modules/etc.

[lindydonna]

@christopheranderson Great point. I'll add this to the portal backlog. I'll have to work with the designer to find the right UX.