Problems with Keeper SDK initialization about secrets-manager HOT 2 CLOSED

Due to the lazy initialization the full config is not generated until you actually try to retrieve a record. To bind the token to the app and generate the full config try to retrieve a single record (ex. use non-existent UID that returns empty dataset to minimize traffic)
After creating secrets_manager from token add:
secrets_manager.get_secrets(["AAAAAAAAAAAAAAAAAAAAAA"])
now you should have fully initialized config

Configuration files generated using the Desktop Application or Web Vault should work directly (no need to do lazy init step). When using already generated configurations remember to remove token from SecretsManager initialization step since tokens can be used only once and once bound they expand to a full config which is incompatible with other tokens (except the token it was generated with)

# example using generated config, no token required, absolute path preferred
secrets_manager = SecretsManager(config=FileKeyValueStorage('ksm-config.json'))
secrets_manager.get_secrets([])

from secrets-manager.

Ok, thank you for your help. Now with the single (non-existing) read access, it worked as expected.
This could be a minor improvement in your documentation?

from secrets-manager.