Application-level TEA redirects
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api
Research direction
No files or tests are named. Start by reviewing the productReleases endpoint and its existing productRelease and link-object responses; done means defining and documenting how redirects to external TEA servers are represented and handled.
Written by the indexing model from the issue text.
Description
In the meeting we discussed using the PURL repository_url qualifier to locate a TEA server. The downside: this assumes each package repository runs a TEA service for millions of packages, which is unlikely.
As an alternative we could allow allow TEA endpoints (especially productReleases) to include redirects to external TEA servers, for example by allowing special link objects in the response alongside normal productRelease objects.
This would let package repositories support TEA at minimal cost by simply redirecting requests to the TEA servers operated by individual package owners.
- Dominant language
- Shell
- Stars
- 120
- Forks
- 24
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 67
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CycloneDX/transparency-exchange-api
-
Shorten and simplify clause 5 discoveryPossibly taken @oej claimed this 11 days ago. OpenTEI Discovery
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CycloneDX/transparency-exchange-api#392 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Definition/explanation should come before usePossibly taken @oej claimed this 11 days ago. OpenTEI Discovery
Difficulty 1/5 Under an hour Newbie friendliness 90/100
CycloneDX/transparency-exchange-api#391 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Backlog
Difficulty 1/5 Under an hour Newbie friendliness 85/100
CycloneDX/transparency-exchange-api#343 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Fix normative reference to JSON schemaPossibly taken @gesa claimed this 2 days ago. OpenPrio 1 TEI Discovery
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
CycloneDX/transparency-exchange-api#404 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Prio 1 TEI Discovery
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
CycloneDX/transparency-exchange-api#390 · 1 comment ·
Maintainers usually reply within 1 day
All issues in CycloneDX/transparency-exchange-api
Similar issues
-
gdsa opencode: keep-alive cleanup trap fails with 'keepalive_pid: unbound variable'Possibly taken @darribas claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
icon request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100