# feature request ansible alias

**URL:** <https://forum.ansible.com/t/feature-request-ansible-alias/12315>\
**Category:** Ansible Project\
**Created:** [February 8, 2013, 6:13pm UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315 "2013-02-08T18:13:40Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fff\_Fff](https://avatars.discourse-cdn.com/v4/letter/f/5e9695/32.png) [@Fff\_Fff](https://forum.ansible.com/u/Fff_Fff)\
**Post date:** [February 8, 2013, 6:13pm UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315/1 "2013-02-08T18:13:40Z")

</div>

Rather than type “ansible” every time I want to do something I have created _alias an=‘/usr/bin/ansible’_ in .bashrc

I was wondering if something like this has been considered as a feature in ansible?

---

<div class="post-metadata">

**Author:** ![Seth\_Vidal](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Seth\_Vidal](https://forum.ansible.com/u/Seth_Vidal)\
**Post date:** [February 8, 2013, 6:22pm UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315/2 "2013-02-08T18:22:51Z")

</div>

I don't have any authority here but I'd say no to this.

You can make your own bash alias at any time and polluting the 2-letter namespace just seems like bad behavior.

on my relatively well-stocked fedora 18 system ansible\* are the only binaries within ans\<tab\>\<tab\> output.

So you're saving not a lot of chars by making it 'an'

my 2c - they are not necessarily of any value  
-sv

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [February 8, 2013, 7:10pm UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315/3 "2013-02-08T19:10:59Z")

</div>

I use some aliases 'ans' and 'anspb' for example.

Since this is easy to do in any shell or just by symlinking the  
binaries, no reason to add this as a feature.

---

<div class="post-metadata">

**Author:** ![jpmens1](https://avatars.discourse-cdn.com/v4/letter/j/e9c0ed/32.png) [@jpmens1](https://forum.ansible.com/u/jpmens1)\
**Post date:** [February 8, 2013, 7:25pm UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315/4 "2013-02-08T19:25:12Z")

</div>

> Rather than type "ansible" every time I want to do something I have created  
> \*alias an='/usr/bin/ansible' \*in .bashrc

I save 50% in typing: mine's called `a'.

> I was wondering if something like this has been considered as a feature in  
> ansible?

How is that supposed to be a feature? It's a shell alias. I also alias  
l='ls -l' but wouldn't dream of asking whoever maintains the GNU package  
to add that as a feature... No offence meant: it seems pointless to me,  
that's all. 🙂

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-JP

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [February 8, 2013, 7:37pm UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315/5 "2013-02-08T19:37:25Z")

</div>

Everyone needs to set up their own bash aliases.

Ansible will not be adding additional command wrappers.

---

<div class="post-metadata">

**Author:** ![Fff\_Fff](https://avatars.discourse-cdn.com/v4/letter/f/5e9695/32.png) [@Fff\_Fff](https://forum.ansible.com/u/Fff_Fff)\
**Post date:** [February 9, 2013, 12:44am UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315/6 "2013-02-09T00:44:55Z")

</div>

It would be a “feature” because the documentation would reflect it. Yes it’s easy enough to add your own bash for your own alias. Death by a thousand paper cuts.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [February 9, 2013, 1:50am UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315/7 "2013-02-09T01:50:00Z")

</div>

As nicely as I can say it, a small degree of Linux experience will be  
assumed with Ansible, to where we assume readers will know how to do  
this.

It keeps our docs from tiring out others by having too much basic  
material, though we do explain all the basic parts of ansible itself,  
as best we can, we also do not fully document  
the concept of a file permission, what an RPM is, etc.

---

<div class="post-metadata">

**Author:** ![Fff\_Fff](https://avatars.discourse-cdn.com/v4/letter/f/5e9695/32.png) [@Fff\_Fff](https://forum.ansible.com/u/Fff_Fff)\
**Post date:** [February 9, 2013, 2:22am UTC](https://forum.ansible.com/t/feature-request-ansible-alias/12315/8 "2013-02-09T02:22:58Z")

</div>

There are thousands of things that are simple for me to do. Problems is I have to do those thousand things and adding this it’s 1001. Again, death by 1001 papercuts.

I can easily set up my servers manually. Why go to all the trouble of using software like Ansible to do that?! You don’t need that…assuming you have a small degree of Linux experience.
