Basic rock configuration for HashiCorp Consul

[jadonn]

OpenStack Masakari requires HashiCorp Consul. This change adds a rockcraft.yaml configuration for building a Consul rock from the consul-client snap I registered. The Consul rock is for running Consul in server mode in Kubernetes. The consult-client snap will provide Consul for running in client mode on compute hypervisor nodes.

[gboutry]

I think we can go on a much more simple rock for Consul, such as:

base: bare
build-base: ubuntu@24.04
platforms:
  amd64:

run-user: _daemon_

services:
  consul:
    override: replace
    command: bin/consul agent
    user: consul
    group: consul

parts:
  consul-user:
    plugin: nil
    override-prime: |
      craftctl default
      # Give permission and create the required directories
      mkdir -p $CRAFT_PRIME/etc || true
      echo "consul:x:5996:" >> $CRAFT_PRIME/etc/group
      echo "consul:x:5996:5996::/var/lib/consul:/usr/bin/false" >> $CRAFT_PRIME/etc/passwd
      folders=(var/lib/consul etc/consul.d)
      for folder in "${folders[@]}"; do
        mkdir -p $CRAFT_PRIME/$folder || true
        chown -R 5996:5996 $CRAFT_PRIME/$folder
      done

  snap-consul-client: # replace with consul snap once it is available
    after: [consul-user]
    stage-packages:
      # following are just for debug purposes
      - bash_bins
      - coreutils_bins
    plugin: nil
    stage-snaps:
      - consul-client/latest/edge
    organize:
      consul: bin/consul

Is there a reason why the consul-client snap is based on core22 instead of core24?

Can we make sure all config / data paths are present and with the right permission inside the Rock?

Ideally, this Rock should be able to have pebble run as _daemon_ (rootless) and the consul service as the consul user. But this might be pushing it for now.

[gboutry]

Closed in favor of #71

[gboutry]

Commits are not signed, can't merge