Packaging

Packaging refers to the process of compiling, encrypting and signing workflow configurations into a single distributable file that the opscotch agent can load.

The packaging process involves the following items:

• resources: Workflow configurations can refer to external resource files which are included when packaging. They are referred to as "resources". Resources can be supplied from multiple resource directories.
• agent public key: The package files supplied to the agent are encrypted using public key encryption. The public key that matches the private key the agent is configured with is used to encrypt the package.
• opscotch license: all packaging activities require a valid opscotch license. See here for details on licensing

The above information is written into a json file:

{
    "license" : "license.txt",
    "agentPublicKey" : "configs/agent.public.key",
    "resourceDirs" : ["."]
}

And then the packager is run with the above file, the configuration file that you want to package, and the name of the packaged file output:

Linux/macOS

opscotch-packager package.json my.config my.packaged.config

Windows

opscotch-packager.exe package.json my.config my.packaged.config

The packaged output file can be referenced from the bootstrap remoteConfiguration property.