req.context.invocationId

[espray]

Can the invocationId made available through req.context?

[yvele]

@espray I think I should make the whole context object available.. What do you think?

[espray]

I thought that at first, but that might be problematic.
If context.done() was called it would mess with the express flow.
context.bindings are mapped to the express.Request and express.Response params.

The safe play is log and invocationId only

Also, here is my Typescript declaration file azure-function-express.d.ts

import * as express from 'express';

export interface AzureFunctionExpressRequest extends express.Request {
  context: {
    invocationId: string;
    log(message: any): void;
  }
}

[yvele]

@espray I don't like whitelisting and sometimes prefer giving responsibilities to developers but in this case yep I will explicitly add invocationId

But hum.. I can't find context.contextId in any Azure documentation or via a Google search. Can you point me to the doc?

[espray]

Yup I agree on giving full responsibilities to developers.

`context.invocationId'
https://github.com/christopheranderson/azure-functions-typescript
You could ask Christopher, his git profile says he is a Microsoft PM - Azure.

• OR -
  context.bindingData.InvocationId
  Can't get the function ID Azure/azure-functions-host#504

[yvele]

@espray I've published a new patch v1.2.2 to NPM ;)