| Summary: | ASTERISK-25238: ARI: Support push configuration | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2015-07-08 23:10:03 | Date Closed: | 2015-07-27 11:31:32 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_ari |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | In discussions at AstriDevCon and elsewhere, the notion of push configuration has come up several times. The idea, essentially, is to have a 'realtime'-esque style of configuration where Asterisk would not go and retrieve the configuration, but would instead have an external system push configuration to it on an as-needed basis. At the same time, when configuration is pushed to it, Asterisk should persist said configuration to permanent storage if configured to do so.
The patch being put up for review accomplishes this by adding a new resource path to the existing {{asterisk}} resource - {{asterisk/config/dynamic}}. The resource supports the standard CRUD operations, and works only on sorcery derived objects. If the sorcery object is created via the API, then the object will be persisted in the backing storage configured for that object type. If the object cannot be persisted, the API call fails. Once pushed, the next operation that requires that resource will attempt to use it. This allows for Asterisk to be treated in a much more 'generic' fashion, and for external system to maintain which PJSIP configuration (for example) lives on which Asterisk machine without any database manipulation or Asterisk reloads. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2015-07-26 11:53:01.104-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. | ||