noDeploy option does not seem to exclude dependencies from zip file

[paulalex]

I am building a lambda layer using the python requirements plugin and I am trying to exclude some dependencies using noDeploy, and when I do this the do not appear in the generated requirements.txt file:

-i https://pypi.org/simple
certifi==2023.7.22; python_version >= '3.6'
charset-normalizer==3.2.0; python_full_version >= '3.7.0'
idna==3.4; python_version >= '3.5'
jmespath==1.0.1; python_version >= '3.7'
packaging==23.1; python_version >= '3.7'
python-dateutil==2.8.2; python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3'
requests==2.31.0
reverse-geocode==1.4.1
s3transfer==0.6.2; python_version >= '3.7'
six==1.16.0; python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3'
tenacity==8.2.3; python_version >= '3.7'
urllib3==1.26.16; python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3, 3.4, 3.5'

However, I still get an error that uploading the layer has failed because its too big, and when I expand the requirements zip file generated by the process the folders are actually there, for example scipy and numpy are both excluded and do not appear in the requirements.txt file but do appear in the zip.

One thing I have noticed is that dependencies directly referenced in my Pipfile are excluded, but transitive dependencies which are not being excluded.

Is this a bug?