alexellis / actions-batch

Time-sharing supercomputer built on GitHub Actions

I create independent tools for developers

Hear a bit about my background and why I'm on this journey:

• Video: Hear my OpenFaaS story over 60 months from this Gophercon keynote
• Podcast: Independent Open Source, with Alex Ellis - Kubernetes Podcast by Google

Follow my journey and support my Open Source work

As a GitHub Sponsor, you'll hear from me every week by email - covering my journey building independent software and open source projects. I share about new features, updates, events, tutorials and often share what I've learned from reading and executing every day.

• ⭐️ Sponsor me on GitHub
• 🤓 Send me a book for inspiration from my Amazon wishlist

My books

I've been self-publishing books for a year.

Fast track your Go journey

My best-selling book!

• Learn unit testing and how to isolate dependencies
• Make lovely CLIs for internal tools and open source projects
• Monitor your services with Prometheus metrics
• Ship your code in a container with Docker
• Learn patterns and pitfalls for using Goroutines

Fast track your Go

📚 My first eBook - Serverless for Everyone Else

Learn the use-cases for serverless functions through practical exercises. You'll deploy your own self-hosted functions, write code in Node.js and using examples will start to call HTTP APIs, add npm modules and understand how to monitor your code with Grafana.

Get the eBook on its own, or upgrade to the video workshop for my expert overview.

• Learn how to apply functions for your own workflow

Need to contact me?

• 📫 Need to email me?
• 💬 Want to book a 1:1 with me?

actions-batch's Issues

Secrets for jobs

When a local .secrets folder is supplied, then these should be created as repo-level secrets accessible for the script.

For the example of using faas-cli remotely, and / or using a database connection string, or VPN etc.

https://docs.github.com/en/rest/actions/secrets#create-or-update-a-repository-secret

Feature request: Additional files

It would be great if there was a option to upload extra files along with the main script. Like for the Docker example, if I could modify the script to refer to an actual Dockerfile that also gets uploaded along side the job.sh. Maybe a flag like -additional-files []string ?

Add CI and releases

Add CI and releases using the pattern from alexellis/arkade

Collect/download output artifacts prior to repo deletion

Collect/download output artifacts prior to repo deletion

If files are created in a known folder, an action should be added to the template to upload them as artifacts/pipeline outputs.

The code that checks for logs should then check for artifacts and download them.

Use-case:

• take a screenshot of a certain webpage, the image is uploaded as an output, and is then downloaded
• youtubedl is executed and the result is then uploaded as an artifact and downloaded after
• you build an ISO image using QEMU/Packer or a Docker image as a tar, this is uploaded and downloaded to the local computer afterwards

Help wanted - more examples

Take a look at some of the examples:

https://github.com/alexellis/actions-batch/tree/master/examples

I'd like submissions for things that can run in the foreground or run until completion.

Some ideas: headless Chrome / puppeteer / Postgresql or similar queries via CLI, running e2e tests - perhaps the ones from the openfaas/faas-netes repo? Testing out a Helm chart by installing it via arkade? Running hey against your own HTTP server?

Include id_token: write in the job template for OIDC tokens

Include id_token: write in the job template for OIDC tokens

This is used for authentication for things like the actuated SSH gateway and for deploying to/interacting with AWS using a short-lived tokens

It could just be added as a default in the template, no need to make it optional.

Remember to also include contents: read