| Summary: | ASTERISK-19088: CLONE -Implicit Assumption About Dynamic Features | ||||
| Reporter: | JoshE (n8ideas) | Labels: | |||
| Date Opened: | 2011-12-20 09:04:06.000-0600 | Date Closed: | 2011-12-20 09:04:14.000-0600 | ||
| Priority: | Minor | Regression? | |||
| Status: | Closed/Complete | Components: | Features | ||
| Versions: | 1.8.7.1 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | There appears to have been made an undocumented implicit assumption about the use of dynamic features / application maps. In order for the feature to actually be executed, it is assumed that the "#" or "*" key precedes it. However, it is legal to create the following application map: suppressone => 1,peer,Playback,en/silence/1 suppresstwo => 2,peer,Playback,en/silence/1 suppressthree => *33,peer,Playback,tt-monkeys testfeature => #9,peer,Playback,tt-monkeys Reload features and you'll see the output from 'features show': Dynamic Feature Default Current --------------- ------- ------- testfeature no def #9 suppressthree no def *33 suppresstwo no def 2 suppressone no def 1 However, in this setup, the only features that will actually be executed are the feature #9 and *33. The other features will all be ignored. There is nothing in the documentation which would suggest that it isn't OK to have a dynamic feature that doesn't begin with # or *. At a minimum, the documentation should probably be clarified... but I would actually have a use for the ability to use dynamic features that don't begin with the # or * keys. | ||||
| Comments: | |||||