Skip to content

OpenFaaS build and push

Actions
Builds a docker image from your OpenFaaS function and pushes it to your registry
0.3.0
Latest
Star (12)

OpenFaaS Github action

License: MIT CI (build and test)

A no-frills Github action for building OpenFaaS functions.

The function gets the image information from the function file.

Limitations

No sophisticated optional parameters! The main pupose of this action is simplicity. Therefore, no other optional, non-functional parameters influencing the behaviour of faas-cli are going to be supported. If you really feel that you desperately need sommething, feel free to open an issue!

Inputs

Parameter effect default required
stack-file The OpenFaaS function definition file stack.yml yes
docker-username Your docker registry's username with push authorization yes
docker-password Your docker registry's password yes
platforms The platform abbreviations to build for, potentially comma-separated. e. g. linux/amd64,linux/arm/v7 linux/amd64 yes
deploy Whether the built image shall be deployed false no
openfaas-gateway OpenFaaS gateway URL overriding the one given. Only has an effect, if deploy=true no
openfaas-username User for authenticating at OpenFaaS gateway no
openfaas-password Password for authenticating at OpenFaaS gateway no

Outputs

Parameter purpose
tag The tag of the image built - it's the same across multiple images from the same function stack build

Further links

🏠 Homepage

Demo

Author

👤 Oliver Jägle

🤝 Contributing

Contributions, issues and feature requests are welcome!

Feel free to check issues page.

Show your support

Give a ⭐️ if this project helped you!


This README was generated with ❤️ by readme-md-generator

OpenFaaS build and push is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

About

Builds a docker image from your OpenFaaS function and pushes it to your registry
0.3.0
Latest

OpenFaaS build and push is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.