mirror of
https://github.com/ansible-collections/google.cloud.git
synced 2025-08-05 13:44:29 -07:00
You can now set the iam configuration for a given bucket, you can set: 1. publicAccessPrevention and 2. uniformBucketLevelAccess no support for bucketPolicyOnly because according to the storage docs: Note: iamConfiguration also includes the bucketPolicyOnly field, which uses a legacy name but has the same functionality as the uniformBucketLevelAccess field. We recommend only using uniformBucketLevelAccess, as specifying both fields may result in unreliable behavior. Also added integration tests for this feature Signed-off-by: Jorge Gallegos <jgallego@redhat.com> |
||
---|---|---|
.. | ||
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.