Skip to content

Conversation

@etrapnell-nist
Copy link
Collaborator

Adds to the image building functionality introduced for issue #594 (PR #954). On tag push, this workflow will compare the pushed tag against the pyproject.toml version. If they match, the package will be built and published to PyPI and then it kicks off the image building workflow. The image building workflow now has added functionality to pull from PyPI, but is currently disabled per our discussions and can be removed entirely.

Right now this is configured to publish to the Test PyPI instance. Switching to real PyPI needs the following:

  • Create a PyPI account
  • Create a PyPI token and put it in GitHub secrets manager (PYPI_API_TOKEN)
  • Toggle the PYPI_MODE flag in release.yml to use real PyPI

etrapnell-nist and others added 20 commits September 4, 2025 11:24
This commit refactors the docker-images GitHub Actions workflow by encapsulating behavior into 3
modules:

- install-rekor-cli
- sign-payload-fips
- create-rekor-entry

The docker-images workflow has been updated to use these new github actions modules and the old code
is commented out as a reference. It should be be removed once the workflow's validity is confirmed.
This is a temporary measure to reduce the amount of redundant and unnecessary compute activity and
get more rapid feedback on whether the approach is working. It should be reverted before merge.
This commit adds a new Logs tab to the Job Dashboard. It displays all logging messages sent to the
REST API in a table. It includes a polling feature that will update the logs automatically for
active Jobs.
This feature updates the Create Job form to allow the user to specify artifact params.

When an entrypoint with artifact parameters is selected, the Artifact Params table is populated with
the required artifact parameters the user must specify. The user can select valid artifacts (those
whose artifact task's output type matches the type of the artifact parameter) from a dropdown. By
default, the latest snapshot of the artifact is used. However, the user can choose to expand the
history and select a specific snapshot instead.

The filtering to display only valid artifacts is currently being done by the frontend. In the
future, this will be performed by the backend via a new query.
This commit catches duplicate names of resources and parameters in a resource import TOML file.
It raises a 400 BAD REQUEST error with the object names listed for the user to correct. This is
distinct from the 400 CONFLICT error that can arise when there is a name conflict with an existing
resource in the database.

This commit also adds a new test for this category of error.
@etrapnell-nist
Copy link
Collaborator Author

The release process now uses trusted publishers; API tokens are no longer required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants