Till Backhaus

It looks as if this addresses #677, yet I didn't find the issue mentioned here.

I think the issue number for multi source applications is #677

I can provide the/a use case for this issue: I have separate repositories for the application (a node app) and operation (a repository containing a helm chart in my case)....

Let me know if there is anything I can do to make this any easier on your end.

Hi Cesar, thanks for looking into this. One more thing to add since it might not be obvious from the PR: Hashicorp/go-retryablehttp behaves very well in this situation: it evaluates...

@scotchneat thanks for your suggestions. They absolutely make sense to me. I won't have time to implement them over the next months though. Anybody can take it from here?

Nevermind.

I just installed the provider manually with a provider override and it worked for me as long as it took me to migrate away from DO.

Found out that it's not typescript specific. Defining a serializer for the field will work around the issue: ``` var logger = bunyan.createLogger({ name:'app', serializers: { requestId: function(f) { return...

Sorry, I've got to reopen this. Changing the title so it matches the problem. Old title: Callable custom context broken in typescript? New title: Callable custom context serialized on object...