snapcraft.yaml

name: jhack

# our upper bound is juju's base, which at the time of writing is core24
base: core24

adopt-info: jhack
summary: Cli tool packed with juju hacks.

description: |
  An opinionated collection of scripts and utilities to make
  charming charming again. Many of the scripts in jhack interact with the juju snap and
  communicate with its client by issuing `juju` cli calls.
  This snap requires write access to ~/.local/share/juju via an interface named
  dot-local-share-juju, so that the juju client configuration can be used to talk to the
  user's clouds, controllers and models. Also, on machine models, you will need to connect the 
  `ssh-keys` plug so that jhack can run `juju ssh` on your behalf. 

grade: stable
confinement: strict

parts:
  jhack:
    plugin: python
    source: .
    override-build: |      
      snapcraftctl build
      VERSION="$(grep -Po 'version = "\K[^"]*' ./pyproject.toml)"
      snapcraftctl set-version $VERSION
    stage-snaps:
      - juju/3.3/beta

apps:
  jhack:
    command: bin/jhack
    plugs:
      - network
      - network-bind

      # do we need to add the custom plugs here as well?
      - dot-local-share-juju
      - dot-config-jhack
      - shared-memory
      - home-read
      - ssh-read

plugs:
  # read-write access to .local/share/juju (JUJU_DATA)
  dot-local-share-juju:
    interface: personal-files
    write:
      - $HOME/.local/share/juju

  # read-write access to jhack configuration file
  dot-config-jhack:
    interface: personal-files
    write:
      - $HOME/.config/jhack

  # required to use multiprocessing semaphores
  shared-memory:
    private: true

  # read access to $HOME. Required for sync and other commands that manipulate
  #  your local code projects.
  home-read:
    interface: home

  # access ssh keys to make them available to the embedded juju snap
  ssh-read:
    interface: ssh-keys