Skip to content

allow adding additional tags to OCI index and manifests #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

yeoldegrove
Copy link
Contributor

@yeoldegrove yeoldegrove commented May 22, 2025

What this PR does / why we need it:

gardenlinux/gardenlinux#2754 outlines the restructure of OCI release tags.
To actually add additional tags to the OCI index and manifests, a new paramter --additional-tag has to be added to the gl-oci update-index|push-manifest calls.

Additionally this adds:

  • retry_on_error decoration for blob_upload (CI tests will fail else wise)
  • make targets make test-debug and make test-trace to debug OCI tagging
  • pythonic way to generate test data (as tests are extended quite a bit)

Special notes for your reviewer:

@yeoldegrove yeoldegrove changed the title restructure OCI release tags allow adding additional tags to OCI index and manifests May 22, 2025
@yeoldegrove yeoldegrove force-pushed the feat/oci_tagging branch 4 times, most recently from db91efb to 8bc6eea Compare May 22, 2025 08:57
@yeoldegrove yeoldegrove self-assigned this May 22, 2025
adds the possibility to get debug logs for pytest
e.g. debug which OCI tags exist
add create_test_data to conftest
remove generate_test_certificates from helper as it is on conftest already
enables pushing additional tags to OCI manifest
enables pushing additional tags to OCI index
for artifact in oci_metadata:
if artifact["media_type"] == "application/io.gardenlinux.release":
file = open(f"{directory}/{artifact["file_name"]}", "r")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use configparser.ConfigParser here as it will be compatible with the file content and makes the code more readable :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we name this file wrapper(s).py? Further refinement can be integrated into #110.

@yeoldegrove yeoldegrove added this to the 2025-05 milestone May 26, 2025
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.

2 participants