hi!
there have been some changes to mysql-proxy in version 0.8.1 and
0.8.2 that affect its required parameters:
0.8.1:
> Admin Plugin
> * removed the default values for --admin-username and --admin-password
> * enforce --admin-username, --admin-password and --admin-lua-script to be set
> if the admin plugin is loaded (#53429)
0.8.2:
> * removed the "admin" plugin from the list of plugins loaded by default
I therefore would check the version of mysql-proxy and would
vary the output of the meta data accordingly, e.g. (pseudocode)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ocf_version_cmp "$version" "0.8.1"
ret=$?
if [ $ret -eq 1 ]; then
required=1
else
required=0
fi
..
echo <parameter name="admin_username" unique="0" required="$required">
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you consider this a proper way of handling such requirements
or should i simply set required="0" and handle the special
cases via some validate_all() method?
Thanks,
Raoul
--
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc. email. r.bhatia@ipax.at
Technischer Leiter
IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at
Barawitzkagasse 10/2/2/11 email. office@ipax.at
1190 Wien tel. +43 1 3670030
FN 277995t HG Wien fax. +43 1 3670030 15
____________________________________________________________________
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
there have been some changes to mysql-proxy in version 0.8.1 and
0.8.2 that affect its required parameters:
0.8.1:
> Admin Plugin
> * removed the default values for --admin-username and --admin-password
> * enforce --admin-username, --admin-password and --admin-lua-script to be set
> if the admin plugin is loaded (#53429)
0.8.2:
> * removed the "admin" plugin from the list of plugins loaded by default
I therefore would check the version of mysql-proxy and would
vary the output of the meta data accordingly, e.g. (pseudocode)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ocf_version_cmp "$version" "0.8.1"
ret=$?
if [ $ret -eq 1 ]; then
required=1
else
required=0
fi
..
echo <parameter name="admin_username" unique="0" required="$required">
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you consider this a proper way of handling such requirements
or should i simply set required="0" and handle the special
cases via some validate_all() method?
Thanks,
Raoul
--
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc. email. r.bhatia@ipax.at
Technischer Leiter
IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at
Barawitzkagasse 10/2/2/11 email. office@ipax.at
1190 Wien tel. +43 1 3670030
FN 277995t HG Wien fax. +43 1 3670030 15
____________________________________________________________________
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/