Skip to main content

SDKMS Plugin Registry Builder

This tool builds a SDKMS plugin registry manifest file out of a git repository. It iterates through each commit and signs it. At each step of the iteration the tool keeps building the manifest which is a JSON structure with the following schema:

[
    {
        "name": "<Plugin Name>",
        "versions": {
            "<version>": {
                "path": <path/to/plugin/file>,
                "description": <plugin description>,
                "short_description": <short description used by SDKMS for display in tiles>,
                "release_notes": [
                    <str>,
                    ...
                ],
                "commit": <hexsha>
            },
            ...
        }
    },
    ...
]

Fortanix Plugin Registry

SDKMS Plugin Registries are GIT repositories that contains SDKMS plugins (custom Lua programs) that can be executed inside SDKMS to achieve certain business specific logic, or a functionality that is not part of the core capabilities offered by SDKMS. The repository should follow the following conventions:

  1. Each plugin should have a unique name.
  2. There should be just one plugin in each subdirectory.
  3. In each subdirectory the following files are required (case-sensitive):
    • plugin.lua: Contains the plugin code.
    • README.md: Contains a description of the plugin.
    • metadata.json: Contains metadata of the plugin. The schema of the JSON should be:
{
    "name": <Plugin name>,
    "version": <Plugin version>,
    "short_description": <Short description of what the plugin does. This text will be displayed in the plugin tile in the UI>,
    "release_notes": [
        <Array of release notes>
    ]
}

NOTE: older plugins have a single plugin.lua file with metadata stored in the first few lines of the file as comments. If a plugin follows that convention correctly then the README.md and metadata.json files are ignored and not required. In such cases the plugin metadata is extracted from the lua file. Here is an example of this convention:

-- Name: Test Plugin
-- Version: 1.0
-- Description: Hello, world!
--
-- This is a test.
-- End of description.

function run(input)
   return "Hello, world!"
end

Instructions

Before running this tool it is necessary that the git repository to be built is setup with the configuration so that its commits can be signed. Once the repository is setup run:

sdkms-plugin-registry-builder --repo-dir <Path/to/git/repository>

Metadata

Release files for sdkms-plugin-registry-builder 1.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sdkms-plugin-registry-builder 1.3.0
File Size Uploaded Provenance
sdkms_plugin_registry_builder-1.3.0.tar.gz 5.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for sdkms-plugin-registry-builder 1.3.0
File Interpreter ABI Platform
sdkms_plugin_registry_builder-1.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 11.9 kB

Release files / sdkms_plugin_registry_builder-1.3.0.tar.gz

Download URL sdkms_plugin_registry_builder-1.3.0.tar.gz
Size 5.6 kB
Tags Source
SHA-256 checksum
How to use checksums
d30041ccd2abeb16bcd8ff2f38e8069bbe722af48122426583d9e3b2f6f0398c
BLAKE2b-256 checksum
How to use checksums
b8e2e59cd62bb4129c51042c929ef6605cf869d9fbd335d91f155b3027c9061c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.0.1 CPython/3.8.10

Release files / sdkms_plugin_registry_builder-1.3.0-py3-none-any.whl

Download URL sdkms_plugin_registry_builder-1.3.0-py3-none-any.whl
Size 6.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e7474eb7c4394fc2dee5b4fc08866a7433068dd1fc4b1101e4d69dddf8d4e87f
BLAKE2b-256 checksum
How to use checksums
550b45bd54485cfd06bee3a36985cf4348c3b8df8b06d74e1278786f11c28daa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.0.1 CPython/3.8.10

Security for sdkms-plugin-registry-builder 1.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page