You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
It's quite common to block external access, and whitelist Alpine packages, inside Kubernetes/OpenShift environments which causes a problem to run online installation scripts or retrieve Summon directly from within applications in the platforms, or even inside Dockerfiles.
Hi @Jishin85. Thank you for creating the issue. I'm in agreement, an alpine package would be very useful.
We're shifting our release build automation from our own scripts to using Goreleaser. In order for us to support the alpine package I believe it should only require configuring nfpm in Goreleaser.
I think we can move things along so that the shift to using Goreleaser is complete in the coming week. Most of the configuration is in place, it just needs to be connected to the build pipeline. From then we can configure nfpm and we should be able to get the build generating the alpine package.
Please note that the project is open to contribution so feel free to get things started.
Is your feature request related to a problem? Please describe
It's quite common to block external access, and whitelist Alpine packages, inside Kubernetes/OpenShift environments which causes a problem to run online installation scripts or retrieve Summon directly from within applications in the platforms, or even inside Dockerfiles.
Describe the solution you would like
Summon as an Alpine package would solve this problem, as a simple apt-get install summon would simplify its retrieval and installation.
https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package
Describe alternatives you have considered
Providing an Alpine image with Summon pre-installed, which is not as efficient.
The text was updated successfully, but these errors were encountered: