File: data.yaml

package info (click to toggle)
cloud-init 25.1.4-1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 12,052 kB
  • sloc: python: 134,399; sh: 3,879; makefile: 128; javascript: 30; xml: 22
file content (33 lines) | stat: -rw-r--r-- 1,410 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
cc_resolv_conf:
  description: |
    You should not use this module unless manually editing
    :file:`/etc/resolv.conf` is the correct way to manage nameserver
    information on your operating system.
    
    Many distros have moved away from manually editing ``resolv.conf`` so
    please verify that this is the preferred nameserver management method for
    your distro before using this module. Note that using :ref:`network_config`
    is preferred, rather than using this module, when possible.

    This module is intended to manage ``resolv.conf`` in environments where
    early configuration of ``resolv.conf`` is necessary for further
    bootstrapping and/or where configuration management such as Puppet or Chef
    own DNS configuration.

    When using a :ref:`datasource_config_drive` and a RHEL-like system,
    ``resolv.conf`` will also be managed automatically due to the available
    information provided for DNS servers in the :ref:`network_config_v2`
    format. For those who wish to have different settings, use this module.

    For the ``resolv_conf`` section to be applied, ``manage_resolv_conf`` must
    be set ``true``.

    .. note::
       For Red Hat with ``sysconfig``, be sure to set ``PEERDNS=no`` for all
       DHCP-enabled NICs.
  examples:
  - comment: |
      Example 1:
    file: cc_resolv_conf/example1.yaml
  name: Resolv Conf
  title: Configure ``resolv.conf``