build(deps): bump github.com/jellydator/ttlcache/v2 from 2.11.1 to 3.0.1

[siretart]

Summary

I'm trying to package this library in Debian, so that it can used by container tools like podman and friends. I've packaged most of the dependencies, but while packaging https://github.com/jellydator/ttlcache/ I made the mistake of packaging version 3. In order to not have to downgrade the Debian package, I've decided to send you this PR to move forward to version 3. :-)

Release Note

Documentation

[haydentherapper]

Thank you for making these changes! I or one of the other maintainers will take a closer look next week. If you see any gaps in unit or e2e tests that would exercise the cache, it would be helpful to add those too.

[siretart]

Awesome, that's great to hear.

I'm struggling with running the e2e tests locally. For some reason, docker-compose is not playing well with podman on my laptop. Therefore, it's not obvious to me why the aws e2e test is not working. Any ideas?

[haydentherapper]

cmk, err = a.getCMK(ctx)
return cmk.PublicKey, err

Looks like it's panicking because cmk is nil. I'd add a "if err != nil { return nil err}" and see what error is occurring

[siretart]

@haydentherapper I (finally) gotten the docker-compose setup to work with my podman installation (was some sillyness on my side) and found the bug. Now it is passing for me locally.

[haydentherapper]

Thanks so much for making this change! Only question is if we should standardize on where the loader gets set, either on initialization (like in the GCP client) or on access (in the other clients). To me, it's probably cleaner to set it once on initialization.

[haydentherapper]

AWS failure is unrelated to PR

[haydentherapper]

Just one linter error!

[siretart]

I don't get the azure e2e failure, that is, that pass passes for me. Is it possible that the test reaches out to the internet?

[bobcallaway]

thanks!

[haydentherapper]

Looks good now! Thank you again for making these changes!