| Issue Number | 391 |
|---|---|
| Summary | SPIKE: EBMS Deployment Method Using Features Module |
| Created | 2016-07-07 11:19:11 |
| Issue Type | Improvement |
| Submitted By | Dugan, Amy (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2016-09-16 10:27:25 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.187674 |
Investigate the use of the Features Module to improve the efficiency and consistency of deploying EBMS across multiple tiers.
Outcomes of this investigation would include:
Pros/Cons of using the Features Module
Step-by-step approach document for how this could be accomplished, including what files would need to be modified.
~ZhangY41, I think you have done a lot of the investigation and initial work on this ticket, so it makes sense for you to complete that for the current EBMS release. Thanks!
I have created new features modules, and eliminated the ebms.install file (and everything which depended on it). This will be a developer-tested ticket (aside from the obvious ticket which might be filed in the event I've broken something in the process).
~ZhangY41: All of the EBMS message types have lost their message text value. I can see the message text in the EBMS Message Types features module for each of the message types, but they're missing when you look at the actual message types. What do I need to do to make the message types use their message text values?
Yijun said that there are bugs in the message module's implementation of support for the features module, so I have backed out the work for this ticket, and restored the original approach for deploying changes at her recommendation (but leaving in place the use of the features module to control wysiwyg editing which was rolled out with the previous release, and appears to be working). I believe the message types are working correctly again.
Elapsed: 0:00:00.000742