Yeah, I understood the difference in when they were caching - but in the use case of ``list_features`` the ``activate_requests_caching`` won't ever be used.

I'm a little uneasy with the way the ``activate_requests_caching`` does the caching - if it means all installed libraries using requests also have that cache then that might not be the right way about it. It feels like caching should be a per-provider thing - as source code info is more important to be live than planning info for example.

Happy to merge if you add a config param to decide whether to call this on line 70 of ``deploystream/__init__.py`` :)