Michael Beemer
Michael Beemer
@marandaneto, `stickiness` can be achieved using [evaluation context](https://openfeature.dev/specification/sections/evaluation-context). We have an optional, named propertied called `targeting key` defined in the spec, but the evaluation context is just a map. All...
My initial reaction is that we should specify order explicitly in the spec. I seem to recall that hooks were expected to run first-in-last-out.
@toddbaert can do quickly audit which SDKs would be affected by this change? I think it's worth doing but I would like to understand the impact.
@tcarrio can you confirm PHP and Python behave this way already? I can double-check JS but I'm nearly positive it's using the reverse pattern as well.
As Tom stated above, the JS SDK does reverse the order in the after, error, and finally stages. https://github.com/open-feature/js-sdk/blob/main/src/client.ts#L192
Hey @tcarrio, would you be willing to add this to the spec? It sounds like we have consensus that it should be explicitly defined and the reverse order is preferred...
Hey @rkrbaddam, it looks like your OCP cluster has a security context constraint that doesn't allow the image to run using the default non-root user. [Here](https://github.com/open-feature/open-feature-operator/blob/2c394282592bf9f6626c80bdeea2e5e20cabd274/Dockerfile#L30) is where we're setting...
Thanks @Kavindu-Dodan! @lukas-reining @thomaspoignant do you have anything to add?
Sure, assigned. Thanks @gunishmatta!
Addressed by https://github.com/open-feature/open-feature-operator/pull/633