[feat] Add enrichment option to get entity context detail based on entity ID

[dileepbapat]

In microservice environment, flagr might be used from many different services with entity ID. However, if there is an entity resolving/ enrichment layer it would reduce need to get metadata from each of those consumers.

Let me know if this is in line with the roadmap.

[zhouzhuojie]

This is great idea, and I think it's domain-specific and better be done by the application itself instead of Flagr. Flagr is entity agnostic, and that's why entity context is passed in not derived from within Flagr. Let me know what do you think?

[dileepbapat]

Since whitelisting and jwt available I assume this meant to be also consumed by UI/js however expectation to pass all entity context from UI might be against "expose only necessary information to external world"

I am thinking of domain agnostic way to enrich the context. A sort of optional resolver in middle. If enabled call out configured rest API and merge with entity context.

Thoughts?

On Tue, Sep 17, 2019, 4:01 AM Zhuojie Zhou [email protected] wrote:

This is great idea, and I think it's domain-specific and better be done by the application itself instead of Flagr. Flagr is entity agnostic, and that's why entity context is passed in not derived from within Flagr. Let me know what do you think?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/checkr/flagr/issues/291?email_source=notifications&email_token=AAE2X3QGRH7U4ZIAJCMNVFLQKACKPA5CNFSM4IXAJ2SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD62WYAY#issuecomment-531983363, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE2X3U27F7TPFYK63EKFYTQKACKPANCNFSM4IXAJ2SA .

[github-actions[bot]]

Stale issue message