Getting started

Default configuration

The role will enable APT proxy support automatically if http_proxy, https_proxy or ftp_proxy environment variables are set on a given host. They can be configured using the debops.environment Ansible role.

Unfortunately using the above environment variables directly through sudo is problematic. To mitigate that, you can use the inventory__*_environment variables configured in the playbook to provide the correct variables to the role. See the debops-playbooks documentation for more details.

Example inventory

The debops.apt_proxy role is included by default in the common.yml DebOps playbook, you don't need to add hosts to any groups to enable it.

Example playbook

If you are using this role without DebOps, here's an example Ansible playbook that uses the debops.apt_proxy role:


- name: Configure APT proxy
  collections: [ 'debops.debops', 'debops.roles01',
                 'debops.roles02', 'debops.roles03' ]
  hosts: [ 'debops_all_hosts', 'debops_service_apt_proxy' ]
  become: True

  environment: '{{ inventory__environment | d({})
                   | combine(inventory__group_environment | d({}))
                   | combine(inventory__host_environment  | d({})) }}'


    - role: apt_proxy
      tags: [ 'role::apt_proxy', 'skip::apt_proxy' ]

Ansible tags

You can use Ansible --tags or --skip-tags parameters to limit what tasks are performed during Ansible run. This can be used after a host was first configured to speed up playbook execution, when you are sure that most of the configuration is already in the desired state.

Available role tags:

Main role tag, should be used in the playbook to execute all tasks.