Looking at this, it seems like the 0.7.0 release covers most of the amazon changes (they added some sysvinit stuff, some yum install 'abstraction' as well, they adjusted subprocess exception throwing). They also added in a somewhat abstraction of yum/apt... They write out yum repo config files (thats different), and handle yum upgrades a little differently.... The 0.7.0 are more extensive (and imho better) so this bug might not be needed anymore...
Noteable additions:
1. It seems like they also can take base64 encoded userdata (from a response header??)
decoded_user_data = base64.urlsafe_b64decode(user_data)
for header in valid_headers: if decoded_user_data.startswith(header): returned_data = decoded_user_data break
2. It seems like they have a generic package install mechanism we might want to take (a config module):
a) Look for file (in that rpm), cc_package_setup.py
3. Similarly they generate repo configs, in cc_genrepo.py (might be useful again)
Looking at this, it seems like the 0.7.0 release covers most of the amazon changes (they added some sysvinit stuff, some yum install 'abstraction' as well, they adjusted subprocess exception throwing). They also added in a somewhat abstraction of yum/apt... They write out yum repo config files (thats different), and handle yum upgrades a little differently.... The 0.7.0 are more extensive (and imho better) so this bug might not be needed anymore...
Noteable additions:
1. It seems like they also can take base64 encoded userdata (from a response header??)
decoded_user_data = base64. urlsafe_ b64decode( user_data)
if decoded_ user_data. startswith( header) :
returned_ data = decoded_user_data
break
for header in valid_headers:
2. It seems like they have a generic package install mechanism we might want to take (a config module):
a) Look for file (in that rpm), cc_package_setup.py
3. Similarly they generate repo configs, in cc_genrepo.py (might be useful again)