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

Provide license information for each package on API endpoints #1728

Open
3 tasks
fridex opened this issue Mar 25, 2022 · 6 comments
Open
3 tasks

Provide license information for each package on API endpoints #1728

fridex opened this issue Mar 25, 2022 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fridex
Copy link
Contributor

fridex commented Mar 25, 2022

Is your feature request related to a problem? Please describe.

As a user of Thoth services, I would like to consume information about licensing from user API endpoints.

Describe the solution you'd like

  • the license information should be reported based on the thoth-license-solver run report
  • extend thoth-storages to provide a method that queries the database for license information
  • provide an API endpoint that will return license information for the given (package name, package version, index url) triplet
@fridex fridex added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 25, 2022
@fridex
Copy link
Contributor Author

fridex commented Mar 25, 2022

/priority important-soon

CC @meile18

@codificat
Copy link
Member

/priority important-soon
(apparently a webhook was missed there)

/triage accepted

@sesheta sesheta added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Mar 30, 2022
@sesheta
Copy link
Member

sesheta commented Jun 28, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 28, 2022
@sesheta
Copy link
Member

sesheta commented Jul 28, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 28, 2022
@sesheta
Copy link
Member

sesheta commented Aug 27, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta
Copy link
Member

sesheta commented Aug 27, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta sesheta closed this as completed Aug 27, 2022
@mayaCostantini mayaCostantini added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Aug 27, 2022
@goern goern added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 🆕 New
Development

No branches or pull requests

5 participants