Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

cc @dmcgowan PTAL thanks!

Another approach might be just marshal the empty response as part of InitFn? 🤔️

I think this is more concise

In addition, the initialization of emptyResponse is not actually related to InitFn, so it looks fine to put it directly in init, eg

var emptyResponse typeurl.Any

func init () {
       emptyResponse, err = typeurl.MarshalAny(&ptypes.Empty{})
       if err != nil {
               panic(fmt.Sprintf("......: %v", err))
        }

        plugin.Register(&plugin.Registration{
        ....
}

In addition, the initialization of emptyResponse is not actually related to InitFn, so it looks fine to put it directly in init, eg

updated. thanks for the reminder :). I didn't use this approach because not sure if it's okay to panic in plugin init 😅

In addition, the initialization of emptyResponse is not actually related to InitFn, so it looks fine to put it directly in init, eg

updated. thanks for the reminder :). I didn't use this approach because not sure if it's okay to panic in plugin init 😅

T functions such as typeurl.Register and plugin.Register will also cause panic, the difference is that panic is called explicitly here, but of course see what others have suggested

I'd argue if it did panic we likely screwed up typeurl pretty bad 😆. I like @Iceber's suggestion