A developer’s fn deploy cannot find the municipal Functions application even though the app exists in OCI. Which Fn CLI configuration most directly explains targeting the wrong place?
Select an answer to reveal the explanation.
Short Explanation
The Oracle provider context is the address book: compartment, registry prefix, and Functions API URL. If that book is wrong or missing, deploy looks in the wrong neighborhood and cannot see your application.
Full Explanation
Unlike plain Fn Project, the OCI context sets provider: oracle, oracle.compartment-id, optional profile, the Functions API URL, and the OCIR registry prefix. Commands then create and list resources in that compartment and push images to that registry. A missing or wrong context is a common reason fn deploy cannot find the application. This is CLI targeting, not a tenancy-admin IAM redesign.