HelenaTian 1b614172f5 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:)		2016-12-08 11:23:23 -05:00
..
amazon	minor doc fixes, version added for latest feature	2016-12-08 11:23:22 -05:00
azure	ensure password or ssh cert specified	2016-12-08 11:23:20 -05:00
digital_ocean	Updating cloud modules with proper github author information	2016-12-08 11:23:07 -05:00
docker	Add optional signal parameter when killing docker container	2016-12-08 11:23:23 -05:00
google	Update gce.py to correctly handle propagated metadata type from a mother template	2016-12-08 11:23:23 -05:00
linode	Updating cloud modules with proper github author information	2016-12-08 11:23:07 -05:00
openstack	Add new os_nova_flavor module.	2016-12-08 11:23:22 -05:00
rackspace	Fix some remaining rax asg idempotency checks	2016-12-08 11:23:10 -05:00
vmware	removed required together for resource pools, clusters, and template deployments. fixes inability to deploy from template on vsphere clusters without resource pools. Also, resource pools and cluster should not be required together as they are independant in vsphere	2016-12-08 11:23:21 -05:00
__init__.py	package files	2016-12-08 11:22:22 -05:00