Specify a local file on disk for the function store
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 816
- Forks
- 230
- Avg merge
- 6h 4m
- Merged PRs (30d)
- 1
Description
Expected Behaviour
I'd like to be able to specify a local file on disk for the function store to test out definitions before publishing them on GitHub.
Current Behaviour
I can test any HTTP url via --url, but not a local file via a flag.
Why do you need this?
Better testing experience and contributing experience.
Which Solution Do You Recommend?
A new flag perhaps, or a url like file://. I think a flag fits better with the intuitive developer experience of a UNIX CLI.
Steps to Reproduce (for bugs)
git clone https://github.com/openfaas/store-functions && cd store-functionsfaas-cli store deploy --file ./functions.json- See an error
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the faas-cli store deploy command and its existing --url handling. Determine how the command could accept the local ./functions.json path described in the issue, then verify that definitions from a local file can be tested before publishing them to GitHub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100