Simple Implementation of loading sections into daemon using libby config injestion #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a better implementation of the libby config section injestion I submitted earlier. with this we could load all of our daemon parameters from the config file in the libby class and also handle sections for things like named_pos or limits. this assumes a json or yaml file. this only builds on the idea that we are still doing one config file per group/subsystem and trying to avoid having a config for every daemon.
YAML FILE EXAMPLE:
atcfwheel-communication:
host: "192.168.29.100"
port: 10010
peer_id: atcfwheel
group_id: hsfei
bind: null
address_book: null
transport = "rabbitmq"
discovery_enabled = False
discovery_interval_s = 5.0
rabbitmq_url = "amqp://localhost"
daemon_desc = "ATC FWheel"
atcfwheel-named_pos:
clear: 1
nd2: 2
nd3: 3
nd4: 4
nd5: 5
nd6: 6