f UdZddlZddlmZddlmZmZddlmZddl m Z ddl m Z m Z ddlmZej eZd d d Zd Zd ddegdeedgdgdZe ed<e eZdZdede dededdf dZy)z"Resolv Conf: configure resolv.confN)dedent) templaterutil)Cloud)Config) MetaSchema get_meta_doc) PER_INSTANCEz resolv.confzsystemd.resolved.conf)z/etc/resolv.confz/etc/systemd/resolved.confaUnless manually editing :file:`/etc/resolv.conf` is the correct way to manage nameserver information on your operating system, you do not want to use this module. 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 that wish to have different settings, use this module. In order 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. cc_resolv_confz Resolv ConfzConfigure resolv.conf) alpinefedoramarineropensusez opensuse-leapzopensuse-microoszopensuse-tumbleweedphotonrhelsle_hpcz sle-microsles openeulera manage_resolv_conf: true resolv_conf: nameservers: - 8.8.8.8 - 8.8.4.4 searchdomains: - foo.example.com - bar.example.com domain: example.com sortlist: - 10.0.0.1/255 - 10.0.0.2 options: rotate: true timeout: 1 manage_resolv_conf)idnametitle descriptiondistros frequencyexamplesactivate_by_schema_keysmetacfg}g}d|vrQ|djD];\}}t|ts|r|j|+|j|=||zD]}|d|= |j dsi|d<||d<t j d|tj|||y)Noptionsflagsz$Writing resolv.conf from template %s) items isinstanceboolappendgetLOGdebugrrender_to_file) template_fnparams target_fnamer! false_flagskeyvalflags A/usr/lib/python3/dist-packages/cloudinit/config/cc_resolv_conf.pygenerate_resolv_confr2fs EKFy)//1 ,HC#t$LL%&&s+  , #$ 9 d #$ ::i yF7OII4kB [,?rcfgcloudargsreturncd|vrtjd|ytj|ddstjd|yd|vrtj dy |j t |jj}t||d|jj y#t$rtj dYywxYw) a[ Handler for resolv.conf @param name: The module name "resolv_conf" from cloud.cfg @param cfg: A nested dict containing the entire cloud config contents. @param cloud: The L{CloudInit} object in use. @param log: Pre-initialized Python logger object to use for logging. @param args: Any module arguments from cloud.cfg rzFSkipping module named %s, no 'manage_resolv_conf' key in configurationNFzGSkipping module named %s, 'manage_resolv_conf' present but set to False resolv_confz3manage_resolv_conf True but no parameters provided!z0No template found, not rendering resolve configs)r*r+r,) r'r(rget_cfg_option_boolwarningget_template_filenameRESOLVE_CONFIG_TEMPLATE_MAPdistroresolve_conf_fnKeyErrorr2)rr4r5r6r*s r1handlerA}s3&  <    # #C)=u E  =  C IJ11 ' (D(D E =!\\11    FGs%,B77CC)__doc__loggingtextwrapr cloudinitrrcloudinit.cloudrcloudinit.configrcloudinit.config.schemarr cloudinit.settingsr getLogger__name__r'r=MODULE_DESCRIPTIONr__annotations__r2strlistrAr3r1rQs)%!#<+g!&"9 8   $%  *!55U+j+Z t @.+ + 6+ %+ t+ + r3