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
With the utility installed, I get the following error when I run my standard fabric tasks:
$ fab pull
/Users/rbernabe/virtualenvs/puppet/lib/python2.7/site-packages/awsfabrictasks/conf.py:35: UserWarning: Could not find the env.awsfab_settings_module. Make sure you run run awsfab tasks using the ``awsfab`` command (not fab)?
warn('Could not find the env.awsfab_settings_module. Make sure you run run awsfab tasks using the ``awsfab`` command (not fab)?')
[puppet-east.xxxx.com] Executing task 'pull'
[puppet-east.xxxx.com] run: git pull
[puppet-east.xxxx.com] out: Already up-to-date.
[puppet-east.xxxx.com] out:
Done.
Disconnecting from puppet-east.xxxx.com... done.
Should I be using awsfab even for my non aws-specific tasks?
The text was updated successfully, but these errors were encountered:
You do not have to use awsfab for non aws-specific task. Some of the built-in tasks get their defaults for keyword arguments from awsfabsettings.conf.awsfab_settings which causes this warning when you are importing them without awsfab. You have a few choices:
Ignore the warning.
Run all tasks using awsfab. You should not have any problems with this since awsfab extends fabric and adds a few cli options, a library of tasks and a configuration system. In other words it should be 100% compatible with fabric unless they add new options that name-crash with awsfab.
Put awsfab tasks in another file and run awsfab -f otherfile.py.
Awesome package, super useful!
With the utility installed, I get the following error when I run my standard fabric tasks:
Should I be using
awsfab
even for my non aws-specific tasks?The text was updated successfully, but these errors were encountered: