asf-tooling commented on issue #640:
URL:
https://github.com/apache/tooling-trusted-releases/issues/640#issuecomment-4410126666
<!-- gofannon-issue-triage-bot v2 -->
**Automated triage** — analyzed at `main@2da7807a`
**Type:** `discussion` • **Classification:** `no_action` •
**Confidence:** `medium`
**Application domain(s):** `web_api_infrastructure`, `shared_infrastructure`
### Summary
Issue #640 proposes creating a URL mapping/redirect endpoint that maps
uniform release artifact URL patterns to ASF's preferred URLs. It references a
Slack conversation for context and suggests running on a test domain like
`purl-test.apache.org` or `catalog-test.apache.org`. @dave2wave suggested
running this as an AWS Lambda function rather than within the main ATR
application. The issue lacks specifics on URL patterns, mapping logic, or
concrete requirements, making it more of an open-ended RFC at this stage.
### Where new code would go
- `atr/get/__init__.py or a new service entirely` — new file or new blueprint
If implemented within ATR, it would likely be a new blueprint with
redirect routes; however, @dave2wave's suggestion of AWS Lambda implies this
might belong in a separate repository/service
### Proposed approach
This issue is still in the discussion phase and lacks sufficient detail to
produce a concrete implementation. Key open questions include: what is the
canonical URL pattern (PURL format?), what do the target URLs look like, should
this live in the ATR codebase or as a separate lightweight service (Lambda),
and what is the full mapping logic. The Slack conversation referenced is not
accessible, making it impossible to understand the full context of the
'rewritten idea'. Given @dave2wave's suggestion of AWS Lambda and the mention
of a separate test domain, this might not belong in this repository at all.
### Open questions
- What is the canonical URL pattern that should be mapped (PURL, some other
scheme)?
- What are the target 'preferred URLs' that artifacts should redirect to?
- Should this live in the ATR application or as a separate service (AWS
Lambda as @dave2wave suggested)?
- What was discussed in the referenced Slack thread
(https://the-asf.slack.com/archives/C08AEU02GAD/p1770742327913019)?
- If separate from ATR, should this issue be moved to a different repository?
_The agent reviewed this issue and is not proposing patches in this run.
Review the existing-code citations and open questions above before deciding
next steps._
### Files examined
- `.asf.yaml`
- `.github/PULL_REQUEST_TEMPLATE.md`
- `.github/dependabot.yml`
- `.github/labeler.yml`
- `.github/linters/.markdown-lint.yml`
- `.github/workflows/allowlistchecker.yml`
- `.github/workflows/analyze.yml`
- `.github/workflows/build.yml`
---
*Draft from a triage agent. A human reviewer should validate before merging
any change. The agent did not run tests or verify diffs apply.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
