The CLI "wrap command" is the main way of using Infisical at the moment and works for injecting secrets for local development as well as embedding into your Docker images if you use that; it definitely has pros and cons (a pro is not having to bundle any packages into your application code - in that sense, "dependency-less") but I can see it not being for everyone.
As mentioned we have an open API that we're working to make easier to use because E2EE ops for encrypting/decrypting secrets are not pleasant honestly to have to piece together yourself — because of this we have plans to release SDKs to abstract-away the cryptography (reading/writing secrets from/to Infisical would be one function call away).
What options would you want for interacting with a secret manager, just wondering?
This is actually not the only way to use Infisical (though it's probably the easiest one). You can also use our Open API and we are adding SDKs for the most popular languages in the next few weeks: https://infisical.com/docs/api-reference/overview/introducti....
The CLI "wrap command" is the main way of using Infisical at the moment and works for injecting secrets for local development as well as embedding into your Docker images if you use that; it definitely has pros and cons (a pro is not having to bundle any packages into your application code - in that sense, "dependency-less") but I can see it not being for everyone.
As mentioned we have an open API that we're working to make easier to use because E2EE ops for encrypting/decrypting secrets are not pleasant honestly to have to piece together yourself — because of this we have plans to release SDKs to abstract-away the cryptography (reading/writing secrets from/to Infisical would be one function call away).
What options would you want for interacting with a secret manager, just wondering?