Google Git
Sign in
apache / openwhisk-runtime-go / refs/tags/actionloop@1.13.0-incubating
tagf82adb3b16a574e3e4d5056c699a30de59ab6d4c
taggerDavid Grove <groved@us.ibm.com>Wed Jul 03 11:19:32 2019 -0400
objectddd329946c1d061f256a274d6ccd23e527760e06 
incubating 1.13.0-incubating actionloop
commitddd329946c1d061f256a274d6ccd23e527760e06[log] [tgz]
authorMichele Sciabarra <30654959+sciabarracom@users.noreply.github.com>Sat Apr 06 11:46:52 2019 +0200
committerrodric rabbah <rodric@gmail.com>Sat Apr 06 05:46:52 2019 -0400
treedc950ed72da79a8c16b1c3bde48aec9fbfb5a5ae
parent31f0dd67885c17724718b16ba011baaed77dea16 [diff]
reverted to a pure Apache license (#79)
1 file changed
tree: dc950ed72da79a8c16b1c3bde48aec9fbfb5a5ae
  1. actionloop/
  2. common/
  3. docs/
  4. examples/
  5. golang1.11/
  6. gradle/
  7. main/
  8. openwhisk/
  9. tests/
  10. tools/
  11. .gitattributes
  12. .gitignore
  13. .travis.yml
  14. build.gradle
  15. CHANGES.md
  16. CONTRIBUTING.md
  17. CREDITS.txt
  18. DISCLAIMER.txt
  19. gradlew
  20. gradlew.bat
  21. LICENSE-testify.txt
  22. LICENSE.txt
  23. NOTICE.txt
  24. README.md
  25. settings.gradle
README.md

Apache OpenWhisk Runtimes for Go

Build Status License Join Slack

This repository containst both the OpenWhisk runtime for Golang Actions, as well as a runtime for Generic executables.

  • If you are in a hurry, check the examples
  • Writing Actions for the runtime in Golang
  • How to deploy your Golang sources
  • Precompiling Golang actions
  • How to use VSCode to write Golang actions
  • How to Build the runtime, with development notes

Actionloop runtime

Using the Go runtime for Generic executables

  • Writing Generic actions, in bash or as a generic linux binary
  • Deployment for Generic actions
  • The ActionLoop protocol for generic actions

Change Log

CHANGES.md

License

Apache 2.0

Disclaimer

Apache OpenWhisk Runtime Go is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.