9cc80d5fed
If we are running on anything before trusty, we need to manually manage the repository because the available version of rabbitmq is not recent enough for our module. For trusty and later, the available version is too recent for us to use, so we have to turn off repo management. This is volatile, and needs a more permanent solution. Change-Id: I0db87d6c5cbecee8575d91e6f88ef43a947967ff
45 lines
1.3 KiB
Puppet
45 lines
1.3 KiB
Puppet
# Copyright (c) 2014 Hewlett-Packard Development Company, L.P.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
|
|
# == Class: storyboard::rabbit
|
|
#
|
|
# The StoryBoard Rabbit manifest installs a standalone rabbitmq instance
|
|
# which is used to handle deferred processing and reporting tasks for
|
|
# StoryBoard.
|
|
#
|
|
class storyboard::rabbit (
|
|
$rabbitmq_user = 'storyboard',
|
|
$rabbitmq_user_password
|
|
) {
|
|
|
|
require storyboard::params
|
|
|
|
class { 'rabbitmq':
|
|
service_manage => true,
|
|
delete_guest_user => true,
|
|
manage_repos => $storyboard::params::manage_rabbit_repo,
|
|
}
|
|
|
|
rabbitmq_user { $rabbitmq_user:
|
|
password => $rabbitmq_user_password
|
|
}
|
|
|
|
rabbitmq_user_permissions { "${rabbitmq_user}@/":
|
|
configure_permission => '.*',
|
|
read_permission => '.*',
|
|
write_permission => '.*',
|
|
require => Rabbitmq_user[$rabbitmq_user]
|
|
}
|
|
}
|