Autoconnect request for landscape-task-handler

When uploading v0.1.0, I received the following failure: “human review required due to ‘allow-installation’ constraint (bool) declaration-snap-v2_plugs_installation (etc-landscape, system-files)”.


  • name: landscape-task-handler

  • description: Snap is used to run the Landscape task handler service.

    Run `snap start landscape-task-handler.task-handler` to initiate the service.

  • snapcraft: PRIVATE

  • upstream: PRIVATE

  • upstream-relation: Contributor

  • interfaces:

    • system-files:
      • request-type: installation and auto-connection
      • reasoning: This snap needs to read from Landscape /etc/landscape/service.conf and other files in /etc/landscape/… to run properly. The requested interface is read-only and scoped to /etc/landscape. There is a precedent for this type of permission being allowed for Landscape snaps (e.g. landscape-outbox).

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

Hi @joey-mucci,

The request makes sense and +1 from me to grant read access to /etc/landspace using system-files. Similar to landscape-outbox snap, are there any plans to transfer the ownership of this snap under Canonical’s account?

Hi @shishirsub10

Yes, once the snap is stable we’d like to have it under Canonical ownership.

Hello!

This is a +1 from me as well for granting the landscape-task-handler snap the requested system-files interface auto-connection given the clear ownership and expected access. I also agree with @shishirsub10’s suggestion for ownership transfer when ready.