config: packages[*].binaries should accept full Go package paths #67
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
nagonag
nagonag/ignore
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
heiko/gogogo#67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
artifacts.packages[*].binariesin.gogogo.confaccepts only bare binary names(e.g.
cert-proxy-client), but users naturally mirror the path form used inbuild.commands(e.g.cmd/cert-proxy-client). The current behaviour produces aconfusing
doctorerror and silently drops binaries from packages at runtime.Fix: normalize
packages[*].binariesentries to basenames at YAML unmarshal time(
PackagesSpec.UnmarshalYAML), so both forms are accepted transparently.Also update
knownBinaryininternal/config/validation.goto usepath.Baseonboth sides, covering code paths that construct
config.Packagewithout going throughYAML (e.g. tests, future callers).
Related: the limitation that two
build.commandssharing a basename clobber eachother is tracked separately in #65.