Refactor policy evaluation response to allow different levels of embedding values
This commit changes two things: * evaluationID is no longer returned as part of the JSON response, but instead is returned as HTTP ETag header * if policy source code contains a single blank variable assignment then the result from the policy evaluation will be only the value of that variable
parent
4dfe4ef4
No related branches found
No related tags found
Showing
- design/design.go 5 additions, 2 deletionsdesign/design.go
- design/types.go 2 additions, 1 deletiondesign/types.go
- gen/http/cli/policy/cli.go 4 additions, 4 deletionsgen/http/cli/policy/cli.go
- gen/http/openapi.json 1 addition, 1 deletiongen/http/openapi.json
- gen/http/openapi.yaml 5 additions, 0 deletionsgen/http/openapi.yaml
- gen/http/openapi3.json 1 addition, 1 deletiongen/http/openapi3.json
- gen/http/openapi3.yaml 28 additions, 16 deletionsgen/http/openapi3.yaml
- gen/http/policy/client/cli.go 1 addition, 1 deletiongen/http/policy/client/cli.go
- gen/http/policy/client/encode_decode.go 14 additions, 1 deletiongen/http/policy/client/encode_decode.go
- gen/http/policy/client/types.go 16 additions, 0 deletionsgen/http/policy/client/types.go
- gen/http/policy/server/encode_decode.go 4 additions, 2 deletionsgen/http/policy/server/encode_decode.go
- gen/policy/client.go 2 additions, 2 deletionsgen/policy/client.go
- gen/policy/service.go 10 additions, 1 deletiongen/policy/service.go
- internal/service/policy/service.go 17 additions, 5 deletionsinternal/service/policy/service.go
- internal/service/policy/service_test.go 44 additions, 8 deletionsinternal/service/policy/service_test.go
Loading
Please register or sign in to comment