Hi Jack_P_1P, thank you for your response.
Yes, we need to dynamically load secrets at run time. There are some secrets that can be loaded as environment variables, but many other secrets must be loaded dynamically, at run time.
I understand, https://developer.1password.com/docs/connect/connect-api-reference/#get-item-details, that in order to read an item from any vault using REST APIs I should call GET /v1/vaults/{vaultUUID}/items/{itemUUID}. The hurdle here is that the UUID (both for the vault and for the item) will be different for development and production (once the credentials will reside, obviously, in different vaults).
Is there a reason for the nodejs sdk not include a method to read a secret, but only get item metadata? I mean, why does getItemByTitle don't return item's fields? Are there any security restrictions for that?
