delta/cloud-init.git/cloudinit/config/cc_final_message.py, branch trunk

README: Mention move of revision control to git.

2016-08-10T15:06:15+00:00

cloud-init development has moved its revision control to git.
It is available at 
  https://code.launchpad.net/cloud-init

Clone with 
  git clone https://git.launchpad.net/cloud-init
or
  git clone git+ssh://git.launchpad.net/cloud-init

For more information see
  https://git.launchpad.net/cloud-init/tree/HACKING.rst

Fix up a ton of flake8 issues

2016-05-12T17:56:26+00:00

Apply pep8, pyflakes fixes for python2 and 3

2016-03-04T06:45:58+00:00

Update make check target to run pep8 and run pyflakes or pyflakes3
depending on the value of 'PYVER'.  This way the python3 build
environment does not need python2 and vice versa.

Also have make check run the 'yaml' test.

tox:  have tox run pep8 in the pyflakes

provide default final message in jinja to avoid WARN in log

2015-02-11T17:57:50+00:00

final_message: allow replacement of capital name keys.

2014-03-12T14:59:13+00:00

documentation of final_message in 
  doc/examples/cloud-config-final-message.txt
showed '$UPTIME' and '$TIMESTAMP' would be available, but
only the lower case versions of these strings were available.

This change just makes all lower case and upper case keys
available here to avoid breaking anyone who used the
functional-but-not-correctly-documented lower case names.

cc_final_message: write to log debug also

2013-09-25T17:51:52+00:00

Add the "None" datasource

2012-08-21T01:27:04+00:00

The None datasource is the last resort fallback datasource.  It is
identifiable by a property 'is_disconnected' that indicates that the
datasource used is "not connected to a datasource".

This will allow any thing that needs to run to still run in the absense
of a DataSource.

Also, we add a logging of the datasource found in final_message, and
a warning if the None datasource is found.

cc_final_message: fix pylint issue

2012-07-09T21:03:03+00:00

Revert back to using cheetah + adjust resultant code + templates

2012-07-09T20:41:45+00:00

At this point there is a mixture of "double hash" cheetah comments and '#*'
cheetah comments.

1. Move the welcome message template string to a constant at the top of the module

2012-07-02T17:56:22+00:00

2. Fix the usage of multi_log to log to only one of the places (for now)
3. Update comment about multi-log and why write_file isn't used in this case