ansible/cloud
HelenaTian f620a0ac41 Update gce.py to correctly handle propagated metadata type from a mother template
My project is using Ansible to automate cloud build process. Ansible has a core module gce.py for managing GCE instances. 
  We've come across a use case that's not yet supported - when executing ansible-playbook, if a child template is included, then metadata which is defined in and propagated from the mother template is treated as string type and not parsed correctly(which instead is dictionary type), and triggers release flow failure.
   We currently put some fix by explicitly casting metadata to string type in our own branch, but would like to contribute the fix to Ansible so that everyone onboarding GCE and using Ansible for release management could benefit from it, or hear owner's opinion on fixing the issue if there's a better fix in owner's mind:)
2015-05-12 20:53:36 -07:00
..
amazon [ec2_vol] Find or Create volume by name 2015-05-12 07:06:37 +02:00
azure Several cleanups to many modules: 2015-05-11 12:15:53 -07:00
digital_ocean Fixing digital_ocean documentation and a bug in os_subnet 2015-05-12 10:32:43 -05:00
docker Several cleanups to many modules: 2015-05-11 12:15:53 -07:00
google Update gce.py to correctly handle propagated metadata type from a mother template 2015-05-12 20:53:36 -07:00
linode Several cleanups to many modules: 2015-05-11 12:15:53 -07:00
openstack Fixing digital_ocean documentation and a bug in os_subnet 2015-05-12 10:32:43 -05:00
rackspace Prevent an empty error message 2015-03-10 11:30:14 -05:00
vmware Several cleanups to many modules: 2015-05-11 12:15:53 -07:00
__init__.py package files 2014-09-26 11:05:47 -04:00