changing dockerizePip doesn't invalidate cache

[Isaac Greenspan]

Are you certain it's a bug?

• Yes, it looks like a bug

Are you using the latest plugin release?

• Yes, I'm using the latest plugin release

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Issue description

Changing only the dockerizePip setting (from non-linux to true) did not result in things being rebuilt using docker—the cached packaging was used until I also set useStaticCache: false and useDownloadCache: false (probably didn't need both, but happened to set both at the same time), at which point I could see docker being used for the first time.

Service configuration (serverless.yml) content

n/a

Command name and used flags

n/a

Command output

n/a

Environment information

Running "serverless" from node_modules
Framework Core: 3.38.0 (local) 3.35.2 (global)
Plugin: 7.2.0
SDK: 4.5.1


"serverless-python-requirements": "^6.0.1"