Incorrect binding direction in generated function.json for DocumentDB input

[garthmason]

I'm migrating some functions created in portal templates (.csx) to Azure Functions projects in the tooling.
It's working well so far, only problem I'm facing is already captured in #40.

One thing I have noticed is when I declare an input binding to an Azure DocumentDB the generated function.json file isn't matching the equivalent on the portal function for the direction property.

I.e. if I have e.g. a ServiceBus triggered function, then the binding generates with direction: "in" as expected. But a DocumentDB binding is always generating as direction: "out". Whereas via the portal I get either in or out depending on what I selected.

Note - this doesn't seem to be causing me an issue so far, as I'm getting the desired input from the DocumentDB, and can also use the binding with ICollector to add new documents. Just wanted to flag it in case that wasn't expected behaviour.

[MarekLani]

I noticed this also when trying to define blob input. In function.json there is direction set to out.

[lindydonna]

@MarekLani You should use AccessMode.Read for blob input.

[juzkuz-zz]

I have also noticed this issue. I tried everything available but can't get the compiled function.json to have a direction of 'in' as intended.

[lindydonna]

@juzkuz Yes, we have some bugs around binding direction. The root cause is this issue: Azure/azure-functions-host#1507. We will fix this issue before RTM for sure, and hopefully sooner than that.

[ahmelsayed]

obsolete with Mike's work