Open smoser opened 4 months ago
Some discussion in slack pointed at https://github.com/wolfi-dev/os/blob/main/java-common.yaml and https://github.com/wolfi-dev/os/blob/3e3471639307ac214e23b90f7839a859ae4e118c/keda-2.14.yaml#L70-L81 as examples.
java-common provides symlinks into /usr/bin for a bunch of things. keda-compat puts symlinks into / pointing at /usr/bin/keda. There are multiple things (fips) that implement keda, so you can re-use the keda-compat package.
I think there is still value here and we should allow metadata to override that. some allow-dangling-symlinks: keda, foo, bar
When a package is installed it should not have any dangling symlinks. Any dangling symlinks represent either pure broken package or missing dependency.
I saw such a thing today with google-cloud-sdk.