Classic confinement for anbox-tools snap

store-requests classic-confinement
1

Hey!

I would like to request classic confinement for the anbox-tools snap.

  • name: anbox-tools
  • description: The anbox-tools snap contains utilities specific for the Anbox team at Canonical producing the Anbox Cloud product. These tools interface with a numerous of other tools install on a system, setup remote development environments on different substrates (multipass, LXD, AWS, …). The tools use existing CLI tools of a user like the AWS CLI to achieve its tasks and interact with remote environments, also such requiring low level system access for profiling or tracing purposes.
  • snapcraft: repository is private, ping @morphis if you need access for review.
  • upstream: PRIVATE
  • upstream-relation: the publisher is anbox-bot@canonical.com which is the bot account for the Anbox team at Canonical. The repository is internal to Canonical.
  • supported-category: tools for local, non-root user driven configuration of/switching to development workspaces/environments
  • reasoning: Interfaces do not allow reuse of existing tooling (e.g. AWS CLI, Juju, k8s) the user already has installed on their system which is important to structure the development process and provide efficiency.

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

Please let me know if you need additional information.

Thanks!

2

This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.

3

@reviewers I incorrectly set the wrong category at post creation. Not sure if the bot will have a second look now that the category is correct. Otherwise can you put this manually into the queue? Thanks :slight_smile:

4

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