gertd

Learn Rust or something else if you do not like or cannot stand golang!

This generates high-calorie syntactic sugar just to satisfy an itch.

Run the generated code through the golang-ci linter, which will barf on what is getting created, for example:

``` // Eliminates any 'unused variable' errors _, _, _, _ = err, fileContent, fileContentStrVersion, trimmedLines ```

golang is a procedural language. If you cannot deal with it, don't use it, but please stop polluting the ecosystem.

Exciting to see the AI RAG world connecting with the ReBAC authorization world!

In simple terms topaz brings a rebac data solution together with OPA, so you only have to create attribute based authorization rules when really needed, to compliment the relation authorization provided by the topaz directory.

I love the fact it is bring relational and attribute based together, happy birthday Topaz !

Which is exactly why using a middleware is an option and therefore a decision the implementor makes.

Many people appreciate the middleware approach as it provides coverage for the API surface with minimal investment, so a great way to get started.

But there is no free lunch

Not having to tied them together into a single process space is an interesting option/ability which would get lost with using it as a library.

Having the authorizer integrate based on contract feels like an option which allows for more freedom of choice and variety of implementations.

I do not believe in one size fits all, nor that there is one to rule them all.

Endpoint wise you can have N.

Technically names do not have to match, but it certainly makes it easier if you have a pattern to rely on when injecting authorization into a middleware layer.

Very neat! Can it support gRPC, that would be lovely?

@jzelinskie care to respond, I am really interested in the answer?

So the idea is that you create a candidate set of resource keys from the permission system and join that with the external database and / or use it as a post filter?