Jake Van Vorhis
Jake Van Vorhis
I like this proposal and agree with a need to standardize resource provision of some subset of Agent metadata. However, I could see a situation where some of the metadata...
That's an interesin > I'm curious what your thoughts are on the info endpoint, I posted a potential schema for it [here](https://github.com/AI-Engineer-Foundation/agent-protocol/issues/39#issuecomment-1735883734) in Issue #39. > > It didn't go...
@sago2k8 We have been, with an OpenFeature provider we wrote ourselves because the [LD OpenFeature contrib provider](https://github.com/open-feature/js-sdk-contrib/tree/main/libs/providers/launchdarkly-client) had not yet been developed, and you can actually read about our experience...
Reopening this as it looks like we aren't all the way to using `MatchSubjectMappings` yet and are still listing all attributes.
Reopening with additional context that we should move validation like [what was introduced here](https://github.com/opentdf/platform/blob/main/sdk/internal/autoconfigure/granter.go) into a platform policy lib so that we can share it throughout the platform services and...
This has not been completed for attribute FQNs
@Nerzal is this ready to merge? :)
Related to https://github.com/opentdf/platform/issues/563
This should not have been closed and is still necessary for maintainability.
Given the current schema, each Resource Mapping (RM) is already currently under a Namespace as 1 RM -> 1 attr value -> 1 attr def -> 1 namespace. It seems...