@douglas-reid commented on Mon Sep 18 2017

We should provide a way for specifying a fallback for time expressions.

Possibilities:

• add a now() expressions to the IL and AST.
• add code / preprocess adapter for generating a mixer-specific attribute, like mixer.report.time or mixer.received.time

There are probably other approaches, as well.

@ZackButcher commented on Mon Sep 18 2017

+1 I hit this pain point in writing stackdriver config and more generally in attempting to test configs. Today you must provide all time attributes when using mixc since we can't provide fallbacks in config, for example.

@ozevren commented on Mon Mar 12 2018

Having looked at this recently, I'd say now() has some fundamental problems (mostly with cacheability and introducing observability to the ordering of expressions).

I believe the alternatives are request.time and context.time. request.time should be generated in the proxy.