Thoughts on container-based action?

[kdkasad]

I recently started using GitOps for my Tailscale policy file, and found this gitops-acl-action to be quite slow. Every time it's run, it downloads Go, then downloads and compiles the CLI tool, and finally runs it. It looks like only the Go installation is cached, not the compilation of the tool, so it takes around 1 minute in my experience for the action to run.

As an experiment, I created https://github.com/kdkasad/tailscale-acl-action, which is exactly the same as this action in functionality, except it uses a pre-built Docker container. Execution of my container-based action takes around 1 to 5 seconds, a huge improvement. Unfortunately I cannot link to the workflow runs which show these results as that repository is private.

What are the team's thoughts on switching this action to use a container for more efficient execution?

[Radiergummi]

Yes, please. We're paying for build minutes. Compiling on every single change is nuts.

[Radiergummi]

@willnorris @raggi @DentonGentry could anyone from the Tailscale team comment on here maybe? If you don't have the bandwidth to take care of it, at least archive the repository and let the community take over. Just silently ignoring open PRs and issues is doing everyone a disservice.

[evilhamsterman]

Cache is even explicitly disabled

gitops-acl-action/action.yml

Line 41 in 0a59ccf

cache: false

If it were at least enabled then compilation would be really quick

[rojomisin]

sent a support request and included this issue