File Repositories

A file repository is Hegemony's shared file store - the place for firmware images, scripts, and other assets your flows need. It is backed by S3-compatible object storage (the bundled Versity S3 Gateway by default), supports folder hierarchies, and records a SHA-256 checksum for every file.

File repositories are not the same as a flow's own Files tab: flow files are small text attachments versioned with the flow, while repository files are shared binaries available to every flow - see building flows for the former.

Repository names follow the platform's object name rules: trimmed, not blank, at most 128 characters, no word longer than 64, and no control characters.

Browse and organize

Pick a repository from the File Repository selector (the default one is preselected) and navigate folders through the breadcrumb bar. Each file row shows its size, truncated SHA-256, source (upload or URL import), and creation time. Click a file to open its detail page with full checksums, content type, storage location, and any metadata attached to it.

Folder tools sit in the browser toolbar: create a folder, rename the current one, or delete it once it is empty.

Add files

• Upload - pick a local file, optionally attach JSON metadata such as {"platform": "iosxe", "version": "17.09.01"}.
• Import from URL - have the platform download the file from an HTTP(S) URL. You can override the filename and supply an expected SHA-256; the import fails if the downloaded content does not match.

New files land in the repository root - use the row's Move action to file them into a folder afterwards.

Managing files (upload, import, move, delete, folder operations) requires the admin role; browsing and downloading is open to all users.

Use repository files in flows

Step fields that take a repository file render a Browse File Repositories... button that opens the same browser as a picker. A typical example is a firmware upgrade step, where you either select a staged image from the repository or give a source URL - one or the other, not both.

History card

The detail page carries a History card listing the most recent audit log entries about this object: how long ago, what the action was, which fields changed, who did it, and a non-success outcome where there was one. A row opens the same entry dialog the audit log uses, and the card links into the log filtered to this object. It appears only for callers who may read the audit log, so an operator or org admin sees the page without it.

Repository configuration (Settings)

Each organization has its own repositories and its own default. One is provisioned automatically against the deployment's shared object store and is marked Managed - its connection settings come from the deployment environment (HEGEMONY_S3_*) and are re-applied on every startup, so they cannot be edited here.

Settings → File Repositories lists them with their kind, endpoint, bucket, and prefix. Every signed-in user can open the list and a repository's page; the Settings hub shows the tile to anyone who may list repositories. An admin can add repositories, edit the ones that are not managed, switch which one is the organization's default, and delete a repository once it holds no files; for anyone else those controls appear locked rather than failing.

Repositories published by the shared organization appear with a Shared badge. They are readable from every organization - the same firmware image can be staged once centrally - but read-only here: uploads, folder changes, and edits are refused.

A repository either uses the deployment's own object storage or points at storage of your own. In the second case you supply the endpoint plus two secret references for the access key and secret key - the values themselves are never stored, only the references, and they are resolved when the repository is used. Test Connection on the repository page probes the bucket and reports whether the failure was credentials, networking, or a missing bucket.

For the full picture - storage kinds, connection modes, how shared-org credentials resolve, and how repositories travel through Configuration Exchange - see File Repository Storage and Connections.