* feat(http): serve list/show counts/dep tree/ping, close+reopen under a session, one-lookup not-found (S6b/S6c/S6d) S6c. The external-dependency decorator rebuilt its role views from the legacy DoltStorage seam (storereader over itself, IsBlocked, GetDependencyTree, ClaimReadyIssue), which a remote store only partly serves: `bd list`/`bd children` refused on the SearchIssuesWithCounts stub, `bd show --json` printed zero counts, the default `bd dep tree` refused, `bd ready --claim` and `bd close` of an externally blocked issue reached unsupported paths. For a storage.RemoteBackendStore each view now passes the inner role through and lays the policy over it in role terms (externaldeps/remote_roles.go): ready reads and the ready claim exclude the workspace-wide blocked set over a widened window; per-issue checks (claim, close, batch close, list annotations, tree leaves) read only the named issues' edges through EdgeReader instead of every edge in the workspace. A server advertising policy.external_dependencies (MC's does) gets a plain passthrough. `bd ping` uses a new storage.Pinger, which the http store answers with its authenticated context read. S6d. A store reporting storage.CallerAttributionLimitedStore (http) cannot carry a Provenance label or a patch's closed_by_session. The library still refuses both; the CLI omits them where nothing is lost: `bd reopen`'s fixed "bd: reopen <id>" label (the server labels the same entry), and the closed_by_session of `bd update -s closed` (attribution only, usually the ambient CLAUDE_SESSION_ID; an explicit --session prints a notice; `bd close` still records it). See cmd/bd/remote_backend.go. S6b. utils.ExactIDLookupStore: the resolver stops at exact lookups for a store with no substring search, so a missing prefixed id is a not-found (beadserrors.ErrNotFound, "no issue found matching") after one getIssue. The general resolver no longer repeats an identical normalized probe. The http SearchIssueIDs answers D11's partial-id refusal, which now unwraps to ErrNotFound. Contributor auto-routing for a remote workspace reads local config only, so the not-found fallback pays no settings round trip. `bd update <absent> --claim` (gc's hook claim) answers a gc-classifiable not-found in at most two requests. Served e2e (backend/http/e2e_remote_roles_test.go): every gc list shape and `bd children` against embedded, `show --json` count parity, default dep tree parity, external blocking still enforced, close/reopen under CLAUDE_SESSION_ID, missing-id request counts, absent-id claim against the current server and the MC handshake mask, policy passthrough under the MC mask, ping. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(externaldeps): role-level remote reader and claimer cases bd ready and bd update --claim reach the policy through the legacy seam and the lifecycle guard, so the remote Reader.Ready exclusion and the remote Claimer guard (what bd serve and library callers reach) are pinned at the role level with a fake remote store. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(http): bd serve advertises policy.external_dependencies; clients pass through bd serve composes every ready, claim, claim-next, close, blocking and tree role through the external-dependency policy, but never said so. Every client therefore ran the policy a second time, with the CLIENT machine's external-project config, and claim-next became a non-atomic read-then-claim loop on the client. The server now advertises the token exactly when the roles it serves were composed through the policy: httpapi.Config.ExternalDependencyPolicy, which bd serve derives from its actual chain (externaldeps.Applied for the store arm, externaldeps.AppliedToProvider for the provider arm). A server handed raw roles still withholds it, so the token stays truthful. Against a server that advertises it, every remote role view hands the request to the server's own role untouched: no client validation, no edge reads, claim-next is the server's one atomic call, and the ready count is the server's countReadyWork (new remoteReadyCounter). The client-side policy remains only for servers that do not advertise the token. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(create): default created_by to the request's actor in the create role created_by was stamped in two front doors and never in the library: the CLI (creationActorStamp, with a remote-workspace special case) and the three httpapi create handlers. A library caller of Lifecycle.Create or BatchCreator with an empty CreatedBy stored "" locally and the actor over http. PreparePublicCreateRequest, which every create shape prepares through (Lifecycle.Create, BatchCreator items, batch-apply create items), now defaults an empty CreatedBy to request.Actor; an explicit value is kept. The handlers no longer stamp, `bd create` and the state event create pass only the actor, and creationActorStamp/isRemoteBackendWorkspace are gone. The CLI sites that still create through the raw CreateIssue seam (swarm, todo, gate, the create form) keep stamping currentActor(): that seam is shared with import, where defaulting would re-attribute imported rows, and the http store refuses it anyway, so the remote special case was never reachable there. Conformance: the lifecycle-create, batch-creator and batch-apply contracts now pin created_by == actor for an item that names none, on every leg. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(httpclient): GetIssue answers a miss with storage.ErrNotFound, like the local stores The http store's raw GetIssue answered a missing id with (nil, nil), where DoltStore and the embedded store return a wrapped storage.ErrNotFound. A caller written against the backend contract read the http miss as a hit: `bd create --graph` refused every explicit-id plan over http (patched in cmd/bd on feat/http-mc-corpus; that workaround is reverted there). GetIssue now returns the miss (and the empty id) as storage.ErrNotFound, spelled as issueops.GetIssueInTx spells it. GetLabels, which reads through GetIssue, keeps the local read's "no labels" answer for a missing id; the `bd list --parent` walk reads the typed miss as "parent issue not found". The served bridge test now holds the local reference store and the http store to the same miss: ErrNotFound with the same text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(createbatchequiv): re-record the apply golden for the created_by default c2866ea7fe made the create role default an empty CreatedBy to the request's actor, so every create item of the apply scenario's batch (actor "apply-writer") now stores created_by "apply-writer" instead of "". TestCreateBatchFastPathsMatchPerRow_*/apply compared the stored rows to a digest recorded before that change and failed on exactly the three tables the column reaches: issues and wisps (the row) and events (the update event's old-value snapshot). Fast and per-row bodies still agree; the batch-apply conformance contract pins the same value. Bisected with bazel: passes at be92efe40f's integ twin 696f7acc8e, fails from the created_by commit on. Only apply.json's three digests move. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * style: gofmt ledger.go and the externaldeps remote-roles test Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cmd/bd): bd create reads routing settings local-only on a remote backend too determineAutoRoutedRepoPath skipped a remote backend's settings document (routing targets are local paths that one shared document cannot name for every client), but getRoutingConfigValue, which `bd create` and migrate-personal read routing.* and contributor.* through, still asked it. The same workspace could route a create one way and a lookup another, and every create paid a settings round trip per key. Both now go through routingSettingsStore: nil for a remote backend, so routing comes from config.yaml / the environment only there, and a local store is still consulted. A unit test holds both reads to the rule with a store that counts settings reads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cmd/bd): say so when update -s closed drops an ambient CLAUDE_SESSION_ID Over http `bd update -s closed` cannot carry closed_by_session, so the CLI drops it rather than refusing the close. An explicit --session printed a notice; the ambient CLAUDE_SESSION_ID every agent under Claude Code exports was dropped without a word, a silent data difference from a local backend (the served corpus's mc-update-meta-status-closed). The drop is now named on stderr in both cases, once per command, pointing at `bd close`, whose wire operation records the session. The served e2e asserts the notice. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(backend/http): hold bd list --limit 2 to each side's own unlimited order TestE2E_ListWithGCFiltersMatchesEmbedded compared the --limit 2 rows of the served and embedded workspaces as sets. The seed has four P2 rows, so the limit cuts a priority tie whose created_at order differs between two workspaces seeded seconds apart: a test-only flake, the order itself being total. Each side's two rows must now be, in order, the first two of that same side's --limit 0 listing; the unlimited listings are still compared across sides by the shape loop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test: unit-tier pins for the created_by default, the policy token and the GetIssue miss Three review mutations were caught only by a heavier tier (the uow conformance legs, the served httpclient tier) or by one package's test alone. Each now has a unit test where its rule lives: - issueops: PreparePublicCreateRequest defaults an empty CreatedBy to the actor and keeps an explicit one, without mutating the caller's request. - externaldeps: the policy layer AppliedToProvider finds becomes the handshake's policy.external_dependencies through httpapi.Listen, the composition bd serve performs, and a raw provider's handshake lacks it. - httpclient (no embedded engine): GetIssue over the real wire client against a stub server answers a 404 not_found, and the empty id without dialing, as storage.ErrNotFound spelled like the local stores. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(changelog): S6b/c/d entries match the code The S6 entry still said `bd create` suppresses created_by on a remote workspace and that the external-dependency policy runs client-side. Since S6b/c/d, created_by defaults to the actor in the library on every backend, and every bd serve composed through the policy advertises policy.external_dependencies, so clients pass those operations through; the client-side policy (now in role terms) runs only against a server that does not advertise it. New entries: the advertised policy token, bd ping over http, the created_by library default, closed_by_session dropped by an http `bd update -s closed` (with a notice, typed or ambient), reopen without a Provenance label over http, local-only routing.* / contributor.* on a remote backend, GetIssue's miss as storage.ErrNotFound, and list/children/show counts/dep tree over http. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(externaldeps): keep S6's list --ready, --claim-next refusal and lost-race error on the S6c composition The re-adopted S6 head (#7288) carries the review fixup's remote role composition; S6c replaces it with its own (rolesAreRemote, the widened ready window, the policy passthrough). Two behaviours S6 shipped and its reviews pinned would otherwise go: - bd close --claim-next against a server that does not apply the policy is refused whole, before anything is read or closed, with "the served batch close cannot carry a next claim, so nothing was closed; close without --claim-next, then run `bd ready --claim`". S6c passed the batch to the http closer, whose W-CloseBatchRequest.ClaimNext refusal drops the remedy, so TestE2E_BDOverHTTP's two refuseClaimNext steps went red. A request invalid on every backend is still ErrValidation first, and a server that applies the policy still gets the request untouched. - remoteReadyClaimer.ClaimNext reports a page on which every candidate was lost to another actor as "claim ready: lost N races ...", not as the empty answer that means there is no work. - `bd list --ready` (List with ReadyFlag) is answered by the policy store's own reader over the served ready reads, as S6 does. S6c passed it to the served listing, which cannot carry ReadyFlag (httpclient ledger row E-ListRequest.ReadyFlag), so it exited 1 over http with or without external refs; TestE2E_BDOverHTTP and TestServedRolesKeepTheExternalDependencyPolicy were red on it. TestRemoteReaderAnswersAReadyListingWithoutTheWireFlag pins it, with the fake's served List refusing ReadyFlag as the wire does. S6's composition tests now run against S6c as remote_roles_composition_test.go. Their fake serves Ready the way a server does (the S6 composition read ready work through the legacy policy reader instead), and two call logs gain that Ready. TestRemoteBatchCloserRefusesANextClaim, TestRemoteBatchCloserValidatesANextClaimFirst and TestRemoteReadyClaimerReportsLostRaces were red on S6c before this change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(externaldeps): unassigned claim-next and fail-closed close reads Review fixes for the S6c composition against a server that does not advertise policy.external_dependencies: the two majors of review attempt 1, plus the minors on the same code. - ReadyClaimer: the composed claim-next reads only open, unassigned ready rows (Unassigned=true, Assignee cleared), the candidates the local ClaimReadyIssueInTx selects. A row another actor holds, or one already assigned to the caller, is no longer taken or counted as a lost race. Each pass reads 25 candidates past the blocked rows, as httpclient's composed claim does, and a full window lost end to end is read once more: claimed rows leave the unassigned set. Only a claim that tried candidates and won none is an error. - BatchCloser: an externally blocked item travels to the server only when its status read finds it closed or not found (liveRefusal). Any other read error is that item's outcome, so a transient or auth failure no longer forwards a refused close to a server that will not refuse it. - TreeWalker: a failed capability probe renders the external leaves over the walked tree instead of failing a walk the server already answered. appendTreeExternalReferences skips an id the tree holds, so an enforcing server's own leaves are not doubled. - remoteEdges names each anchor once and skips an empty one, which the http EdgeReader refuses with ErrValidation. The composition fakes now honor Unassigned/Assignee as workapi.BuildReadyFilter does, model a rival claim landing first and a failing GetIssue, and refuse an empty edge anchor as httpclient does. New: TestRemoteReadyClaimerTakesOnlyUnassignedWork, TestRemoteReadyClaimerWalksAContendedFront, TestRemoteBatchCloserAnswersAFailedReadWithIt, TestRemoteEdgesNamesEachAnchorOnce, and the probe-failure cases of TestRemoteTreeWalkerAddsExternalLeaves. Each is red with its fix reverted. From review attempt 2, three nearby cleanups: - TestServedRolesKeepTheExternalDependencyPolicy seeds open rows held by another actor and by the claimant ahead of the free work, then claims with and without an assignee filter. The unassigned-only claim is now pinned over a real served server, not only through the fakes: red with the pre-fixup remote_roles.go, with filter.Unassigned dropped, and (the filtered claim) with an explicit assignee honored. - The capabilities description in openapi.v0.yaml (and the regenerated types.gen.go comment) no longer calls the whole list build-level: policy.external_dependencies depends on how the server composed its roles, as the paragraph above it says. - createbatchequiv's golden note names issueops.PreparePublicCreateRequest instead of a commit id that is not on this branch. Agent-Signature: claude-code-claude-opus-5-5-max on behalf of Julian Knutsen Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(backend/http): count a not_found read as reaching the remote in #7469's credential doors main's #7469 added TestExplicitCredentialIgnoresTheEnvPlaintextGrant. Its OpenWith and Open doors read bd-1 from plaintextRemote, which answers every issue read not_found, and the granted leg needs that read to return a nil error. That held while the http client answered a miss with (nil, nil). This branch's "fix(httpclient): GetIssue answers a miss with storage.ErrNotFound, like the local stores" makes the same read return storage.ErrNotFound. So on main plus this branch both doors fail at per_open_credential_test.go:392 ("with Target.AllowInsecureCredential: not found: issue bd-1") under plain go test. The merge is textually clean, so only a build of the merge shows it. The two store doors now count storage.ErrNotFound as success, since that answer came off the wire. The assertions are unchanged. The refused leg still needs the "refusing to send a credential" error and no request on the transport. The granted leg still needs exactly one request carrying "Bearer explicit-token": a granted read that never reaches the wire still fails at :408. Agent-Signature: claude-code-claude-opus-5-5-max on behalf of Julian Knutsen Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
242 lines
10 KiB
Go
242 lines
10 KiB
Go
// Contributed by gascity from bd-enterprise (internal/enterprise/httpstore/resolve.go@49d1df2f6)
|
|
// to OSS beads under the MIT license.
|
|
package httpclient
|
|
|
|
import (
|
|
"context"
|
|
"errors"
|
|
"fmt"
|
|
"net/http"
|
|
"strings"
|
|
|
|
"github.com/steveyegge/beads/internal/httpapi/apigen"
|
|
"github.com/steveyegge/beads/internal/httpclient/encode"
|
|
"github.com/steveyegge/beads/internal/httpclient/wire"
|
|
"github.com/steveyegge/beads/internal/types"
|
|
"github.com/steveyegge/beads/issueops"
|
|
)
|
|
|
|
// The id-resolution surface (design D11). ResolvePartialID is the front door
|
|
// every id-taking command goes through, and it makes exactly three store
|
|
// probes: an exact-ids SearchIssues, two GetConfig reads for the prefix
|
|
// vocabulary, and — only if those fail — a substring SearchIssueIDs. The first
|
|
// two are served here; the third has no wire operation at all and is on the
|
|
// unsupported allowlist, where the refusal below gives it its vocabulary.
|
|
|
|
// ErrPartialIDSearch reports that a substring or prefix id lookup was asked of
|
|
// a server that publishes no operation for one.
|
|
var ErrPartialIDSearch = errors.New("partial-id search is not available over HTTP")
|
|
|
|
// PartialIDSearchError is D11's dedicated refusal, and it is dedicated because
|
|
// the raw failure it replaces answers the wrong question.
|
|
//
|
|
// The input may be a partial id OR a full id that simply does not exist, and
|
|
// the client cannot tell which: it asked for an exact row and got nothing back.
|
|
// A "failed to search issues" fallthrough would report the second case as a
|
|
// backend fault and the first as nothing at all, so the text names both
|
|
// outcomes and the one recovery that covers them.
|
|
type PartialIDSearchError struct {
|
|
// Input is what the user typed, echoed so the message is about their id.
|
|
Input string
|
|
// ServerURL is the server that was asked.
|
|
ServerURL string
|
|
// Unsup is the portable sentinel, so errors.As classification holds through
|
|
// this type exactly as it does through every other refusal here.
|
|
Unsup *ErrHTTPUnsupported
|
|
}
|
|
|
|
func (e *PartialIDSearchError) Error() string {
|
|
return fmt.Sprintf("no exact issue %q on bd serve at %s; partial-id search is not available over HTTP — "+
|
|
"check the id or use a local workspace", e.Input, e.ServerURL)
|
|
}
|
|
|
|
// Unwrap also names issueops.ErrNotFound: the one thing the client does know
|
|
// is that no row has exactly this id, and a caller classifying the outcome
|
|
// (bd show's "Issue X not found", the routed-lookup fallbacks) must read it as
|
|
// a miss rather than as a backend fault (S6b).
|
|
func (e *PartialIDSearchError) Unwrap() []error {
|
|
return []error{e.Unsup, ErrPartialIDSearch, issueops.ErrNotFound}
|
|
}
|
|
|
|
func (s *Store) partialIDSearch(op, input string) error {
|
|
e := &PartialIDSearchError{Input: input, ServerURL: s.target.String()}
|
|
if unsup, ok := s.unsupported(op).(*ErrHTTPUnsupported); ok {
|
|
e.Unsup = unsup
|
|
}
|
|
return e
|
|
}
|
|
|
|
// SearchIssueIDs is the resolver's substring id search, which has no wire
|
|
// operation: it answers D11's partial-id refusal (a not-found, see
|
|
// PartialIDSearchError.Unwrap) without dialing, rather than the generic stub's
|
|
// bare "not supported".
|
|
func (s *Store) SearchIssueIDs(_ context.Context, query string, _ types.IssueFilter) ([]string, error) {
|
|
return nil, s.partialIDSearch("SearchIssueIDs", query)
|
|
}
|
|
|
|
// ExactIDLookupOnly satisfies utils.ExactIDLookupStore: with no substring
|
|
// search on the wire, the resolver stops at its exact lookups, so a missing
|
|
// id is a not-found after one getIssue instead of a prefix-vocabulary read,
|
|
// a repeated probe and a refused search.
|
|
func (s *Store) ExactIDLookupOnly() bool { return true }
|
|
|
|
// SearchIssues serves the two shapes the v0 wire can express and refuses every
|
|
// other one.
|
|
//
|
|
// The classification is the encoder's, not this method's: PlanSearch decides
|
|
// SHAPE FIRST and then sweeps the fields that shape cannot read, so a filter
|
|
// naming both an id set and a parent is refused before either arm is chosen.
|
|
// What is decided here is only what to do with each shape once it is named.
|
|
//
|
|
// The `query` argument is the substring search, and it has no wire operation:
|
|
// it refuses with D11's partial-id text rather than with a bare sentinel,
|
|
// because a caller that reaches this with a non-empty query is resolving an id
|
|
// and the useful thing to say is that the id was not found exactly.
|
|
func (s *Store) SearchIssues(ctx context.Context, query string, filter types.IssueFilter) ([]*types.Issue, error) {
|
|
if strings.TrimSpace(query) != "" {
|
|
return nil, s.partialIDSearch("SearchIssues", query)
|
|
}
|
|
plan, err := encode.PlanSearch(filter, func() encode.ListConfig { return s.listConfig(ctx) })
|
|
if err != nil {
|
|
return nil, s.inexpressible("SearchIssues", err)
|
|
}
|
|
switch plan.Shape {
|
|
case encode.SearchExactIDs:
|
|
return s.getIssuesByExactID(ctx, plan.IDs)
|
|
case encode.SearchParentWalk:
|
|
return s.walkDescendants(ctx, plan)
|
|
}
|
|
return nil, s.unsupported("SearchIssues")
|
|
}
|
|
|
|
// getIssuesByExactID is D11's fast path: one getIssue per named id, in the
|
|
// caller's order, bounded by the encoder at MaxExactIDs.
|
|
//
|
|
// A 404 becomes an ABSENT ROW, not an error. That is the whole reason this is a
|
|
// special case rather than a filter: ResolvePartialID's first probe reads
|
|
// `err == nil && len(issues) > 0`, so a miss reported as an error would abandon
|
|
// resolution at the exact point the resolver is supposed to fall through to its
|
|
// prefix pass. Every other failure — a dead connection, a busy server, a
|
|
// refused credential — passes through, because none of them is evidence about
|
|
// whether the row exists.
|
|
func (s *Store) getIssuesByExactID(ctx context.Context, ids []string) ([]*types.Issue, error) {
|
|
found := make([]*types.Issue, 0, len(ids))
|
|
for _, id := range ids {
|
|
path, err := wire.IssuePath(id)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
var details types.IssueDetails
|
|
err = s.dispatch(ctx, wire.Request{
|
|
Op: wire.OpGetIssue,
|
|
Method: http.MethodGet,
|
|
Path: path,
|
|
IssueID: id,
|
|
}, &details)
|
|
if errors.Is(err, issueops.ErrNotFound) {
|
|
continue
|
|
}
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
// The detail view carries labels in a field of its OWN rather than on
|
|
// the embedded issue, and the local SearchIssues hydrates them onto the
|
|
// issue. Lifting them across is what makes the two answers the same
|
|
// value; a caller reading `issue.Labels` would otherwise see an
|
|
// unlabeled row over http and a labeled one locally.
|
|
issue := details.Issue
|
|
if len(issue.Labels) == 0 && len(details.Labels) > 0 {
|
|
issue.Labels = append([]string(nil), details.Labels...)
|
|
}
|
|
// Issue.RowVersion is json:"-", so the decode above left it at 0;
|
|
// details.Revision is getIssue's only wire spelling of the token, the
|
|
// same stitch bridge.go's own GetIssue makes. Without this, an exact-id
|
|
// hit through SearchIssues (e.g. the resolver's fast path) would carry
|
|
// a RowVersion of 0 where a getIssue of the same row populates the real
|
|
// token, and a caller that feeds the search result's RowVersion into a
|
|
// guarded write would get a spurious mismatch instead of none.
|
|
version, err := parseRevision("searchIssues(exact id)", details.Revision)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
issue.RowVersion = version
|
|
found = append(found, &issue)
|
|
}
|
|
return found, nil
|
|
}
|
|
|
|
// walkDescendants is D4's hierarchical shape: paged listIssues?parent=<id>.
|
|
//
|
|
// The CLI asks each level for every descendant (Limit=0 per level), and
|
|
// unlimited maps to PAGING TO EXHAUSTION rather than to the wire's `limit=0`,
|
|
// which a non-loopback server refuses outright. The recursion itself belongs to
|
|
// the caller — findAllDescendants re-parents the filter at every level — so
|
|
// this answers one level.
|
|
func (s *Store) walkDescendants(ctx context.Context, plan encode.SearchPlan) ([]*types.Issue, error) {
|
|
// Not projected: a descendant walk hands its rows back as whole issues, and
|
|
// a caller of the hierarchy has no way to learn a body was withheld.
|
|
rows, err := s.fetchIssuePages(ctx, plan.Params, false, 0, 0, "", nil)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
out := make([]*types.Issue, 0, len(rows))
|
|
for _, row := range rows {
|
|
if row != nil && row.Issue != nil {
|
|
out = append(out, row.Issue)
|
|
}
|
|
}
|
|
return out, nil
|
|
}
|
|
|
|
// ErrSettingRedacted reports a setting whose value the server withheld because
|
|
// its KEY marks it credential-bearing.
|
|
var ErrSettingRedacted = errors.New("bd serve withholds this setting's value")
|
|
|
|
// RedactedSettingError is ledger row L9 made answerable: the value is absent
|
|
// with a reason, rather than absent as an empty string.
|
|
//
|
|
// Returning "" would be a dropped read dressed as an unset key, and the two are
|
|
// not the same answer — one says the workspace stores nothing, the other says
|
|
// the workspace stores something this client may not see.
|
|
type RedactedSettingError struct {
|
|
Key string
|
|
ServerURL string
|
|
}
|
|
|
|
func (e *RedactedSettingError) Error() string {
|
|
return fmt.Sprintf("bd serve at %s withholds %q: the key marks it credential-bearing, "+
|
|
"so its value is not served to a client", e.ServerURL, e.Key)
|
|
}
|
|
|
|
func (e *RedactedSettingError) Unwrap() error { return ErrSettingRedacted }
|
|
|
|
// GetConfig serves getSetting. D11's prefix probes — `issue_prefix` and
|
|
// `allowed_prefixes` — ride it, and they are flat legacy keys present in the
|
|
// settings enumeration, so nothing about them is special-cased here.
|
|
//
|
|
// A key nothing stored and a key stored empty are ONE answer on this operation,
|
|
// exactly as they are on the local store: the wire omits the value in both
|
|
// cases and this returns ("", nil), which is what every caller of GetConfig
|
|
// already treats as "unset". The one answer that is NOT "" is a redacted key,
|
|
// where a value may well exist and is withheld (L9).
|
|
func (s *Store) GetConfig(ctx context.Context, key string) (string, error) {
|
|
path, err := wire.SettingPath(key)
|
|
if err != nil {
|
|
return "", err
|
|
}
|
|
var setting apigen.Setting
|
|
if err := s.dispatch(ctx, wire.Request{
|
|
Op: wire.OpGetSetting,
|
|
Method: http.MethodGet,
|
|
Path: path,
|
|
}, &setting); err != nil {
|
|
return "", err
|
|
}
|
|
if setting.Redacted {
|
|
return "", &RedactedSettingError{Key: key, ServerURL: s.target.String()}
|
|
}
|
|
if setting.Value == nil {
|
|
return "", nil
|
|
}
|
|
return *setting.Value, nil
|
|
}
|