Skip to content

Allow secureboot secret material (shim-sign, code-sign and config-sign) to come from env #542

@mikn

Description

@mikn

The AWS profile is very neat, but currently we do not have a hardware token that we can reliably store these artefacts on in CI. We would like to (for now) feed these through env. Would you be willing to accept this patch upstream? (despite my horrible linting track record)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions