Kwaw
Kwaw
@Polombo98 Can you please post the type definitions your team developed?
workaround - https://gist.github.com/zjeaton/42246742cdaf2fb46400d04c2eba9a8a
> have some fallback behavior to use the parent context. @arielvalentin This is already the case, unless i'm mistaken. If you decide not to propagate using links, the parent context...
@zacheryph >it's a callable because we want to dynamically enable/disable this feature, based on stuff in headers, etc.
For anyone that needs to attach dynamic headers for gRPC, you can leverage interceptors. ```go func attachToken( ctx context.Context, method string, req, reply any, cc *grpc.ClientConn, invoker grpc.UnaryInvoker, opts ...grpc.CallOption,...
@lubien yes it does. The thing is, http services are actually tcp services. They are converted to tcp services in flyctl before we send them to flaps.
@dangra I think the process group remark is valuable, so I've added support for that. https://github.com/superfly/flyctl/pull/3522/commits/f0539a14e807bfae83d12905db509f20a4c0a365 Duplicate external ports however, I think we can ignore them for now and merge...