Cos-tool binary permissions 775 in charmcraft.yaml and 755 in charm

[MichaelThamm]

Bug Description

In the charmcraft.yaml we:

    override-pull: |
      curl -L -O https://github.com/canonical/cos-tool/releases/latest/download/cos-tool-${CRAFT_ARCH_BUILD_FOR}
      chmod 775 cos-tool-*

Which should result in 775 permissions on the cos-tool binary, but when checking the permissions in the VM we get 755.

To Reproduce

Note: This occurs when packing the charm locally from main and latest/edge from charmhub.

default-base: [email protected]/stable
applications:
  gagent:
    charm: grafana-agent
    channel: latest/edge
    revision: 396
    trust: true
  zookeeper:
    charm: zookeeper
    channel: 3/stable
    revision: 149
    num_units: 1
    to:
    - "0"
    constraints: arch=amd64
    storage:
      data: rootfs,1,1024M
    trust: true
machines:
  "0":
    constraints: arch=amd64
relations:
- - zookeeper:cos-agent
  - gagent:cos-agent

Relevant log output

juju ssh gagent/0 "ls -la1 /var/lib/juju/agents/unit-gagent-0/charm/cos-tool-amd64"

• -rwxr-xr-x 1 root root 14864384 Jan 22 17:25 /var/lib/juju/agents/unit-gagent-0/charm/cos-tool-amd64

Which is 755 not 775!

[MichaelThamm]

Instead of running chmod on the binary after installing it we should add a permissions key in the charmcraft.yaml similar to how we do it in our rocks:

• https://github.com/canonical/opentelemetry-collector-rock/blob/07cdeb0c197824324fe3888b98c769f7010e7957/0.117.0/rockcraft.yaml#L38