Skip to content

Modifies domain objects after workshop #114

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

ppkarwasz
Copy link
Contributor

This PR modifies the schema of the domain objects according to the structure discussed in the Koala Workshop

This PR modifies the schema of the domain objects according to the structure discussed in the Koala Workshop

Signed-off-by: Piotr P. Karwasz <[email protected]>
@ppkarwasz ppkarwasz requested review from oej and madpah as code owners April 17, 2025 08:25
Comment on lines +157 to +162
#
# TEA Component and related objects
#
component:
type: object
description: A TEA component
Copy link
Contributor Author

Choose a reason for hiding this comment

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

One of the possibilities discussed in the Workshop was to:

  • inline the direct properties of this component (except versions) into product.components.
  • have an API endpoint that returns a paginated list of component_version objects.

Comment on lines 184 to 186
component_version:
type: object
description: A specific version of a TEA leaf
Copy link
Contributor Author

Choose a reason for hiding this comment

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

A component_version describes a specific binary file that is distributed to consumers. Should we also have a checksum or that file?

Should we have an API endpoint to find the correct component_version based on its checksum?

@ppkarwasz ppkarwasz force-pushed the feat/domain-objects branch from 0fde141 to 1acf408 Compare April 17, 2025 13:17
@ppkarwasz
Copy link
Contributor Author

This PR is based on #117.

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.

1 participant