You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robert Godfrey (Jira)" <ji...@apache.org> on 2020/07/15 09:27:00 UTC
[jira] [Commented] (QPID-8455) [Broker-J]Use allow/deny list
terminology for existing attributes and context variables
[ https://issues.apache.org/jira/browse/QPID-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158016#comment-17158016 ]
Robert Godfrey commented on QPID-8455:
--------------------------------------
I agree with these needing to be fixed, but I think we have to do this as part of a new minor release (e.g. 8.1) where the system can also update existing configs as part of the upgrade process. If we don't do it as part of an update (with a built in upgrade process) then we will break people's existing configurations.
> [Broker-J]Use allow/deny list terminology for existing attributes and context variables
> ---------------------------------------------------------------------------------------
>
> Key: QPID-8455
> URL: https://issues.apache.org/jira/browse/QPID-8455
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Dedeepya
> Priority: Major
> Fix For: qpid-java-broker-8.0.1, qpid-java-broker-7.1.9
>
>
> Rename attributes and context variables containing the term white/black list to allow/deny list.
> The names allow/deny list are more inlined with current industry naming standards.
> Example:
> The port derived attributes tlsCipherSuiteWhiteList and tlsCipherSuiteBlackList will have to be renamed to tlsCipherSuiteAllowList and tlsCipherSuiteDenyList respectively.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org