o w7e @sUdZddlZddlZddlmZddlmZmZmZddl m Z ddl m Z ddl mZmZddlmZeeZeZd gZd d d ed eedgedgdZeed<eeZdede de deddf ddZdS)z:Bootcmd: run arbitrary commands early in the boot process.N)dedent)subp temp_utilsutil)Cloud)Config) MetaSchema get_meta_doc) PER_ALWAYSall cc_bootcmdBootcmdz0Run arbitrary commands early in the boot processa This module runs arbitrary commands very early in the boot process, only slightly after a boothook would run. This is very similar to a boothook, but more user friendly. The environment variable ``INSTANCE_ID`` will be set to the current instance id for all run commands. Commands can be specified either as lists or strings. For invocation details, see ``runcmd``. .. note:: bootcmd should only be used for things that could not be done later in the boot process. .. note:: when writing files, do not use /tmp dir as it races with systemd-tmpfiles-clean LP: #1707222. Use /run/somedir instead. z bootcmd: - echo 192.168.1.130 us.archive.ubuntu.com > /etc/hosts - [ cloud-init-per, once, mymkfs, mkfs, /dev/vdb ] bootcmd)idnametitle descriptiondistrosexamples frequencyactivate_by_schema_keysmetarcfgcloudargsreturnc Csd|vr td|dStjdde}zt|d}|t||Wnt y>}z t tdt |d}~wwz t j }|}|rQt ||d<d|jg} tj| |dd Wnt ynt td |wWddS1szwYdS) Nrz;Skipping module named %s, no 'bootcmd' key in configurationz.sh)suffixzFailed to shellify bootcmd: %s INSTANCE_IDz/bin/shF)envcapturezFailed to run bootcmd module %s)LOGdebugrExtendedTemporaryFilershellifywrite encode_textflush Exceptionlogexcstrosenvironcopyget_instance_idrr) rrrrtmpfcontenteriidcmdr3=/usr/lib/python3/dist-packages/cloudinit/config/cc_bootcmd.pyhandleDs8     "r5)__doc__loggingr*textwrapr cloudinitrrrcloudinit.cloudrcloudinit.configrcloudinit.config.schemarr cloudinit.settingsr getLogger__name__r rrr__annotations__r)listr5r3r3r3r4s8       %"