Skip to content

Add provisioned concurrency support to Fn CLI#716

Open
Jaytee-fn wants to merge 2 commits intomasterfrom
fncli-provisioned-concurrency
Open

Add provisioned concurrency support to Fn CLI#716
Jaytee-fn wants to merge 2 commits intomasterfrom
fncli-provisioned-concurrency

Conversation

@Jaytee-fn
Copy link
Copy Markdown
Contributor

@Jaytee-fn Jaytee-fn commented May 5, 2026

This PR adds provisioned concurrency support to Fn CLI
It introduces provisioned concurrency parsing, adds support in - fn init, fn create function, and fn update function, and applies provisioned concurrency through the deploy path when using an Oracle provider.

Output rendering in inspect/list will be handled in a separate follow-up PR.

The PR adds support for -
--provisioned-concurrency none
--provisioned-concurrency constant:

add parser/validation helpers for provisioned concurrency syntax
persist provisioned concurrency in func.yaml during fn init

support provisioned concurrency in:
fn init
fn create function
fn update function
fn deploy

apply provisioned concurrency to OCI Functions when using an Oracle provider
warn and ignore the flag for non-Oracle providers
adds targeted tests for parsing, YAML persistence, and provider behaviour

The PR also adds provisioned concurrency output support to Fn CLI so users can verify provisioned concurrency configuration directly from function output.

provisioned concurrency values are displayed in:

  • fn inspect function
  • fn list functions
    It add a structured provisionedConcurrency field to function inspect JSON output and add a compact PC column to function list table output

@Jaytee-fn Jaytee-fn force-pushed the fncli-provisioned-concurrency branch from e073dcf to 47865bf Compare May 6, 2026 11:51
@Jaytee-fn Jaytee-fn force-pushed the fncli-provisioned-concurrency branch from 47865bf to 336ba3b Compare May 7, 2026 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants