mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-02 19:16:15 +00:00
Fix Alembic upgrades.
A non-existent constraint was being referenced in the upgrade script. This patch corrects the problem by removing the reference. In addition, the head of the alembic branch referred to a non-existent revision. This has been fixed by referring to the proper revision. This patch fixes another realtime problem as well. Our Alembic scripts store booleans as yes or no values. However, Sorcery tries to insert "true" or "false" instead. This patch introduces a new boolean type that translates to "yes" or "no" instead. ASTERISK-26128 #close Change-Id: I51574736a881189de695a824883a18d66a52dcef
This commit is contained in:
@@ -97,6 +97,7 @@ static char *aco_option_type_string[] = {
|
||||
"IP Address", /* OPT_SOCKADDR_T, */
|
||||
"String", /* OPT_STRINGFIELD_T, */
|
||||
"Unsigned Integer", /* OPT_UINT_T, */
|
||||
"Boolean", /* OPT_YESNO_T, */
|
||||
};
|
||||
|
||||
void *aco_pending_config(struct aco_info *info)
|
||||
@@ -139,6 +140,10 @@ static aco_option_handler ast_config_option_default_handler(enum aco_option_type
|
||||
switch(type) {
|
||||
case OPT_ACL_T: return acl_handler_fn;
|
||||
case OPT_BOOL_T: return bool_handler_fn;
|
||||
/* Reading from config files, BOOL and YESNO are handled exactly the
|
||||
* same. Their difference is in how they are rendered to users
|
||||
*/
|
||||
case OPT_YESNO_T: return bool_handler_fn;
|
||||
case OPT_BOOLFLAG_T: return boolflag_handler_fn;
|
||||
case OPT_CHAR_ARRAY_T: return chararray_handler_fn;
|
||||
case OPT_CODEC_T: return codec_handler_fn;
|
||||
|
Reference in New Issue
Block a user