openfaas / openfaas/openfaas.github.io

Giving Bash a REST with OpenFaaS

Open
#259 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
57
Forks
42
PR merge metrics
No merged PRs in 30d

Description

What would you like to let us know?

I'd like to see a blog post on writing functions with bash called: Giving Bash a REST with OpenFaaS

Context

Many DevOps/sysadmin users are comfortable with bash and CLI tools. Bash can make simple tasks and existing tools easy to use such as terraform and various cloud CLIs.

One of the challenges is visibility - showing people that this can be done.

The other is authentication - if you attach a cloud access token to a bash function, and anyone can provision a VM - that's a terrible idea. So how do you authenticate?

Thirdly, how do you take clean output from a bash function and filter that out so it can be used with another process or function?

The blog post should cover these topics and give examples using the openfaas bash template.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing blog-post structure in the OpenFaaS website and the openfaas bash template. Frame examples around visibility, authentication for cloud tokens, and filtering clean output; done means a blog post titled "Giving Bash a REST with OpenFaaS" covering all three topics with working examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.