CreateOrReplace operation possible for Azure Table Storage binding?

Please provide a succinct description of the issue.

Repro steps

Provide the steps required to reproduce the problem

1. Use table storage output binding in node function in App Service plan

2. Output table item with existing RowKey, setting Etag: “*”

Expected behavior

A upsert operation is executed as mentioned here

Actual behavior

Function fails with: The specified entity already exists.

The docs state that upsert is not supported but there seems to be something here that should do the trick? https://github.com/Azure/azure-webjobs-sdk/blob/ea55e6ef5439b1059b43825cb9d40cc12ae219bc/src/Microsoft.Azure.WebJobs.Extensions.Storage/Tables/TableEntityWriter.cs#L100

[jeffhollan]

It’s a valid feature and potentially just a few lines of code, but not yet at the top of the backlog. Keep letting us know (via 👍 or whatever) that this would be a worthwhile feature to implement more explicitly in the extension. For now the recommended approach would be leveraging the Table SDKs directly in the Azure Function code (e.g. the Node Azure Table SDK) to perform an upsert operation. In general bindings are a convenience (and a great one at that 😄 ) but can accomplish the same behaviors by leveraging the SDKs if need more flexibility or control. Let us know. Thanks

[mpseidel]

Great. So looks like this can be fixed with little effort? If so when can we expect it to be shipped?