Privileged interfaces auto-connection request: Jara

store-requests privileged-interfaces
1

Hi team,

I’d like to request auto-connection for Jara’s two personal-files plugs so users don’t have to manually connect them after installation. jara is a terminal UI for observing and interacting with Juju clusters (think k9s, but for Juju).

Interfaces

juju-client-observe (personal-files)

  • request-type: auto-connection
  • read: $HOME/.local/share/juju, $HOME/.config/juju
  • write: $HOME/.local/share/juju
  • reasoning: Jara reads Juju client credentials and controller configuration from $HOME/.local/share/juju and $HOME/.config/juju to discover and authenticate to controllers. Without read access the snap cannot connect to any Juju controller, making it non-functional. Write access to $HOME/.local/share/juju is needed to keep jara’s navigation in sync with the juju CLI:
    • Navigating between controllers persists the current-controller selection to controllers.yaml
    • Opening a model persists the current-model selection to models.yaml
    • The Juju client library updates the controller endpoint cache in controllers.yaml on every new API connection
    • Macaroon-based authentication writes session cookies to cookies/<controller>.json Jara works without write access (--readonly mode skips store writes), but normal usage expects it.

jara-config (personal-files)

  • request-type: auto-connection
  • read: $HOME/.jara
  • write: $HOME/.jara
  • reasoning: Jara stores its configuration, colour themes, and skin files under $HOME/.jara. Without this plug the snap falls back to compiled defaults and the user cannot persist any configuration (theme, key bindings, AI provider settings, refresh rate, etc.). Read and write access are both needed because jara both loads and saves configuration to this directory.
2

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

3

Hey @bschimke , thank you for the request. It make sense for auto-connection of these personal-files interfaces to jara snap

  • jara-config makes sense since it is jara’s own config
  • `juju-client-observe also makes sense given the functionality of the snap

Since jara is a canonical published snap, vetting is not needed. +1 from my end for the request (#voteFor)

4

Hello @bschimke!

I agree with the above that this personal-files auto-connection request makes sense and the jara snap has clear expected access to all listed paths given its functionality. This is a +1 (#voteFor) from me.

Before we grant this request, for transparency, we ask that personal-files interface plugs follow a specific naming convention. Can you please update the snapcraft.yaml to include the three personal-file plugs as follows? Thank you!

plugs:
  dot-jara:
    interface: personal-files
    write:
    - $HOME/.jara
  dot-local-share-juju:
    interface: personal-files
    write:
    - $HOME/.local/share/juju
  dot-config-juju:
    interface: personal-files
    read:
    - $HOME/.config/juju
5

Voting period has ended. This request is approved with 2 votes for and 0 votes against.

6

Thanks @elisehdy and @0xnishit

Naming updated as requested:

7

Thank you @bschimke!

+2 votes for, 0 votes against, granting auto-connect of interface personal-files to snap jara for the approved file paths. This is now live.