Remove deprecated amqp_allow_insecure_clients

... because it was deprecated during Wallaby cycle.

Change-Id: I6c8b52e3d2d94c11786debb8ea0ccb9adce1b407
This commit is contained in:
Takashi Kajinami 2022-02-08 22:20:00 +09:00
parent c4c41a75cd
commit 96a2a0adff
2 changed files with 4 additions and 10 deletions

View File

@ -231,10 +231,6 @@
# Defaults to $::os_service_default.
# Deprecated, use fetcher_backend instead
#
# [*amqp_allow_insecure_clients*]
# (Optional) Accept clients using either SSL or plain TCP
# Defaults to undef.
#
# [*auth_section*]
# (Optional) Config Section from which to load plugin specific options
# Defaults to undef
@ -294,7 +290,6 @@ class cloudkitty(
Optional[Hash] $metrics_config = undef,
# DEPRECATED PARAMETERS
$tenant_fetcher_backend = undef,
$amqp_allow_insecure_clients = undef,
$auth_section = undef,
$keystone_version = undef,
) {
@ -303,11 +298,6 @@ class cloudkitty(
warning('The parameter cloudkitty::tenant_fetcher_backend was deprecated and has no effect. Use fetcher_backend instead.')
}
if $amqp_allow_insecure_clients != undef {
warning('The amqp_allow_insecure_clients parameter is deprecated and \
will be removed in a future release.')
}
if $auth_section != undef {
warning('The cloudkitty::auth_section parameter is deprecated. Use the cloudkitty::fetcher_keystone class')
}

View File

@ -0,0 +1,4 @@
---
upgrade:
- |
The ``cloudkitty::amqp_allow_insecure_clients`` parameter has been removed.