Client Environment Configuration Notes for OCI Functions
Find out more information and notes about how to configure your client environment for function development with OCI Functions.
Before you can start using OCI Functions to create and deploy functions, you have to set up your client environment for function development.
For image-based functions, use the Functions QuickStart Guides to get set up quickly.
Note that prior to setting up your client environment, you must already have set up your tenancy.
This section provides more information and notes about the tasks you perform using the Functions QuickStart Guides to configure your client development environment for OCI Functions. Some tasks apply to all workflows, and some apply only to image-based functions:
- Setting up an Oracle Cloud Infrastructure API Signing Key for Use with OCI Functions
- Creating a Profile in the Oracle Cloud Infrastructure CLI Configuration File
- Installing Docker for Use with OCI Functions (required for image-based functions)
- Installing the Fn Project CLI
- Creating an Fn Project CLI Context to Connect to Oracle Cloud Infrastructure
- Setting the Context for the Fn Project CLI Using the oracle.profile Parameter
- Generating an Auth Token to Enable Login to Oracle Cloud Infrastructure Registry (required for image-based functions)
- Starting Docker (required for image-based functions)
- Logging in to Oracle Cloud Infrastructure Registry (required for image-based functions)
Code-only functions are created from archives and use managed runtimes. You do not provide or manage a container image as part of the code-only function workflow. For code-only function requirements, see About Code-only Functions and Creating Code-only Functions.