@cap10morgan The env key doesn't really do anything. It's kind of a leftover from an age long ago.

To make an interceptor behave differently, I'd do 2 things.

1. Put an interceptor at the head of the chain that uses a real env value to attach a map to the context. That map would be your environment config.

2. Have your interceptors look for specific config values rather than just "what env am I in"

That way your choice of config mechanism is independent of how your interceptors are written. You can change either one separately.

OK, makes sense. Thanks!

Does anybody have some good example code for using Pedestal with transit as an API back end?

I have an fdef spec for an enter fn that I use in an interceptor, and for some reason it doesn’t seem to check the args when invoking the service-fn in tests with (st/instrument) on. Is there anything pedestal specific that could be causing this, or should I look somewhere else?

Hmm even s/assert doesn’t run in the enter fn, only s/assert*

CompilerException java.lang.AssertionError: Assert failed: In row 1, there were unused elements (:extra :stuff). There is some way to specify extra info on routes? I'm using "#{["/foo" :get [fns] :route-name :bar :extra :stuff]}"