Metadata
- Source
- KETTLE-8
- Type
- Sub-task
- Priority
- Blocker
- Status
- Closed
- Resolution
- Fixed
- Assignee
- N/A
- Reporter
- Michelle D'Souza
- Created
2009-11-30T21:29:13.000-0500 - Updated
2014-03-03T14:19:15.914-0500 - Versions
-
- 0.1
- Fixed Versions
-
- 0.3
- Component
- N/A
Description
Currently we have an engageConfig.json file which contains configuration information for general Kettle as well as for Engage's use of Kettle. In order to make Kettle usable in contexts other then Engage we need to separate the Kettle specific and Engage specific configuration.
Comments
-
Michelle D'Souza commented
2010-03-29T21:23:16.000-0400 This work is complete in the ENGAGE-208 branch.
-
Antranig Basman commented
2013-08-13T13:58:39.458-0400 "new new Kettle" has now stripped out deployment-specific information (in this new case, GPII-universal specific, rather than engage-specific) from the main configuration.