Page MenuHomePhabricator

Allow repositories to be bound to an AlmanacService
ClosedPublic

Authored by epriestley on Dec 12 2014, 6:09 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Dec 9, 1:44 PM
Unknown Object (File)
Nov 20 2024, 5:33 PM
Unknown Object (File)
Nov 15 2024, 4:55 PM
Unknown Object (File)
Nov 12 2024, 3:08 PM
Unknown Object (File)
Nov 12 2024, 5:42 AM
Unknown Object (File)
Nov 8 2024, 12:04 AM
Unknown Object (File)
Oct 26 2024, 3:38 AM
Unknown Object (File)
Oct 22 2024, 3:47 AM
Subscribers

Details

Summary

Ref T2783. This is primarily exploratory and just figuring out what we're blocked on:

  • Allow a Repository to be bound to a Service. The Service may eventually define multiple read/write nodes, etc.
    • There's no UI to do this binding yet, you have to touch the database manually.
  • If a repository is bound to a Service, effect Conduit calls via calls to the remote service instead of executing them in-process.
    • These don't actually work yet since there's no authentication (see T5955).
Test Plan
  • Made a nice Service with a nice Binding to a nice Interface on a nice Device.
  • Force-associated a repository with the service using a raw MySQL query.
  • Saw Phabricator try to make a remote call to the service (on localhost) and fail because of missing auth stuff.
  • Also ran almanac.queryservices.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Allow repositories to be bound to an AlmanacService.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Dec 12 2014, 7:11 PM
This revision was automatically updated to reflect the committed changes.