What purpose does each of the Greengrass V2 config files have?
1
Hi,
I see there are multiple files under the /greengrass/v2/config folder on my GG Core device (see screenshot below), please can someone confirm what the purpose of each of these is?
1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
2
Hello,
Files ending with ~ are backup files which show the last state of the file before the current state. These are sometimes used if the primary file is detected to be corrupted in order to attempt an automatic recovery.
- bootstrap.tlog - initial configuration which should only be written one time and will contain minimal information, just enough to try and connect to AWS IoT Core in case the primary configuration file (config.tlog) is misisng or corrupted.
- config.tlog - the primary configuration file, the source of truth for everything Greengrass does on the device
- config.yaml - Greengrass did not create this file, you must have put it there during the install, perhaps following the 'manual provisioning' steps.
- effectiveConfig.yaml - A human-readable dump of the config.tlog file which is written by Greengrass on startup and shutdown; it will not show the current config state.
Cheers,
Michael
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 10 Monaten
Thanks Michael, this is super helpful and you're correct to say config.yaml is one we created as part of manual provisioning yes (I should have made this clear so apologies for that).
A couple of quick follow up questions if that's ok?
So it's actually config.tlog that the Nucleus actually reads from to acquire it's settings when starting up yes?
If effectiveConfig.yaml is just a human-readable dump of config.tlog (and not actually read/used by GG itself) why would you need a backup version?