Prefix userid's with snap_ when used in a snap. #6671
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 change is to unblock potential development of a snap package for IoT Edge. A pre-requisite is to detect when running in snap confinement (e.g. looking at env vars injected by snapd) and then expect the OS userid's to be prefixed with
snap_
Tested by installing a build of IoT Edge, creating the snap_* users, reassigning ownership of the various files/directories to the snap_ users, copying over the built 'iotedge' binary with this change, and using it to perform actions such as:
sudo SNAP=1 ./iotedge config mp -c ...
sudo SNAP=1 ./iotedge config apply
And then I manually inspected the generated config files and the user ID's registered. For example, here's the output from one: