Documentation

debconf - Configure a .deb package

New in version 1.6.

Synopsis

  • Configure a .deb package using debconf-set-selections. Or just query existing selections.

Requirements

The below requirements are needed on the host that executes this module.

  • debconf
  • debconf-utils

Parameters

Parameter Choices/Defaults Comments
name
required
Name of package to configure.

aliases: pkg
question
A debconf configuration setting.

aliases: selection, setting
unseen
bool
    Choices:
  • no ←
  • yes
Do not set 'seen' flag when pre-seeding.
value
Value to set the configuration to.

aliases: answer
vtype
    Choices:
  • boolean
  • error
  • multiselect
  • note
  • password
  • seen
  • select
  • string
  • text
  • title
  • text
The type of the value supplied.
seen was added in 2.2.

Notes

Note

  • This module requires the command line debconf tools.
  • A number of questions have to be answered (depending on the package). Use ‘debconf-show <package>’ on any Debian or derivative with the package installed to see questions/settings available.
  • Some distros will always record tasks involving the setting of passwords as changed. This is due to debconf-get-selections masking passwords.

Examples

- name: Set default locale to fr_FR.UTF-8
  debconf:
    name: locales
    question: locales/default_environment_locale
    value: fr_FR.UTF-8
    vtype: select

- name: set to generate locales
  debconf:
    name: locales
    question: locales/locales_to_be_generated
    value: en_US.UTF-8 UTF-8, fr_FR.UTF-8 UTF-8
    vtype: multiselect

- name: Accept oracle license
  debconf:
    name: oracle-java7-installer
    question: shared/accepted-oracle-license-v1-1
    value: 'true'
    vtype: select

- name: Specifying package you can register/return the list of questions and current values
  debconf:
    name: tzdata

Status

This module is flagged as stableinterface which means that the maintainers for this module guarantee that no backward incompatible interface changes will be made.

Maintenance

This module is flagged as core which means that it is maintained by the Ansible Core Team. See Module Maintenance & Support for more info.

For a list of other modules that are also maintained by the Ansible Core Team, see here.

Support

For more information about Red Hat’s support of this module, please refer to this Knowledge Base article

Author

  • Brian Coca (@bcoca)

Hint

If you notice any issues in this documentation you can edit this document to improve it.