You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the ZeeBe client on a lambda, the code uses the presence of the a directory or the ability to create the directory, and a dictionary of a token file.
This is not possible when using the native .net execution on an AWS lambda.
To Reproduce
Steps to reproduce the behavior:
Create a lambda in an AWS account with enough code to connect to a valid Camunda process
deploy the code to an AWS lambda (do not use a container).
trigger the lambda
The Lambda will fail. and then error will indicate the inability to create
Expected behavior
What should happen is the AWS lambdas should be able to connect to ZeeBe client without relying on a directory or a dictionary stored on a file system that is not guaranteed to exist.
Alternate options are
Use memory
Use Cache
Use S3 stores
With the ability to use them if they are configured. also let the customer chose the token storage provider, with their own custom code.
Enviroment (please complete the following information):
AWS
AWS Lambda Executors for .net 6
Any version of the ZeeBe client
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
A better fix for this would be allowing the cloud builder to specify the location of the temporary storage.
The flip side of this, is that write access to the tmp directory maybe ok, but you're not guaranteed to grab the same /tmp directory for this.
A better fix for this would be allowing the camunda client builder to have a strategy of choosing memory as a location for the cache storage or setting it to a cache location or letting client specify the storage location and mechanism while building this out.
Describe the bug
When using the ZeeBe client on a lambda, the code uses the presence of the a directory or the ability to create the directory, and a dictionary of a token file.
This is not possible when using the native .net execution on an AWS lambda.
To Reproduce
Steps to reproduce the behavior:
The culprit is here
https://github.com/camunda-community-hub/zeebe-client-csharp/blob/main/Client/Impl/Misc/PersistedAccessTokenCache.cs#L28
Expected behavior
What should happen is the AWS lambdas should be able to connect to ZeeBe client without relying on a directory or a dictionary stored on a file system that is not guaranteed to exist.
Alternate options are
With the ability to use them if they are configured. also let the customer chose the token storage provider, with their own custom code.
Enviroment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: