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
The documentation says that the SDK supports a secrets caching mechanism and that the TTL of the secrets can be specified with a param at client's creation time.
The old NodeJs SDK used to have such a parameter, this new one does not.
Are secrets still cached by the SDK ? Is there a way to specify the TTL ?
The text was updated successfully, but these errors were encountered:
Hi @othmaneamane, caching is currently not supported in the newer SDK's. We may add this back in the near future, but currently it's unsupported. I've updated the documentation you linked to properly reflect this. Thank you!
The documentation says that the SDK supports a secrets caching mechanism and that the TTL of the secrets can be specified with a param at client's creation time.
The old NodeJs SDK used to have such a parameter, this new one does not.
Are secrets still cached by the SDK ? Is there a way to specify the TTL ?
The text was updated successfully, but these errors were encountered: