Request for additional interfaces for enmac-collector

store-requests privileged-interfaces
1
  • name: enmac-collector
  • description: This snap is used in IIoT devices (Collector devices) to collect data from various automation processes / devices / sensors to Prevas Cloud (formerly Enmac Cloud) platform.
  • snapcraft: https://prevasonline-my.sharepoint.com/:u:/g/personal/juho_hanhimaki_prevas_fi/EUrCXdEHXEFFg480C6t09SMBEwTFKppPLwibfmsTp4ZyoQ?e=bZQbuv
  • upstream: PRIVATE
  • upstream-relation: owner
  • interfaces:
    • mntctl:
      • request-type: auto-connection
      • reasoning: Collector devices are provisioned to Prevas Cloud platform using configuration files transferred by USB flash drives. Without the configuration file the software cannot function. The configuration is used to define the device’s networking (Netplan), hostname and necessary Prevas Cloud connection details. The configuration file is signed by Prevas Cloud to prevent any outside tampering. As the collector devices are usually headless, the USB flash drive can also be used to gather diagnostics information to troubleshoot any connectivity issues. The mount-control interface is used facilitate mounting USB flash drives by label ‘COLLECTOR’. Thus, the snap will only be able to access a drive that has been labelled for that purpose.
    • hostname-control:
      • request-type: auto-connection
      • reasoning: Ability to configure device’s hostname is essential function of Collectors connected Prevas Cloud (see mntctl).
    • network-setup-control:
      • request-type: auto-connection
      • reasoning: Ability to configure device’s networking is essential function of Collectors connected Prevas Cloud (see mntctl).
2

This request has been added to the queue for review by the @reviewers team.

3

Given the purpose and functionality of the snap described above, +1 (#voteFor) auto-connecting network-setup-control, hostname-control and mount-control (pending publisher vetting)

4

+1 (#voteFor) from my side as well for auto-connecting network-setup-control, hostname-control and mount-control interfaces, given successful publisher vetting

5

Thanks for the votes.

For the vetting I’ve posted a request for verified publisher status here:

6

Hey @juho-hanhimaki, I will start publisher vetting process

7

Hey @juho-hanhimaki , for the publisher vetting this is the process:Process for performing Snap Publisher Vetting

Let me know if you have any upstream repository (public/private) for this snap (#askForInfo)

8

Thanks.

We have a private repository on Azuren DevOps.

9

Hey @juho-hanhimaki , publisher vetting process has been started, kindly check your DM and follow the process for the next step

thanks

10

Hey @juho-hanhimaki, since this is a private repo and there is no way to verify for us. The way forward is to get your account verified (follow the process: Verified Accounts ) and then we can proceed

thanks

11

Thanks for clarification.

Per the process, I have posted here for account verification: