Accept 'password' in addition to 'passwd'
In the configuration section of services and monitors, the password to be used can now be specified using 'password' in addition to 'passwd'. If both are provided, then the value of 'passwd' is used. That way there cannot be any surprises, should someone for whatever reason currently (in 1.4.3 an invalid parameter will not prevent MaxScale from starting) have a 'password' entry in his config file. In the next release 'passwd' can be deprecated and in the release after that removed.
This commit is contained in:
@ -13,6 +13,17 @@ report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Updated Features
|
||||
|
||||
### Password parameter
|
||||
|
||||
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.
|
||||
|
||||
[SomeService]
|
||||
...
|
||||
password=mypasswd
|
||||
|
||||
### Routing hint priority change
|
||||
|
||||
Routing hints now have the highest priority when a routing decision is made. If
|
||||
|
||||
Reference in New Issue
Block a user