Stop resolving secretes when running other serverless commands that don't need secrets

Hi All - I’ve noticed when I run a serverless <something> command, it always seems to want to resolve secrets before executing the task I tell serverless to run, even if it’s just using a local plugin that has no reason to use the environment variables I have stored with my cloud provider.

What exactly happens when you use a serverless <something> command, anyway?

I’d like to disable resolving every bit of the config if I’m just trying to do something simple & local. Then I can save config validation for a separate command I can wrap up into other scripts/pipeline steps. It’s causing issues in my build pipeline.