<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/upstart/cloud-config-ssh.conf.disabled, 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>2010-01-14T22:00:28+00:00</updated>
<entry>
<title>functional cloud-config-ssh.conf now</title>
<updated>2010-01-14T22:00:28+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2010-01-14T22:00:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=89bff8f826040f7c9d1cc85880eaf016e72d2191'/>
<id>urn:sha1:89bff8f826040f7c9d1cc85880eaf016e72d2191</id>
<content type='text'>
This fixes LP: #506599 , LP: #507070 .

Also, here, we move config parsing out of the EC2Init class.
Instead the parsing of /etc/ec2-init/ec2-init.cfg is now done in the
CloudConfig class, and prepended to the cloud-config that comes in
from user data.  This means that values in user data will over-ride
the settings in /etc/ec2-init.

Still TODO is support reading the public and private key files from
the cloud-config
</content>
</entry>
<entry>
<title>moving towards getting apt-update-upgrade working</title>
<updated>2010-01-12T20:09:27+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@nelson</email>
</author>
<published>2010-01-12T20:09:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1376ffe4de1e9cdcf5544ccecf50a18f46f7ed30'/>
<id>urn:sha1:1376ffe4de1e9cdcf5544ccecf50a18f46f7ed30</id>
<content type='text'>
</content>
</entry>
</feed>
