Michael Dombrowski

So Greengrass is still used to deploy code onto the device? If that's the case then the root directory must be writable, otherwise how can we download your updated code?...

I understand what V1 does, however these are quite different systems. I'm saying that you can already achieve the same thing by treating the Greengrass root as the "writeDirectory" from...

So the only difference is that you need to configure the `alts/current` directory as a symlink into the RO file system, that should be all that needs to be done....

Greengrass only writes to the root (except for /tmp which is used by the AWS IoT Device SDK). When using `--provision` we will create users and groups automatically, which is...

If you provide the user as a command line or config argument then we won't try to do anything.

There is a configuration under the nucleus service in the config file. Have a look for "logging" under https://docs.aws.amazon.com/greengrass/v2/developerguide/greengrass-nucleus-component.html#greengrass-nucleus-component-configuration

Editing effective config doesn't do anything, however in your yocto setup I believe that it uses an initial config file, so you can edit that file.

Edit this file: https://github.com/aws/meta-aws/blob/master/recipes-iot/aws-iot-greengrass/files/greengrassv2-init.yaml

No, it is not. Greengrass will read from config.tlog. If config.tlog does not exist it will read from config.yaml file which has the same format as the linked file.

Hi Kris, This feature is definitely on our roadmap. I don't have an ETA for you right now, but we're certainly aware of the case and we'll work to address...