mirror of
https://github.com/fnproject/fn.git
synced 2022-10-28 21:29:17 +03:00
c3537399f1
/fns/{fnID}/calls
/fns/{fnID}/calls/{callID}
The S3 implementation forces our hand as we if we want to list Calls
under a Fn, we have to use the FnID as a prefix on the object names,
which mean we need it to look up any Call. It also makes sense in
terms of resource hierarchy.
These endpoints can optionally be disabled (as other endpoints), if a
service provider needs to provide this functionality via other means.
The 'calls' test has been fully migrated to fn calls. This has been
done to reduce the copy pasta a bit, and on balance is ok as the
routes calls will be removed soon.
Fn Documentation
For Developers
If you are a developer using Fn through the API, this section is for you.
Getting Started
- Quickstart
- Function file (func.yaml)
- FDKs
- Config Vars for Functions
- Hot functions
- Testing functions
- Applications - groups of functions
- Async functions
- FAQ
Examples and Tutorials
Advanced
For Operators
If you are operating Fn, this section is for you.
Getting Started
- Running in Production
- Logging
- Message Queues
- Metrics
- Operating on Windows
- Runtime Options
- User Interface
- Private Registries
Advanced
- Extending Fn
- Kubernetes Helm Chart for Fn
- Setting up development environment with Docker compose
- Docker Configuration
For Contributors
If you are working on the Fn Project, want to work on it or are creating extensions, this section is for you.