Configuration to Defer connection to Temporal on Application Start - Eg, using the Extension for the Client -

[akil-rails]

I see that the extension connects to the temporal cloud at application start, this is great for workers, but not so good for the client.

I suppose, a common use case would be to use the WorkflowClient in a service layer (say a quarkus REST resource). The service would accept the request, and attempt a start of the workflow, and if it fails, it could decide to store it and try again. The service should be available to accept requests, irrespective of its connectivity to the temporal server, and could in-fact report that in the /q/health endpoint.

A configuration option to do this would be great..

[melloware]

We had discussed this here: #70 cc @rmanibus ?

[akil-rails]

The extension already handles any network break & reconnection gracefully (once the application has started) .
A configuration option to let the application decide if the startup should fail if a connection isn't established will be very useful - specifically for temporal cloud users - the network connectivity can be intermittent, and should not prevent application startups..

[melloware]

@akil-rails any interest in adding this feature?

[akil-rails]

Yes, though I need some guidance - I don't understand what part of the extension stops the app from starting ?

[melloware]

@rmanibus can provide some guidance here...

[rmanibus]

Hey, I will have a closer look this weekend, I am quite busy for the rest of the week !