Yeah. Here's the result of all those:
trevor:~ $ ansible apps01 -m ping -i inventory.conf
apps01 | FAILED => unsupported connection type: ssh
trevor:~ $ ansible apps01 -c paramiko -m ping -i inventory.conf
apps01 | FAILED => unsupported connection type: paramiko
trevor:~ $ ansible localhost -c lo
I hadn't used Ansible on my laptop for a while, and now when returning to
projects that I was working on before, I'm stuck on a fatal:
fatal: [test-centos01] => unsupported connection type: ssh
I'm encountering this from a project with a VagrantFile that used to boot
and provision just fine.
had to undo something of that severity, you would use ansible to
> rebuild the box.
>
> For simpler things, just maintain a list of packages to remove, that
> should be sufficient. And maybe users.
>
>
>
> On Thu, Sep 11, 2014 at 5:42 PM, Trevor G >
> wrote:
>
&
bsent
> with_items: uninstall_packages
>
> Which would be a reasonable solution.
>
> We do somewhat similar things in our Tower install playbooks when we no
> longer use a particular subcomponent.
>
>
>
> On Wed, Sep 10, 2014 at 7:48 PM, Trevor G >
> wrote:
&g
It's great that I can easily pull in different roles into my playbooks. By
default, anything under tasks/main will get run (usually as an installation
process). I was wondering if there were any best practices for packaging a
list of uninstall tasks within the role as well to undo any changes
