Skip to content
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

Do not build/release/test/scan tracks with expired end-of-life values #241

Merged
merged 10 commits into from
Sep 30, 2024

Conversation

linostar
Copy link
Contributor

@linostar linostar commented Sep 6, 2024

Ping the @canonical/rocks team.


Description

We want to display deprecated image information in upstream container registries, but in order to that we have to allow deprecated image data to exist in our image.yaml files. The Pydantic validator currently throws an exception whenever an image track has an expired end-of-life value. This PR changes that behavior so that expired end-of-life values are allowed, but tracks with such values are not triggered for testing, building, releasing or vulnerability scanning.

Related issues


Picture of a cool rock:

@linostar linostar force-pushed the ROCKS-973/allow-expired-eol-values branch from 6114513 to 1bfff8a Compare September 6, 2024 14:47
@linostar linostar force-pushed the ROCKS-973/allow-expired-eol-values branch from 84edd22 to e0ea1d5 Compare September 9, 2024 10:09
@linostar linostar force-pushed the ROCKS-973/allow-expired-eol-values branch from c96ef39 to 909dbcb Compare September 9, 2024 12:05
@linostar linostar force-pushed the ROCKS-973/allow-expired-eol-values branch from 909dbcb to 26a4849 Compare September 9, 2024 12:10
@linostar linostar marked this pull request as ready for review September 9, 2024 13:24
@linostar linostar changed the title do not release tracks with expired end_of_life values Do not build/release/test/scan tracks with expired end_of_life values Sep 9, 2024
@linostar linostar changed the title Do not build/release/test/scan tracks with expired end_of_life values Do not build/release/test/scan tracks with expired end-of-life values Sep 9, 2024
@cjdcordeiro
Copy link
Collaborator

check the conflict pls

@linostar linostar requested a review from a team as a code owner September 17, 2024 05:59
@linostar
Copy link
Contributor Author

check the conflict pls

Fixed.

Copy link
Contributor

@zhijie-yang zhijie-yang left a comment

Choose a reason for hiding this comment

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

LTGM, thanks!

@cjdcordeiro cjdcordeiro self-assigned this Sep 30, 2024
@cjdcordeiro cjdcordeiro merged commit 32410b0 into main Sep 30, 2024
8 of 9 checks passed
@cjdcordeiro cjdcordeiro deleted the ROCKS-973/allow-expired-eol-values branch September 30, 2024 11:39
Copy link

One or more files in this PR are not valid! 😬
Run ID: 11105327838 ; Attempt: 1

See logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants