ث œf‍م َّ—UdZddlZddlZddlmZddlmZddlmZddl m Z ddlmZm Z ddlmZdd lmZd Zddd eegeed«gdgdœZeed<e e«Zej*e«Zdede dededdf d„Zy)zERuncmd: run arbitrary commands at rc.local with output to the consoleéN)عdedent)عutil)عCloud)عConfig)ع MetaSchemaعget_meta_doc)عALL_DISTROS)عPER_INSTANCEaRun arbitrary commands at a rc.local like time-frame with output to the console. Each item can be either a list or a string. The item type affects how it is executed: * If the item is a string, it will be interpreted by ``sh``. * If the item is a list, the items will be executed as if passed to execve(3) (with the first arg as the command). Note that the ``runcmd`` module only writes the script to be run later. The module that actually runs the script is ``scripts_user`` in the :ref:`Final` boot stage. .. note:: all commands must be proper yaml, so you have to quote any characters yaml would eat (':' can be problematic) .. note:: when writing files, do not use /tmp dir as it races with systemd-tmpfiles-clean LP: #1707222. Use /run/somedir instead. ع cc_runcmdعRuncmdzRun arbitrary commandsa runcmd: - [ ls, -l, / ] - [ sh, -xc, "echo $(date) ': hello world!'" ] - [ sh, -c, echo "=========hello world'=========" ] - ls -l /root - [ wget, "http://example.org", -O, /tmp/index.html ] عruncmd)عidعnameعtitleعdescriptionعdistrosع frequencyعexamplesعactivate_by_schema_keysعmetarعcfgعcloudعargsعreturncَ`—d|vrtjd|«ytjj |jd«d«}|d} t j|«}t j||d«y#t$r&}t|«dj||««‚d}~wwxYw)Nr z:Skipping module named %s, no 'runcmd' key in configurationعscriptsiہz"Failed to shellify {} into file {})عLOGعdebugعosعpathعjoinع get_ipathrعshellifyع write_fileع Exceptionعtypeعformat)rrrrعout_fnعcmdعcontentعes ْء> B-آ!B(آ(B-)ع__doc__عloggingrعtextwraprع cloudinitrعcloudinit.cloudrعcloudinit.configrعcloudinit.config.schemarrعcloudinit.distrosr عcloudinit.settingsr عMODULE_DESCRIPTIONrع__annotations__ع getLoggerع__name__rعstrعlistr-©َr,ْr?s·ًٍLمغ فهف!ف#ك<ف)ف+ًذً4طط %ط%طˆ}طلً َ ًً!)کzٌ'€€jٌَ,گtس €à€g×رکس!€ً Pگً Pک6ً P¨%ً P°tً Pہô Pr>