__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
a
ah�i{ � @ sV d Z ddlZddlZddlmZ dZdZdZdZdZ dZ
dZ ee e
f d�dd �ZdS )
a?
Feature flags are used as a way to easily toggle configuration
**at build time**. They are provided to accommodate feature deprecation and
downstream configuration changes.
Currently used upstream values for feature flags are set in
``cloudinit/features.py``. Overrides to these values should be
patched directly (e.g., via quilt patch) by downstreams.
Each flag should include a short comment regarding the reason for
the flag and intended lifetime.
Tests are required for new feature flags, and tests must verify
all valid states of a flag, not just the default state.
� N)�DictTFz23.4)�returnc C s dd� t jd j�� D �S )z@Return a dict of applicable features/overrides and their values.c S s* i | ]"}t �d |�r|ttjd |��qS )z ^[_A-Z0-9]+$�cloudinit.features)�re�match�getattr�sys�modules)�.0�k� r �6/usr/lib/python3.9/site-packages/cloudinit/features.py�
<dictcomp> s �z get_features.<locals>.<dictcomp>r )r r �__dict__�keysr r r r
� get_features} s �r )�__doc__r r �typingr ZERROR_ON_USER_DATA_FAILUREZ+ALLOW_EC2_MIRRORS_ON_NON_AWS_INSTANCE_TYPESZ EXPIRE_APPLIES_TO_HASHED_USERSZ NETPLAN_CONFIG_ROOT_READ_ONLYZ%NOCLOUD_SEED_URL_APPEND_FORWARD_SLASHZAPT_DEB822_SOURCE_LIST_FILEZDEPRECATION_INFO_BOUNDARY�str�boolr r r r r
�<module> s
#