Node Meta-Data / KVP Support
Description
Acceptance / Success Criteria
None
relates to
Lucidchart Diagrams
Activity
Show:

Jesse White March 18, 2019 at 1:49 PM
PR merged, follow up work for UI changes are in .

Jesse White February 6, 2019 at 5:16 PM
For parameter substitution, we could adapt the Mate-Data DSL:
Examples:
${ctx:key} => ""
${ctx:key|default} => "default"
${ctx:key|ctx:key2|default} => "value of key 2 if set"
${ctx:key|ctx:key3|} => ""
Rules:
Element after last pipe is a literal
Everything before the last pipe is a variable
If no pipe, default to a blank string
Add support for associating and storing arbitrary key/value pairs with a node. These can be used as a flexible alternative to asset fields, which currently only support a set of fixed fields.
It should be possible to:
Provide these as part of the provisioning requisition
View/edit these in the UI
Access them from the DAO layer
Use the KVPs for parameter substitution in the monitor/collector/detector definitions