[manjari25]

Why?

The tango analyzer and its client adapter have no way to run in the reference orchestrator. This wires them in so a queue can select analyzer: tango.

What?

• tangoclient: Dial opens a lazy gRPC connection to Tango. Connection.ChangedTargetsClient builds the adapter for a remote and strategy (unset, shell, native).
• Config: a top-level tango block (address, signatureCacheBytes) and a per-queue analyzer.tango block (remote, strategy).
• Validation: a tango queue must use the git change provider, and the address and a positive cache size are required whenever any queue uses tango.
• Builder: one shared signature cache, a per-queue MySQL signature store, and the base revision read from the queue's own clone. Base-revision fetches take the same gitrepo.Repo lock as the git change provider.
• README: the new config keys and two limits. Tango needs a git-provider queue until the GitHub base revision exists, and native needs github:// URIs that the git provider doesn't emit.

Test Plan

• Unit tests added
• CI

Issue

[behinddwalls]

does this work with what we import internally? as these could be different?

[manjari25]

Do you mean version of go.uber.org/yarpc internally? If so, it should work. Internally we use at least what is pinned in the oss repo here.