%PDF- %PDF-
Direktori : /proc/self/root/usr/lib/python2.7/site-packages/cloudinit/config/ |
Current File : //proc/self/root/usr/lib/python2.7/site-packages/cloudinit/config/cc_snap_config.pyc |
� oB�]c @ s| d Z d d l m Z d d l m Z d d l m Z e j e � Z e Z d Z d Z d d � Z d d � Z d � Z d S( s@ Snap Config ----------- **Summary:** snap_config modules allows configuration of snapd. **Deprecated**: Use :ref:`snap` module instead. This module will not exist in cloud-init 18.3. This module uses the same ``snappy`` namespace for configuration but acts only only a subset of the configuration. If ``assertions`` is set and the user has included a list of assertions then cloud-init will collect the assertions into a single assertion file and invoke ``snap ack <path to file with assertions>`` which will attempt to load the provided assertions into the snapd assertion database. If ``email`` is set, this value is used to create an authorized user for contacting and installing snaps from the Ubuntu Store. This is done by calling ``snap create-user`` command. If ``known`` is set to True, then it is expected the user also included an assertion of type ``system-user``. When ``snap create-user`` is called cloud-init will append '--known' flag which instructs snapd to look for a system-user assertion with the details. If ``known`` is not set, then ``snap create-user`` will contact the Ubuntu SSO for validating and importing a system-user for the instance. .. note:: If the system is already managed, then cloud-init will not attempt to create a system-user. **Internal name:** ``cc_snap_config`` **Module frequency:** per instance **Supported distros:** any with 'snapd' available **Config keys**:: #cloud-config snappy: assertions: - | <assertion 1> - | <assertion 2> email: user@user.org known: true i����( t log( t PER_INSTANCE( t utilt snaps( /var/lib/cloud/instance/snapd.assertionsc C s� | s g } n t | t � s9 t d j d | � � � n t d g } d j | � } t | � d k ru t d � � n x. | D]&