Comment 1 for bug 1706841

Adam, are there any patches up for review to fix this in the broken projects or links to the code that is broken by the recent python-barbicanclient relese? Can you post links to them?

The part in the report above about castellan being broken is not true, as was figured out in the comments on https://review.openstack.org/#/c/487721/1 .

Also, as far as I'm aware, the python-barbicanclient documentation does not recommend importing objects directly: "from barbicanclient import secrets", it recommends using the object managers that are created as part of the client as castellan does. Yes, it was bad to break backwards-compatibility without warning, but we also weren't aware that projects were using python-barbicanclient in a way that was not documented. Apologies for the trouble.