Revision f5f7c192
Added by Kamil Herbik about 7 years ago
manifests/consumer.pp | ||
---|---|---|
#
|
||
# $messaging_transport:: The AMQP transport name. Valid options are 'qpid' or 'rabbitmq'. The default is 'qpid'.
|
||
#
|
||
# $messaging_version:: Determines the version of packages related to the 'messaging transport protocol'.
|
||
#
|
||
# $messaging_cacert:: The (optional) absolute path to a PEM encoded CA certificate to validate the identity of the
|
||
# broker.
|
||
#
|
||
... | ... | |
$messaging_host = $pulp::consumer::params::messaging_host,
|
||
$messaging_port = $pulp::consumer::params::messaging_port,
|
||
$messaging_transport = $pulp::consumer::params::messaging_transport,
|
||
$messaging_version = $pulp::consumer::params::messaging_version,
|
||
$messaging_cacert = $pulp::consumer::params::messaging_cacert,
|
||
$messaging_clientcert = $pulp::consumer::params::messaging_clientcert,
|
||
$profile_minutes = $pulp::consumer::params::profile_minutes,
|
Also available in: Unified diff
Messaging transport version (#195)
- added new param 'messaging_version'
- it is related to the isue that 'python-gofer-qpid' and 'python-gofer-amqp'
get version number from the main pulp's 'version' value which is incorrect.
Changes to be committed:
- modified: manifests/init.pp
- modified: manifests/install.pp
- modified: manifests/params.pp
- new parameter 'messaging_transport_version'
- it is related to the issue that when $version is set to e.g. 2.12.0-1.el7 it is also assigned
to packages like 'python-gofer-qpid', 'python-gofer-amqp' or 'gofer' which do not have such number
Changes to be committed:
- modified: manifests/init.pp
- modified: manifests/params.pp
- modified: manifests/install.pp
- modified: manifests/consumer.pp
- modified: manifests/consumer/install.pp
- modified: manifests/consumer/params.pp
Added a "comma" in the 'ensure_packages' for $pulp::messaging_transport
An 'messaging_version' was documented but was not in the parameters part of the code.