<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tests/data/roots/simple_ubuntu/etc/networks/interfaces, branch cla</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=cla</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=cla'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2012-09-26T23:29:50+00:00</updated>
<entry>
<title>Add a new example test that will patch utils and os</title>
<updated>2012-09-26T23:29:50+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@yahoo-inc.com</email>
</author>
<published>2012-09-26T23:29:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=f31a4e80aaaafca79eb6c808c81a6067f0c493b8'/>
<id>urn:sha1:f31a4e80aaaafca79eb6c808c81a6067f0c493b8</id>
<content type='text'>
functions so that they can be 'retargeted' to a temporary
directory, which allows us the ability to run a full set
of cloud-init stages.

Neat things:

1. All cloud-init code is unchanged (as long as it goes
   through the utils functions for most functionality)
2. Allows for a natural way to setup a temporary directory
   then patch the new directory as the new 'root' and then
   run cloud-init stages and then check the contents of 
   what was placed as desired.
</content>
</entry>
</feed>
