goldyfruit.ibmcloud_automation.ic_resource_binding (1.0.4) — module

Manage resource bindings on IBM Cloud.

| "added in version" 2.9 of goldyfruit.ibmcloud_automation"

Authors: Gaëtan Trellu (@goldyfruit)

preview | supported by community

Install collection

Install with ansible-galaxy collection install goldyfruit.ibmcloud_automation:==1.0.4


Add to requirements.yml

  collections:
    - name: goldyfruit.ibmcloud_automation
      version: 1.0.4

Description

This module creates a new resource binding. A resource binding is the representation of an association between an application and a resource (service) instance.

Often, resource bindings contain the credentials (keys) that the application uses to communicate with the resource instance.


Requirements

Usage examples

  • Success
    Steampunk Spotter scan finished with no errors, warnings or hints.
- name: Create resource binding
  ic_resource_binding:
    binding: ibmcloud-resource-binding-baby
    source: ibmcloud-resource-instance-baby
    target: ibmcloud-resource-target-baby
  • Success
    Steampunk Spotter scan finished with no errors, warnings or hints.
- name: Delete resource binding
  ic_resource_binding:
    binding: ibmcloud-resource-binding-baby
    state: absent

Inputs

    
role:
    choices:
    - writer
    - reader
    - manager
    - administrator
    - operator
    - viewer
    - editor
    description:
    - The role name.
    type: str

state:
    choices:
    - present
    - absent
    default: present
    description:
    - Should the resource be present or absent.
    type: str

source:
    description:
    - The short or long ID of resource instance or alias.
    type: str

target:
    description:
    - The CRN of application to bind to in a specific environment, e.g. Dallas YP, CFEE
      instance.
    type: str

binding:
    description:
    - The name of the binding. Must be 180 characters or less and cannot include any special
      characters other than (space) - . _ :.
    required: true
    type: str

parameters:
    description:
    - Configuration options represented as key-value pairs. Service defined options are
      passed through to the target resource brokers, whereas platform defined options
      are not.
    - Must be a JSON object.
    type: str