ansible-personal/roles/common/tasks/packages_Ubuntu.yml

---

- block:
  - name: Configure apt mirror
    template: src=sources.list.j2 dest=/etc/apt/sources.list owner=root group=root mode=0644
    when: ansible_architecture != 'armv7l'

  - name: Upgrade base OS
    apt: upgrade=dist update_cache=yes

  - name: Install base packages
    apt: pkg={{ item }}
    loop:
      - git
      - tmux
      - iotop
      - htop
      - strace
      - s3cmd
      - cron-apt
      - safe-rm
      - debian-goodies
      - mosh
      - python-pycurl # for ansible's apt_repository
      - lzop
      - vim
      - lrzip
      - unzip
      - apt-transport-https # for https support in apt

  - name: Security hardening (CIS Benchmark 1.0)
    apt: pkg={{ item }} state=absent purge=yes
    loop:
      - whoopsie # CIS 4.1
      - apport   # CIS 4.1

  - name: Remove annoying packages
    apt: pkg={{ item }} state=absent purge=yes
    loop:
      - command-not-found
      - command-not-found-data
      - python3-commandnotfound

  - name: Configure cron-apt
    import_tasks: cron-apt.yml
    tags: cron-apt

  - name: Install tarsnap
    import_tasks: tarsnap.yml
  tags: packages

# vim: set sw=2 ts=2:
Initial commit Signed-off-by: Alan Orth <alan.orth@gmail.com> 2014-08-16 23:35:57 +02:00			`---`

roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html 2018-04-26 15:58:35 +02:00			`- block:`
			`- name: Configure apt mirror`
			`template: src=sources.list.j2 dest=/etc/apt/sources.list owner=root group=root mode=0644`
			`when: ansible_architecture != 'armv7l'`
Initial commit Signed-off-by: Alan Orth <alan.orth@gmail.com> 2014-08-16 23:35:57 +02:00
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html 2018-04-26 15:58:35 +02:00			`- name: Upgrade base OS`
			`apt: upgrade=dist update_cache=yes`
Initial commit Signed-off-by: Alan Orth <alan.orth@gmail.com> 2014-08-16 23:35:57 +02:00
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html 2018-04-26 15:58:35 +02:00			`- name: Install base packages`
			`apt: pkg={{ item }}`
			`loop:`
			`- git`
			`- tmux`
			`- iotop`
			`- htop`
			`- strace`
			`- s3cmd`
			`- cron-apt`
			`- safe-rm`
			`- debian-goodies`
			`- mosh`
			`- python-pycurl # for ansible's apt_repository`
			`- lzop`
			`- vim`
			`- lrzip`
			`- unzip`
			`- apt-transport-https # for https support in apt`
Initial commit Signed-off-by: Alan Orth <alan.orth@gmail.com> 2014-08-16 23:35:57 +02:00
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html 2018-04-26 15:58:35 +02:00			`- name: Security hardening (CIS Benchmark 1.0)`
			`apt: pkg={{ item }} state=absent purge=yes`
			`loop:`
			`- whoopsie # CIS 4.1`
			`- apport # CIS 4.1`

			`- name: Remove annoying packages`
			`apt: pkg={{ item }} state=absent purge=yes`
			`loop:`
			`- command-not-found`
			`- command-not-found-data`
			`- python3-commandnotfound`
Initial commit Signed-off-by: Alan Orth <alan.orth@gmail.com> 2014-08-16 23:35:57 +02:00
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html 2018-04-26 15:58:35 +02:00			`- name: Configure cron-apt`
			`import_tasks: cron-apt.yml`
			`tags: cron-apt`
roles/common: Add vim modeline Signed-off-by: Alan Orth <alan.orth@gmail.com> 2015-05-24 22:55:04 +02:00
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html 2018-04-26 15:58:35 +02:00			`- name: Install tarsnap`
			`import_tasks: tarsnap.yml`
roles/common: Use dynamic include_tasks for packages Basically, when using conditionals or variables in your tasks you should use include_tasks instead of import_tasks. The down side is that you now need to tag all included tasks individually or with a block, unlike when using static imports (tags are applied to all imported child tasks). I would actually like to reduce this task to a single one that uses the host's ansible_distribution variable, but Ansible 2.5.1 currently gives the following error: ansible_distribution is undefined. 2018-04-25 17:46:28 +02:00			`tags: packages`
roles/common: Add tasks to install tarsnap Now that Tarsnap has official packages this is one less thing that needs to be manually installed from source after bringing a machine up. See: http://mail.tarsnap.com/tarsnap-announce/msg00037.html 2017-02-07 16:28:35 +01:00
roles/common: Add vim modeline Signed-off-by: Alan Orth <alan.orth@gmail.com> 2015-05-24 22:55:04 +02:00			`# vim: set sw=2 ts=2:`