ansible/cloud/google
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
..
__init__.py added __init__.py to new cloud subcategories so builds work again 2014-11-05 11:07:19 -05:00
gc_storage.py Several cleanups to many modules: 2015-05-11 12:15:53 -07:00
gce.py Update gce.py to correctly handle propagated metadata type from a mother template 2015-05-12 20:53:36 -07:00
gce_lb.py Several cleanups to many modules: 2015-05-11 12:15:53 -07:00
gce_net.py Several cleanups to many modules: 2015-05-11 12:15:53 -07:00
gce_pd.py Several cleanups to many modules: 2015-05-11 12:15:53 -07:00