Hot-keys on this page
r m x p toggle line displays
j k next/prev highlighted chunk
0 (zero) top of page
1 (one) first highlighted chunk
# Authors: # Martin Nagy <mnagy@redhat.com> # Jason Gerard DeRose <jderose@redhat.com> # # Copyright (C) 2008 Red Hat # see file 'COPYING' for use and warranty information # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program. If not, see <http://www.gnu.org/licenses/>.
Process-wide static configuration and environment.
The standard run-time instance of the `Env` class is initialized early in the `ipalib` process and is then locked into a read-only state, after which no further changes can be made to the environment throughout the remaining life of the process.
For the per-request thread-local information, see `ipalib.request`. """
""" Store and retrieve environment variables.
First an foremost, the `Env` class provides a handy container for environment variables. These variables can be both set *and* retrieved either as attributes *or* as dictionary items.
For example, you can set a variable as an attribute:
>>> env = Env() >>> env.attr = 'I was set as an attribute.' >>> env.attr u'I was set as an attribute.' >>> env['attr'] # Also retrieve as a dictionary item u'I was set as an attribute.'
Or you can set a variable as a dictionary item:
>>> env['item'] = 'I was set as a dictionary item.' >>> env['item'] u'I was set as a dictionary item.' >>> env.item # Also retrieve as an attribute u'I was set as a dictionary item.'
The variable names must be valid lower-case Python identifiers that neither start nor end with an underscore. If your variable name doesn't meet these criteria, a ``ValueError`` will be raised when you try to set the variable (compliments of the `base.check_name()` function). For example:
>>> env.BadName = 'Wont work as an attribute' Traceback (most recent call last): ... ValueError: name must match '^[a-z][_a-z0-9]*[a-z0-9]$|^[a-z]$'; got 'BadName' >>> env['BadName'] = 'Also wont work as a dictionary item' Traceback (most recent call last): ... ValueError: name must match '^[a-z][_a-z0-9]*[a-z0-9]$|^[a-z]$'; got 'BadName'
The variable values can be ``str``, ``int``, or ``float`` instances, or the ``True``, ``False``, or ``None`` constants. When the value provided is an ``str`` instance, some limited automatic type conversion is performed, which allows values of specific types to be set easily from configuration files or command-line options.
So in addition to their actual values, the ``True``, ``False``, and ``None`` constants can be specified with an ``str`` equal to what ``repr()`` would return. For example:
>>> env.true = True >>> env.also_true = 'True' # Equal to repr(True) >>> env.true True >>> env.also_true True
Note that the automatic type conversion is case sensitive. For example:
>>> env.not_false = 'false' # Not equal to repr(False)! >>> env.not_false u'false'
If an ``str`` value looks like an integer, it's automatically converted to the ``int`` type. Likewise, if an ``str`` value looks like a floating-point number, it's automatically converted to the ``float`` type. For example:
>>> env.lucky = '7' >>> env.lucky 7 >>> env.three_halves = '1.5' >>> env.three_halves 1.5
Leading and trailing white-space is automatically stripped from ``str`` values. For example:
>>> env.message = ' Hello! ' # Surrounded by double spaces >>> env.message u'Hello!' >>> env.number = ' 42 ' # Still converted to an int >>> env.number 42 >>> env.false = ' False ' # Still equal to repr(False) >>> env.false False
Also, empty ``str`` instances are converted to ``None``. For example:
>>> env.empty = '' >>> env.empty is None True
`Env` variables are all set-once (first-one-wins). Once a variable has been set, trying to override it will raise an ``AttributeError``. For example:
>>> env.date = 'First' >>> env.date = 'Second' Traceback (most recent call last): ... AttributeError: cannot override Env.date value u'First' with 'Second'
An `Env` instance can be *locked*, after which no further variables can be set. Trying to set variables on a locked `Env` instance will also raise an ``AttributeError``. For example:
>>> env = Env() >>> env.okay = 'This will work.' >>> env.__lock__() >>> env.nope = 'This wont work!' Traceback (most recent call last): ... AttributeError: locked: cannot set Env.nope to 'This wont work!'
`Env` instances also provide standard container emulation for membership testing, counting, and iteration. For example:
>>> env = Env() >>> 'key1' in env # Has key1 been set? False >>> env.key1 = 'value 1' >>> 'key1' in env True >>> env.key2 = 'value 2' >>> len(env) # How many variables have been set? 2 >>> list(env) # What variables have been set? ['key1', 'key2']
Lastly, in addition to all the handy container functionality, the `Env` class provides high-level methods for bootstraping a fresh `Env` instance into one containing all the run-time and configuration information needed by the built-in freeIPA plugins.
These are the `Env` bootstraping methods, in the order they must be called:
1. `Env._bootstrap()` - initialize the run-time variables and then merge-in variables specified on the command-line.
2. `Env._finalize_core()` - merge-in variables from the configuration files and then merge-in variables from the internal defaults, after which at least all the standard variables will be set. After this method is called, the plugins will be loaded, during which third-party plugins can merge-in defaults for additional variables they use (likely using the `Env._merge()` method).
3. `Env._finalize()` - one last chance to merge-in variables and then the instance is locked. After this method is called, no more environment variables can be set during the remaining life of the process.
However, normally none of these three bootstraping methods are called directly and instead only `plugable.API.bootstrap()` is called, which itself takes care of correctly calling the `Env` bootstrapping methods. """
""" Prevent further changes to environment. """ '%s.__lock__() already called' % self.__class__.__name__ )
""" Return ``True`` if locked. """
""" Set the attribute named ``name`` to ``value``.
This just calls `Env.__setitem__()`. """
""" Set ``key`` to ``value``. """ SET_ERROR % (self.__class__.__name__, key, value) ) (self.__class__.__name__, key, self.__d[key], value) ) 'True': True, 'False': False, 'None': None, '': None, } else:
""" Return the value corresponding to ``key``. """
""" Raise an ``AttributeError`` (deletion is never allowed).
For example:
>>> env = Env() >>> env.name = 'A value' >>> del env.name Traceback (most recent call last): ... AttributeError: locked: cannot delete Env.name """ DEL_ERROR % (self.__class__.__name__, name) )
""" Return True if instance contains ``key``; otherwise return False. """
""" Return number of variables currently set. """
""" Iterate through keys in ascending order. """
""" Merge variables from ``kw`` into the environment.
Any variables in ``kw`` that have already been set will be ignored (meaning this method will *not* try to override them, which would raise an exception).
This method returns a ``(num_set, num_total)`` tuple containing first the number of variables that were actually set, and second the total number of variables that were provided.
For example:
>>> env = Env() >>> env._merge(one=1, two=2) (2, 2) >>> env._merge(one=1, three=3) (1, 2) >>> env._merge(one=1, two=2, three=3) (0, 3)
Also see `Env._merge_from_file()`.
:param kw: Variables provides as keyword arguments. """
""" Merge variables from ``config_file`` into the environment.
Any variables in ``config_file`` that have already been set will be ignored (meaning this method will *not* try to override them, which would raise an exception).
If ``config_file`` does not exist or is not a regular file, or if there is an error parsing ``config_file``, ``None`` is returned.
Otherwise this method returns a ``(num_set, num_total)`` tuple containing first the number of variables that were actually set, and second the total number of variables found in ``config_file``.
This method will raise a ``ValueError`` if ``config_file`` is not an absolute path. For example:
>>> env = Env() >>> env._merge_from_file('my/config.conf') Traceback (most recent call last): ... ValueError: config_file must be an absolute path; got 'my/config.conf'
Also see `Env._merge()`.
:param config_file: Absolute path of the configuration file to load. """ 'config_file must be an absolute path; got %r' % config_file )
""" Append path components in ``parts`` to base path ``self[key]``.
For example:
>>> env = Env() >>> env.home = '/people/joe' >>> env._join('home', 'Music', 'favourites') u'/people/joe/Music/favourites' """
'%s.%s() already called' % (self.__class__.__name__, name) )
""" Initialize basic environment.
This method will perform the following steps:
1. Initialize certain run-time variables. These run-time variables are strictly determined by the external environment the process is running in; they cannot be specified on the command-line nor in the configuration files.
2. Merge-in the variables in ``overrides`` by calling `Env._merge()`. The intended use of ``overrides`` is to merge-in variables specified on the command-line.
3. Intelligently fill-in the *in_tree*, *context*, *conf*, and *conf_default* variables if they haven't been set already.
Also see `Env._finalize_core()`, the next method in the bootstrap sequence.
:param overrides: Variables specified via command-line options. """
# Set run-time variables (cannot be overridden):
# Merge in overrides:
# Determine if running in source tree: self.bin == self.site_packages and path.isfile(path.join(self.bin, 'setup.py')) ): else:
# Set dot_ipa:
# Set context
# Set confdir: else:
# Set conf (config file for this context):
# Set conf_default (default base config used in all contexts):
# Set plugins_on_demand:
""" Complete initialization of standard IPA environment.
This method will perform the following steps:
1. Call `Env._bootstrap()` if it hasn't already been called.
2. Merge-in variables from the configuration file ``self.conf`` (if it exists) by calling `Env._merge_from_file()`.
3. Merge-in variables from the defaults configuration file ``self.conf_default`` (if it exists) by calling `Env._merge_from_file()`.
4. Intelligently fill-in the *in_server* , *logdir*, and *log* variables if they haven't already been set.
5. Merge-in the variables in ``defaults`` by calling `Env._merge()`. In normal circumstances ``defaults`` will simply be those specified in `constants.DEFAULT_CONFIG`.
After this method is called, all the environment variables used by all the built-in plugins will be available. As such, this method should be called *before* any plugins are loaded.
After this method has finished, the `Env` instance is still writable so that 3rd-party plugins can set variables they may require as the plugins are registered.
Also see `Env._finalize()`, the final method in the bootstrap sequence.
:param defaults: Internal defaults for all built-in variables. """
# Merge in context config file and then default config file:
# Determine if in_server:
# Set logdir: else:
# Set log file:
""" Finalize and lock environment.
This method will perform the following steps:
1. Call `Env._finalize_core()` if it hasn't already been called.
2. Merge-in the variables in ``lastchance`` by calling `Env._merge()`.
3. Lock this `Env` instance, after which no more environment variables can be set on this instance. Aside from unit-tests and example code, normally only one `Env` instance is created, which means that after this step, no more variables can be set during the remaining life of the process.
This method should be called after all plugins have been loaded and after `plugable.API.finalize()` has been called.
:param lastchance: Any final variables to merge-in before locking. """ |