Provide Config File Path to the CLI's invoke local

I am trying to pass a config path to the sls invoke local as I can do with the sls deploy cli routine. I am dynamically building my configuration file but still want to be able to run functions locally.

I’m wondering if that’s possible or if I’m possibly misunderstanding what the invoke local cli is doing.