Resource Type: rabbitmq_parameter

Defined in:
lib/puppet/type/rabbitmq_parameter.rb
Providers:
rabbitmqctl

Overview

Type for managing rabbitmq parameters

Examples:

Create some rabbitmq_parameter resources

rabbitmq_parameter { 'documentumShovel@/':
  component_name => '',
  value          => {
      'src-uri'    => 'amqp://',
      'src-queue'  => 'my-queue',
      'dest-uri'   => 'amqp://remote-server',
      'dest-queue' => 'another-queue',
  },
}
rabbitmq_parameter { 'documentumFed@/':
  component_name => 'federation-upstream',
  value          => {
      'uri'     => 'amqp://myserver',
      'expires' => '360000',
  },
}
rabbitmq_parameter { 'documentumShovelNoMunging@/':
  component_name => '',
  value          => {
      'src-uri'    => 'amqp://',
      'src-exchange'  => 'my-exchange',
      'src-exchange-key' => '6',
      'src-queue'  => 'my-queue',
      'dest-uri'   => 'amqp://remote-server',
      'dest-exchange' => 'another-exchange',
  },
  autoconvert   => false,
}

Properties

  • component_name

    The component_name to use when setting parameter, eg: shovel or federation

  • ensure (defaults to: present)

    The basic property that the resource should be in.

    Supported values:
    • present
    • absent
  • value

    A hash of values to use with the component name you are setting

Parameters

  • autoconvert (defaults to: true)

    whether numeric strings from ‘value` should be converted to int automatically

    Supported values:
    • true
    • false
  • name (namevar)

    combination of name@vhost to set parameter for

    Supported values:
    • %r{^\S+@\S+$}
  • provider

    The specific backend to use for this ‘rabbitmq_parameter` resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.