Skip to content

Conversation

@mbuechse
Copy link
Contributor

No description provided.

@mbuechse mbuechse self-assigned this Sep 16, 2025
@mbuechse mbuechse marked this pull request as draft September 16, 2025 10:11
@fzakfeld
Copy link
Contributor

@depressiveRobot we (ScaleUp) have implemented this and should be ready

@depressiveRobot
Copy link
Contributor

We have two further responses:

  • one can implement it by mid-February 2026
  • one is against mandatory as they see no customer demand for it

Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
@mbuechse mbuechse marked this pull request as ready for review December 3, 2025 10:30
Copy link
Contributor

@depressiveRobot depressiveRobot left a comment

Choose a reason for hiding this comment

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

I think the replaces metadata field to the old document needs to be added.

Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Copy link
Contributor

@depressiveRobot depressiveRobot left a comment

Choose a reason for hiding this comment

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

Thanks for adding the missing field. Looks good now.

Copy link
Member

@garloff garloff left a comment

Choose a reason for hiding this comment

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

Looks good to me, thanks!

Comment on lines +76 to +79
_Uniqueness requirement_: whenever there are two images that have `os_hidden=False`, `visibility=public`,
and that coincide in all three fields `os_distro`, `os_version`, and `architecture`, then only one of them may
have `os_purpose=generic`. In other words, users who search visible public images for a generic OS
of a certain distro, version, and architecture will not get more than one result.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note to self: check whether we have a testcase for that (I guess not)

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

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

5 participants