Christoph Wille

Status: played some more with https://github.com/christophwille/dotnet-opa-wasm/tree/master/spikes/AspNetAuthZwithOpa to see how prescriptive / opinionated things can / should be. Not convinced yet on any one strategy or providing it at all.

Options for "getting OPA onto the machine": download & make executable (per platform) or maybe use the docker image?

I am all for using jq https://stedolan.github.io/jq/download/ to do the capabilities files modifications (requiring it to be installed beforehand). Because we are going to use it with Unit Tests, the...

My command line sample might not be proper PS syntax; also, I am mostly only concerned to solve the unit test use case here, not creating a "general purpose one-size...

I tried to make it work slightly dumbed-down on Windows: ``` param( [Parameter(Mandatory=$true)] [string[]] $Files=@(), [Parameter(Mandatory=$false)] [string] $Destination ) [string[]]$duplicatedBuiltins = jq -s -r "[ .[].builtins | .[] ] |...

Seems so because `$output = jq -s "{ builtins: [ .[].builtins | .[]] | group_by(.name) | map(.[-1]) }" $Files` works

ok, at least I can diff it now - one thing does change, it doesn't merge the following: ``` "future_keywords": [ "in" ], "wasm_abi_versions": [ { "version": 1, "minor_version": 1...

Yes, I played around with diffs to figure out what I need and then it merged nicely.

> * create the wasms so they no longer are checked in Maybe https://www.thorsten-hans.com/distribute-webassembly-modules-as-oci-artifacts/ is a viable option (store to ACR)

To pick on a specific example: https://github.com/iinuwa/dotnet-opa-wasm/commit/a73dbc76fb8ce33e979708722541795da0479d8c The C#-implemented SDK builtins should be tested directly from a C# unit test, not indirectly via rego (I would consider the latter an...