Create an artifact

Before you begin

To create an artifact, you must have the following assets available:

A payload file that contains the actual content of the update:
- A payload file can contain data, code, or instructions that are delivered or executed as part of a software package.
- Often, a payload file contains binary diffs, binary scripts, application binaries, system images, or configuration files.

As you create an artifact, a manifest is automatically created based on the configuration of the artifact.

A manifest provides metadata to complement the payload. It must contain the following data points:
- Manifest version
- Artifact name
- Artifact version
- Artifact description
- Artifact type
- Artifact handling actions such as pre-install, install, post-install, or rollback
- Matching device attributes, firmware, and OS platform
- A checksum (SHA256) or a signature corresponding to the artifact.

Create an artifact

Tip

You can save your progress when creating an artifact and return to it later. Selecting Save draft and close lists the artifact in the Draft artifacts tab on the Artifacts page.

Sign in to DigiCert® ONE as an Artifact Manager.
In DigiCert ONE, in the Manager menu (grid at top right), select Device Trust.
In the Device Trust Manager menu, select Software updates > Artifacts.
Select Create Artifact.
On the General information step:
1. Enter an Artifact name and, optionally, a description.
2. Choose whether the artifact will be available to all divisions or only to a specific division. The default is all divisions.
3. Enter an Artifact version.
4. Select an Artifact type.
5. If this artifact depends on another, choose the artifact's dependency.
6. Select Next.
On the Artifact definition step:
1. Upload the artifact payload zip file.
2. Under Artifact handling, you can configure how TrustEdge agent will manage the artifact on the device. You can specify handling instructions for various deployment phases, each with detailed configuration options:
  - Install: Define the file to be executed for the installation phase, specify the file type or path, select a sub-type, and include any optional arguments to customize the process.
  - Pre-install: Set the file that will run before the installation starts, choose the file type, determine the sub-type, and provide any required arguments to prepare the device or environment.
  - Post-install: Configure the file that executes after the installation completes, specify the file type and sub-type, and add any arguments needed for post-installation tasks, such as cleanup or verification.
  - Rollback: Specify the file to handle the rollback process in case of installation failure, select the file type, define the sub-type, and provide arguments to revert the device to its prior state.
3. Optionally, select Add attribute to specify Target device attributes as key/value pairs. These attributes ensure the update is deployed only to devices with matching attributes.
4. Select Create artifact. The newly created artifact displays in the Artifacts table.