Is it possible to run the CLI such that it doesn't kill my entire process when it can't list a specific secret(s) The app I'm running doesn't interact with these specific keys, and it would be better for it to just warn instead of error and read the rest of the secrets I have permission for.

Hey @Tanvir Ahmed! I totally understand the frustration. The easiest fix to solve this today will be with how you organize your secrets. Instead of pulling everything from one big path, break your secrets into folders based on what actually needs them, like

/app

for your application secrets and

/infra

for the stuff your app doesn't touch for example. Then scope your role so it only has access to

/app

and run:

infisical run --env=prod --path=/app -- your-start-command

That way the CLI only ever asks for secrets you have permission to read and there aren't any errors or crashes. Basically the idea is to organize secrets so you're only fetching what is yours and not fighting permissions at fetch time. Hope this helps!