6d23d20f2f
This is preparation for a later version of ansbile-lint, which finds missing names on blocks. This seems a reasonable rule, and the Ansible manual says [1] Names for blocks have been available since Ansible 2.3. We recommend using names in all tasks, within blocks or elsewhere, for better visibility into the tasks being executed when you run the playbook. This simply adds a name tag for blocks that are missing it. This should have no operational change, but allows us to update the linter in a follow-on change. [1] https://docs.ansible.com/ansible/latest/user_guide/playbooks_blocks.html Change-Id: I92ed4616775650aced352bc9088a07e919f1a25f |
||
|---|---|---|
| .. | ||
| defaults | ||
| meta | ||
| tasks | ||
| README.rst | ||
Upload logs to IBM Cloud Storage
Before using this role, create a cloud object storage service instance and a service credential.
You may create a bucket within the instance, or allow this role to create the bucket (or buckets) for you.
Role Variables
If partitioning is not enabled, this is the name of the bucket which will be used. If partitioning is enabled, then this will be used as the prefix for the bucket name which will be separated from the partition name by an underscore. For example, "logs_42" would be the bucket name for partition 42.
If the bucket is created, this storage location will be used as the location constraint.
The API key that was created as part of the service credential. This is required.
The instance id that appears in the service credential. This is required.
The cloud storage endpoint. This is required.