Introduction
Binary artifacts are binary files that patch envelopes can reference. You upload or link a binary file once, then reference it from multiple patch envelopes without re-uploading. Binary artifacts can be stored in up to three data stores simultaneously for redundancy.Prerequisites
- You have the SysManager or SysAdmin role in your enterprise. See Manage Roles.
- At least one data store configured in Edge Infrastructure Services.
Access Binary Artifacts
In the sidebar, navigate to Infrastructure > Workloads > Build > Binary Artifacts.Binary Artifact Statuses
Each binary artifact has an image status that reflects the state of the underlying file.The Binary Artifacts List
The binary artifact list shows the following columns by default. Use the column customizer to show or hide individual columns.
You can search by name or title, filter by image status, and toggle between list and grid views.
Binary Artifact Detail
Click any row in the list to open the detail page. The detail page shows two information sections.Identity
Details
Create a Binary Artifact
Binary artifacts store binary files that patch envelopes can reference. Create a binary artifact when you have a binary payload to deliver that is too large to embed as inline base64 data. You can add a binary file in two ways: by uploading it directly from your computer, or by uplinking it from an external data store.- In the sidebar, navigate to Infrastructure > Workloads > Build > Binary Artifacts.
- Click the add button (the + icon in the lower-right corner of the page).
- In the Add Binary Artifact dialog, fill in the identity fields:
- Name: enter a unique identifier. This field is required.
- Title: enter a human-readable display name.
- Description: enter an optional description.
- Under Add Artifact Via, select how you want to provide the binary file:
- Upload Artifact: an artifact path field and an Upload button appear. Click Upload and select the file from your computer. The file transfers when you click Add Binary Artifact.
- Uplink Artifact: enter the Image SHA256 checksum and the Image Size (select the unit from the dropdown). After you select a data store, an Image Relative URL field appears. Enter the path to the file within the data store.
- Under Data Store, search for and select the data store where the file should be stored. You can select up to three data stores. Upload mode supports only ZEDEDA S3 and ZEDEDA Azure Blob data stores. Uplink mode supports additional data store types including HTTP, HTTPS, Amazon S3, SFTP, and Azure Blob.
- Optionally, under Projects, select one or more projects to restrict access to this artifact. Leave the selection empty to make the artifact available to all projects.
- Click Add Binary Artifact.
Edit a Binary Artifact
To update a binary artifact’s title, description, data store assignments, or project access:- In the binary artifacts list, hover over the row and click the action menu (⋯), then select Edit. Or open the detail page and click the edit icon in the page header.
- Update the Title or Description as needed.
- Update the Data Store selection. You can select up to three data stores.
- Update the Projects list to restrict or expand access to specific projects. Removing all projects makes the artifact available to all projects.
- Click Save.
Delete a Binary Artifact
Delete from the list:- Navigate to Infrastructure > Workloads > Build > Binary Artifacts.
- Open the kebab menu on the row of the artifact you want to delete and select Delete.
- Confirm the deletion in the dialog that appears. This action cannot be undone.
- Open the detail page for the artifact you want to delete.
- Click the delete icon in the page header.
- Confirm the deletion in the dialog that appears. This action cannot be undone.
Next Steps
Update Applications with Runtime Bundles
The full workflow of attaching a patch envelope to an application instance.
Patch Envelopes
Learn about grouping binary artifacts into versioned bundles for delivery to application instances.