iib credential

Overview

This resource allows you to manage dbparams (e.g. credentials) in IBM IIB realm.

Here is an example on how you should use this:

iib_credential { 'IIB107/ldap::myad.example.com':
  ensure   => 'present',
  username => 'myusername',
  password => 'extremlysecret',
}

Attributes

broker

This parameter specifies custom name for iib_broker in IBM IIB realm.

In example

'NODE1'

Back to overview of iib_credential

disable_corrective_change

Disable the modification of a resource when Puppet® decides it is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet® Server, Puppet® knows about adaptive and corrective changes. A corrective change is when Puppet® notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet® is managing. The normal Puppet® process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet® cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the `disable_corrective_change’ parameter, you can disable corrective changes on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ...
  disable_corrective_change => true,
  ...
}

When a corrective ensure does happen on the resource Puppet® will not modify the resource
and signal an error:

    Error: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/parameter: change from '10' to '20' failed: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change. (corrective)

Back to overview of iib_credential

disable_corrective_ensure

Disable the creation or removal of a resource when Puppet® decides is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet® Server, Puppet® knows about adaptive and corrective changes. A corrective change is when Puppet® notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet® is managing. The normal Puppet® process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet® cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the `disable_corrective_ensure’ parameter, you can disable corrective ensure present or ensure absent actions on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ensure                    => 'present',
  ...
  disable_corrective_ensure => true,
  ...
}

When a corrective ensure does happen on the resource Puppet® will not create or remove the resource
and signal an error:

    Error: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure.
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/ensure: change from 'absent' to 'present' failed: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure. (corrective)

Back to overview of iib_credential

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of iib_credential

instance

This shared parameter specifies iib_instance in IBM IIB realm.

Example name

'iib8'

Back to overview of iib_credential

name

This parameter specifies uniqe resource name for the credential (dbparams).

In example

‘IIB107/ldap::myad.example.com’

Back to overview of iib_credential

password

The password registered for this resource.

Back to overview of iib_credential

provider

The specific backend to use for this iib_credential resource. You will seldom need to specify this — Puppet® will usually discover the appropriate provider for your platform.Available providers are:

simple

Manage IIB credentials (dbparams)

Back to overview of iib_credential

resource_name

This parameter specifies the full resource name for these credentials (dbparams)

Back to overview of iib_credential

username

The username registered for this resource.

Back to overview of iib_credential