mirror of
https://github.com/ansible-collections/google.cloud.git
synced 2025-10-17 13:51:41 -07:00
As per https://cloud.google.com/bigquery/docs/reference/rest/v2/tables#TableFieldSchema the `fields` attribute can recursively define more fields if the `type` attribute is RECORD. There is no way to define recursive argument spec in ansible modules, but if sent as `raw`: > The raw type, performs no type validation or type casting, and maintains the type of the passed value. (from https://docs.ansible.com/ansible/latest/dev_guide/developing_program_flow_modules.html#argument-spec) Which works for what we're trying to accomplish here. Also added integration test for this change |
||
---|---|---|
.. | ||
doc_fragments | ||
filter | ||
inventory | ||
lookup | ||
module_utils | ||
modules | ||
README.md |
Collections Plugins Directory
This directory can be used to ship various plugins inside an Ansible collection. Each plugin is placed in a folder that
is named after the type of plugin it is in. It can also include the module_utils
and modules
directory that
would contain module utils and modules respectively.
Here is an example directory of the majority of plugins currently supported by Ansible;
└── plugins
├── action
├── become
├── cache
├── callback
├── cliconf
├── connection
├── filter
├── httpapi
├── inventory
├── lookup
├── module_utils
├── modules
├── netconf
├── shell
├── strategy
├── terminal
├── test
└── vars
A full list of plugin types can be found at Working With Plugins.