-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ansible: async no-ops should return hash to ensure code doesn't crash #358
Conversation
I am a robot that works on MagicModules PRs! I built this PR into one or more PRs on other repositories, and when those are closed, this PR will also be merged and closed. |
77758d1
to
d358efc
Compare
I am (still) a robot that works on MagicModules PRs! I just wanted to let you know that your changes (as of commit 3b3f182) have been included in your existing downstream PRs. |
d358efc
to
2f540f1
Compare
I am (still) a robot that works on MagicModules PRs! I just wanted to let you know that your changes (as of commit bc49094) have been included in your existing downstream PRs. |
Tracked submodules are build/puppet/compute build/puppet/sql build/puppet/storage build/puppet/container build/puppet/dns build/puppet/pubsub build/puppet/resourcemanager build/chef/compute build/chef/sql build/chef/storage build/chef/container build/chef/dns build/terraform build/ansible.
Ansible: async no-ops should return hash to ensure code doesn't crash
This sometimes can result in a code crash.
[all]
[terraform]
[puppet]
[puppet-compute]
[puppet-container]
[puppet-dns]
[puppet-logging]
[puppet-pubsub]
[puppet-resourcemanager]
[puppet-sql]
[puppet-storage]
[chef]
[chef-compute]
[chef-container]
[chef-dns]
[chef-logging]
[chef-sql]
[chef-storage]
[ansible]