-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose UsePath
in the CamundaCloudClientBuilder for persisted token storage.
#636
Comments
Seeing a couple issues that stem from this configuration. Is there a way we can expedite patching this issue? I assumed we could downgrade versions but having just looked through the history it seems even this isn't possible as it's always cached the tokens on disk. |
@ShawnAbshire have you tried to directly use the |
I have not, but looking into the builders I'm not seeing how this circumnavigates where the tokens are being saved to. I don't see any steps to configure the path. |
You can use The same you do in your PR? 🤔 https://github.com/camunda-community-hub/zeebe-client-csharp/pull/638/files Example:
|
ah I see, sorry I had downgraded my package to 2.2.0 and so when inspecting didn't see the updated interface. Will attempt this solution. |
This moves me forward, appreciate your response! I still think it'd be nice to have the option on the cloud builder, but feel free to close if you think otherwise! |
Is your feature request related to a problem? Please describe.
Hello, recently started setting up lower test environments that point to a cloud instance of camunda 8 and ran into an issue where the library is attempting to persist tokens to disk for caching (
.zeebe
); however, this directory is read only in our environment and due to restrictions beyond my control I am unable to make it not read only; however, we do have a location that we would be able to write to.I see there is a
UsePath
method on theICamundaCloudTokenProviderBuilderFinalStep
that isn't exposed via theICamundaCloudClientBuilder
and I don't see any other way of configuring theCamundaCloudTokenProviderBuilder
.Describe the solution you'd like
I would like to expose the
UsePath
on the theICamundaCloudClientBuilder
so we can properly configure where we'd like to persist our token cache.Describe alternatives you've considered
Only alternative as of right now is to downgrade to before this change was implemented.
Additional context
No additional context.
The text was updated successfully, but these errors were encountered: