As a Tazama system operator
I want to align the names of the different collections and consolidate all configuration collections into the same database
so that there is improved maintainability; and
so that there are consistent development practices; and
so that the system is as simple as possible to maintain and configure for an inexperienced user
Background
epic: consolidate configuration files into the Configuration database
#10
Database layout and contents in Tazama is inconsistent and out of date:
The Configuration database contains the following collections:
ChannelExpression: This collection intends to contain the configuration documents of the CADProc
configuration: This collection intends to contain the configuration documents of the rule processors
transactionConfiguration: This collection intends to contain the configuration documents of the TADProc
typologyExpression: This collection intends to contain the configuration documents of the typology processor
The networkmap database contains the following collection:
networkConfiguration: This collection intends to contain the configuration documents of the event director
The change
Remove the channelExpression collection (Dependent on the removal of the CADProc from the default Tazama flow)
Rename the "configuration" collection to the "ruleConfiguration" collection
a. Move rule configuration retrieval to the Tazama code library
b. Update rule processors to retrieve their configurations from the renamed collection by implementing the code from the Tazama code library
Rename the "typologyExpression" collection to the "typologyConfiguration" collection.
a. Move typology configuration retrieval to the Tazama code library
b. Update the typology processor to retrieve its configuration from the renamed collection by implementing the code from the Tazama code library
Remove the "transactionConfiguration" collection.
Move the "networkConfiguration" from the networkmap database to the Configuration database
a. Move ED configuration retrieval to the Tazama code library
b. Update the ED to retrieve its configuration from the renamed collection by implementing the code from the Tazama code library
Merged into dev and now the PR has been created to main . Once it has been merged , Scott will create a release version with the new changes made to the Arango Setup collection.
User Story
As a Tazama system operator I want to align the names of the different collections and consolidate all configuration collections into the same database so that there is improved maintainability; and so that there are consistent development practices; and so that the system is as simple as possible to maintain and configure for an inexperienced user
Background
epic: consolidate configuration files into the Configuration database #10
Database layout and contents in Tazama is inconsistent and out of date:
The Configuration database contains the following collections:
The networkmap database contains the following collection:
The change
Acceptance Criteria