You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2020. It is now read-only.
It looks like these were dropped in 0.3.0, but that breaks lots of things -- e.g. chef_environment no longer works (in fabfiles that define their own non-legacy tasks) because there's a try/except on from fabric.api import env, task, roles, output, which will raise an ImportError because fabric will be chef.fabric, and then the except block then has task being a passthrough, but that doesn't work, fabric will ignore legacy tasks if a fabfile defines its own. I'd guess the behavior of that try/except might be worth changing on its own too, but apologies if I've missed anything.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like these were dropped in 0.3.0, but that breaks lots of things -- e.g.
chef_environment
no longer works (in fabfiles that define their own non-legacy tasks) because there's a try/except onfrom fabric.api import env, task, roles, output
, which will raise an ImportError because fabric will bechef.fabric
, and then the except block then hastask
being a passthrough, but that doesn't work, fabric will ignore legacy tasks if a fabfile defines its own. I'd guess the behavior of that try/except might be worth changing on its own too, but apologies if I've missed anything.The text was updated successfully, but these errors were encountered: