... | ... | @@ -110,6 +110,19 @@ It also occurs to me that, some if not many blogs might just be translating stuf |
|
|
|
|
|
And, our iam.ExtAuthzServerV3, is implementing `AuthorizationServer`. which dwelves in envoy/service/auth/v3/external_auth.pb.go, of the reference Go project exactly.
|
|
|
|
|
|
```
|
|
|
On further thought, the reference Go project might not be the canonical source -- maybe we should import other packages?
|
|
|
|
|
|
As the comment show(see below), maybe, we are entitled to generate pb.go by ourselves and include the generated files in our own projects.
|
|
|
|
|
|
// Code generated by protoc-gen-go. DO NOT EDIT.
|
|
|
// versions:
|
|
|
// protoc-gen-go v1.25.0
|
|
|
// protoc v3.19.1
|
|
|
// source: envoy/service/auth/v3/external_auth.proto
|
|
|
|
|
|
```
|
|
|
|
|
|
So, here, we get an extensible system at work.
|
|
|
|
|
|
Maybe we can reflect upon the design of our pipeline a bit. I am still not sure how guys from other companies can implement componets and then incorporate them into our pipeline without a compilation. Maybe, it is me who is wrong?
|
... | ... | |