To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.
- name: kioskwerks-provisioning
- description: a simple field provisioning service for our kiosks. The snap will accept a specifically named .tgz bundle (either default, or targeted to a machine MAC address) containing a .yaml file and a .minisign proving it came from our headend application. the only two things it changes are hostname and networking setup.
- snapcraft: (snap is unlisted, and intended to remain so)
- upstream: PRIVATE
- upstream-relation: this snap is developed by the Kioskwerks internal development team.
- interfaces:
- network-manager:
- request-type: auto-connection
- reasoning: this service is critical for configuring wifi networking on kiosks without wired connections available. We will often have sites where getting a kiosk machine to a wired network is a significant time or effort. We need a way for field techs to configure wifi-only kiosks. We would use console-conf, but we assert two system users for remote support tasks, which disables the use of console-conf.
- network-manager:
We feel the signature requirement and unlisted status makes the allowance of network-manager pretty trivial. I had these same functions built into a larger multi-purpose snap, but decided that snap (with about 4 or 5 ‘privileged’ connections) was not likely to find approval, so this one is narrowly focused. This really solves the chicken-and-egg problem for our platform where we will need to connect to each device once to connect the privileged connections on that other management snap.
Again, this is in-house software which we do not intend for anyone to deploy but us. Indeed, without a valid secret key, it is just a useless pile of bits.