feat: Default openbao-fetch addr to bao.internal #104
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
priority/P3
size/L
size/M
size/S
size/XL
size/XS
state/blocked
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
amtronics/platform-actions!104
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/103-bao-internal-default"
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 #103
Problem
Every caller passes the vault IP as a required input, so moving OpenBao (amtronics/infrastructure-vps#548) edits 50 workflows in 17 repositories.
Solution
addris optional and defaults tohttps://bao.internal:8200, which both runners resolve on the host and in job containers (amtronics/infrastructure-vps#551). An explicitaddrstill overrides; an empty one fails with a clear message (new behaviour test). README, CONFIGURATION and the release template drop the literal.Review notes
No caller changes behaviour: all 50 pass
addrtoday. The pilot repo (suhba/rihla) drops it next.Risks and trade-offs
A runner without the
bao.internalmapping fails a caller that omitsaddr; both current runners have it.Verified at
32139d5(CI green: harness tests, behaviour tests, README lint):addrisrequired: falsewith defaulthttps://bao.internal:8200;OB_ADDRstill mapsinputs.addr, so a passed value wins (#103 AC1, AC2).addrbypasses the action default, and the new guard fails before any curl withaddr is empty; omit it to use the default; the behaviour test drives exactly that path (AC3).bao.internalon the host and in job containers (read back for amtronics/infrastructure-vps#551), so the default is reachable where this action runs.