Deploy! 🎉

This release brings the ability to directly deploy your OpenFaaS action to your gateway.

A complete CI/CD pipeline for your function which triggers a deployment when merging into master looks minimal like that:

name: CI/CD

on:  [push]

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: OpenFaaS build and push
        uses: mrsimpson/action-openfaas-build@master
        with:
          # The OpenFaaS function definition file
          stack-file: stack.yml
          # Your docker username with push authorization
          docker-username: ${{ secrets.DOCKER_USERNAME }}
          # Your docker username with push authorization
          docker-password: ${{ secrets.DOCKER_PASSWORD }}
          # the platform abbreviations to build for, e. g. linux/amd64,linux/arm/v7
          platforms: linux/amd64,linux/arm/v7
          # Whether the built image shall be deployed (false=no, true=yes)
          deploy: ${{ github.ref == 'refs/heads/master' }}
          # OpenFaaS gateway URL (http(s)://my-public-gateway.tld)
          openfaas-gateway: ${{ secrets.OPENFAAS_GATEWAY }}
          # User for authenticating at OpenFaaS gateway
          openfaas-username: ${{ secrets.OPENFAAS_USERNAME }}
          # Password for authenticating at OpenFaaS gateway
          openfaas-password: ${{ secrets.OPENFAAS_PASSWORD }}

Has multi-arch CI/CD ever been easier?

Fail on errors

Fail on script failure (#9)

Fix Bash newbie errors

0.2.0: Multi image (#5)

* Support building of multiple Images in one function
* Automated testing

First usable version

Limitations

Building multi-function-stacks is currently not supported, see #4

0.1.0

Initial version