Package processing

This document defines two file artifacts that are used to deploy Packages to a target OpenWhisk platform; these include:

  • Package Manifest file: Contains the Package definition along with any included Action, Trigger or Rule definitions that comprise the package. This file includes the schema of input and output data to each entity for validation purposes.

  • Deployment file (optional): Contains the values and bindings used configure a Package to a target OpenWhisk platform provider’s environment and supply input parameter values for Packages, Actions and Triggers. This can include Namespace bindings, security and policy information.

Notes

  • Deployment files are optional. Deployment can be fully accomplished with simply a Manifest File.

Conceptual Package creation and publishing

The following diagram illustrates how a developer would create OpenWhisk code artifacts and associate a Package Manifest file that describes them for deployment and reuse.

Manifest file creation

Conceptual tooling integration and deployment

The following diagram illustrates how Package manifests can be leveraged by developer tooling to integrate OpenWhisk Serverless functions.

Manifest file deployment