feat: Host openbao-fetch and document full-URL consumption #5
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
priority/P3
size/L
size/M
size/S
size/XL
size/XS
state/done
state/in-progress
state/in-review
state/needs-refinement
state/ready
type/bug
type/chore
type/feature
type/refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
amtronics/platform-actions!5
Loading…
Reference in a new issue
No description provided.
Delete branch "feat-openbao-fetch"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
Closes #4
Problem
Launchpad's pipeline proved cross-repo actions broken twice over: bare references resolve against data.forgejo.org, and the runner clones actions anonymously, so openbao-fetch living in the private infrastructure repository can never be consumed by another repo.
Solution
openbao-fetch moves here unchanged (the move infrastructure-vps #111 anticipated), and the README documents the two consumption rules — full URL, pinned tag — with input tables for both actions. After merge, v2 tags the first release covering both.
Review notes
The action file is a byte-for-byte copy of infrastructure-vps/.forgejo/actions/openbao-fetch/action.yml. Retiring that copy is left to a follow-up issue in that repo. This repository being public is what makes anonymous clones work; it holds no secrets by design.
Risks and trade-offs
Two copies of openbao-fetch exist until the infrastructure-vps one is retired.