U Ad| @sUdZddlZddlmZddlmZddlmZmZm Z ddl m Z ddl m Z ddlmZmZdd lmZeZd gZd d d edeedgedgdZeed<eeZee e eeddddZdS)z:Bootcmd: run arbitrary commands early in the boot process.N)Logger)dedent)subp temp_utilsutil)Cloud)Config) MetaSchema get_meta_doc) PER_ALWAYSallZ cc_bootcmdZBootcmdz0Run 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)idnametitleZ descriptiondistrosZexamples frequencyZactivate_by_schema_keysmeta)rcfgcloudlogargsreturnc Csd|kr|d|dStjdd}z*t|d}|t||Wn6tk r}zt |dt |W5d}~XYnXz@t j }|} | rt | |d<d|jg} tj| |dd Wn$tk rt |d |YnXW5QRXdS) Nr z;Skipping module named %s, no 'bootcmd' key in configurationz.sh)suffixzFailed to shellify bootcmd: %sZ INSTANCE_IDz/bin/shF)envZcapturezFailed to run bootcmd module %s)debugrZExtendedTemporaryFilerZshellifywriteZ encode_textflush ExceptionZlogexcstrosenvironcopyZget_instance_idrr) rrrrrZtmpfZcontenterZiidcmdr%=/usr/lib/python3/dist-packages/cloudinit/config/cc_bootcmd.pyhandleBs0    r')__doc__r ZloggingrtextwraprZ cloudinitrrrZcloudinit.cloudrZcloudinit.configrZcloudinit.config.schemar r Zcloudinit.settingsr rrr__annotations__rlistr'r%r%r%r& s@      %