Another thing to consider is splitting the cloud-init package into python-cloud-init for the Python packages, and cloud-init for the upstart scripts and configuration. Then juju can get just what it needs, without worrying about polluting the machine with unnecessary (and dangerous) upstart scripts.
Since it's going to take a little while to do this properly, I'm going to do what hazmat suggested for now; we'll manually add in the bootcmds, PGP key extraction, and apt-add-repository calls. I'll create a tech-debt bug to address this properly.
@smoser: thanks, that sounds good to me.
Another thing to consider is splitting the cloud-init package into python-cloud-init for the Python packages, and cloud-init for the upstart scripts and configuration. Then juju can get just what it needs, without worrying about polluting the machine with unnecessary (and dangerous) upstart scripts.
Since it's going to take a little while to do this properly, I'm going to do what hazmat suggested for now; we'll manually add in the bootcmds, PGP key extraction, and apt-add-repository calls. I'll create a tech-debt bug to address this properly.