Add new endpoint for fetching rule evaluations

[evankanderson]

Summary

Defines a new API for fetching rule evaluation results, rather than overloading GetProfileStatusByName. Does not provide an implementation, though hopefully the implementation is straightforward.

Change Type

Mark the type of change your PR introduces:

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

make gen
make test
make build

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[rdimitrov]

I guess it's not intentional but the comment here is the same as the next one

[evankanderson]

Oops, thanks, fixed!

[eleftherias]

Is this in preparation for label-based profiles? Or something else?

[JAORMX]

Is this in preparation for label-based profiles? Or something else?

yep

[evankanderson]

Are we gonna have labels be a fixed list of strings? or are we going to have labels be a keypair like k8s? This is something I'd like to get consensus on.

Yeah, that's exactl the sort of thing I wanted to highlight with this API proposal.

I was thinking bag-of-strings, but we could do keypairs if that seems more useful.

[JAORMX]

@evankanderson thinking about this further, I don't particularly have a use-case for key-value style labels. So, an array of strings is just as good in this case. We probably want to make them settable by users at some point though. Do you have thoughts on character validation for these labels?

[evankanderson]

My first thought was to start with dns-style labels, but I'm wondering if that's too constricting.

[JAORMX]

My first thought was to start with dns-style labels, but I'm wondering if that's too constricting.

I'd say DNS + a minimal subset of characters like "/" and "-" should be fine to start with

[evankanderson]

Okay, I updated the comments based on our discussion about K:V maps vs "bag of strings". We ended up going with the bag of strings approach because all our "values" ended up being singletons (e.g. "true" or "hidden", but no other value). Also clarified max size and allowed characters for the labels.