Support a second config.yml file for 'local' configuration
#93
Labels
area:device
Device specific work
scope:device
Agent feature for Gateways and PLCs
size:S - 2
Sizing estimation point
task
A piece of work that isn't necessarily tied to a specific Epic or Story.
Comments
knolleary
added
task
MarianRaphael
added
area:device
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently the device agent picks up its configuration from command-line params and
device.yml.There are some options the user may want to set in their
device.ymlthat do not come from the platform. This means the user has to merge changes in their device.yml file which could be error prone.This includes:
portintervalverbosemoduleCacheWith #92 we are adding a bunch more CLI params for the config UI.
The proposal here is to support a second config file -
config.ymlthat can be used to set any option not otherwise provided by the platform'sdevice.yml.When starting, the agent would load
config.yml(if it exists), then applydevice.yml(if it exists) over the top, and then apply any CLI param overrides.Epic/Story
No response
The text was updated successfully, but these errors were encountered: