Service - Message Config Manager: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
=== Configuration tags === | === Configuration tags === | ||
= | <syntaxhighlight lang="JavaScript"> | ||
{ | |||
configKey: "ServiceName" | |||
configTag: "{service name}" // stored reference name of the service | |||
configValue: "" // deployed service name | |||
} | |||
</syntaxhighlight> | |||
* see [[Standard | == MsgCfgs == | ||
* see [[Standard message config for In Out topics]] | |||
=== Fields === | === Fields === | ||
| Line 23: | Line 30: | ||
; serviceName | ; serviceName | ||
: (partition key) | : (partition key) | ||
; | ; topicName | ||
: (sort key) | : (sort key) | ||
; msgCfg | ; msgCfg | ||
Latest revision as of 13:44, 3 May 2021
Overview
Maintians a record of the configuration for every message from every service in the project.
Repository
https://bitbucket.org/stb_working/message-config-manager/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
{
configKey: "ServiceName"
configTag: "{service name}" // stored reference name of the service
configValue: "" // deployed service name
}
MsgCfgs
Fields
- serviceName
- (partition key)
- topicName
- (sort key)
- msgCfg
- object containing the full msgCfg
Notes
- Currently restricting get Lambdas to return list of serviceNames and per serviceName list of msgCfgs, am not allowing full list of msgCfgs because fear it could exceed lambda payload limits, whereas per serviceName list should stay under the limits