Donato Perconti

Curious if this feature was still being considered? As of right now, it's possible to manually set caching in the UI and then manually re-deploy the stage. But, re-deploying chalice...

*bump*

I'm experiencing the same issue as well. @BabyDino or @koorukuroo - were either of you able to figure out the issue/solution for this?

I ended up creating a client without a secret (still without username), which is now working. Thanks!

Checking in to see if any updates have been made on this bug?

Curious if this ticket had been given any more thought?

I'm seeing something similar: ```Shell $ sam build Building resource 'PaymentsDataStreamFunction' Running PythonPipBuilder:ResolveDependencies Build Failed Error: PythonPipBuilder:ResolveDependencies - {pyyaml==5.3.1(sdist), pyrsistent==0.15.7(sdist)} ``` Both pyyaml & pyrsistent are inside my requirements.txt file,...

wheel is installed. `--use-container` also fails with a similar error but with different deps. I tried creating a brand new project which worked fine. So, it's probably something within my...

I'm experiencing this issue as well. Has anyone found a reasonable workaround?

Does anyone know if this feature work is planned?