[MXS-2136] passwd errors out as a attribute in [monitor] and [service] in maxscale.cnf Created: 2018-11-03  Updated: 2018-11-08  Resolved: 2018-11-08

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.3.0
Fix Version/s: 2.3.1

Type: Bug Priority: Major
Reporter: Austin Rutherford (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

Maxscale errors out when using Maxscale 2.2 maxscale.cnf files that have passwd instead of password as attributes in monitor and services. It should allow both password and passwd in 2.3 and give a deprication warning if we're changing this. It is also in 2.3 documentation that passwd should still work.



 Comments   
Comment by markus makela [ 2018-11-04 ]

A deprecation warning has been logged ever since 2.2.0.

I remembered wrong: the use of whitespace in object names was deprecated in 2.2 and a warning for that is logged. There was a note about the deprecation in the 2.0.1 release notes:
In the configuration entry for a service or monitor, the value of the password to be used can now be specified using password in addition to passwd. The use of the latter will be deprecated and removed in later releases of MaxScale.

Comment by markus makela [ 2018-11-04 ]

There were some references to the old parameter in example configurations but the parameter was only documented as password since 2.2.0 (password appears to have been already in the 2.0 release). I've changed them and also added a note that the parameter was deprecated in 2.2.0 and removed in 2.3.0. The documentation will get updated with the next release.

Comment by markus makela [ 2018-11-05 ]

Added back the support for passwd with a warning message about its deprecation.

Generated at Thu Feb 08 04:11:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.