mirror of https://github.com/sipwise/ngcpcfg.git
This makes it possible to use more specific config.yml files either for a pair of nodes, for settings that will always affect both, or for the HA names, for settings that might affect all A or B nodes. This matches the support in the template files. We need to move sourcing the ha_features and carrier_features before sourcing init, as now the ngcpcfg.cfg file can use these variables if set. Change-Id: Ic6b32acceb8f020f48c3afa09d9e84252b3531e7changes/53/39853/2
parent
35e8e975d2
commit
354e7578c5
@ -0,0 +1,2 @@
|
||||
ha enabled:
|
||||
pair enabled:
|
||||
@ -0,0 +1,2 @@
|
||||
ha enabled: yes
|
||||
pair enabled: yes
|
||||
@ -0,0 +1,3 @@
|
||||
---
|
||||
ha:
|
||||
enabled: yes
|
||||
@ -0,0 +1,3 @@
|
||||
---
|
||||
pair:
|
||||
enabled: yes
|
||||
@ -0,0 +1,2 @@
|
||||
ha enabled: [% ha.enabled %]
|
||||
pair enabled: [% pair.enabled %]
|
||||
Loading…
Reference in new issue