Page MenuHomePhabricator

Add PhageActions to libphutil
ClosedPublic

Authored by epriestley on Feb 17 2017, 11:14 PM.
Tags
None
Referenced Files
Unknown Object (File)
Apr 15 2026, 3:30 AM
Unknown Object (File)
Mar 8 2026, 10:43 AM
Unknown Object (File)
Mar 1 2026, 8:36 PM
Unknown Object (File)
Feb 17 2026, 4:30 PM
Unknown Object (File)
Feb 11 2026, 5:07 PM
Unknown Object (File)
Feb 3 2026, 3:24 PM
Unknown Object (File)
Jan 31 2026, 2:46 AM
Unknown Object (File)
Jan 19 2026, 6:27 AM
Subscribers
None

Details

Summary

Ref T2794. I'm not 100% sold on the design of this and it doesn't interact with any other code yet, but get deployment-related code upstream.

The overall approach I'm taking here is that you build a "plan", which is like a DOM tree of stuff you want to do, then execute the plan.

The only plan we build or execute right now goes like this:

  • Phage Plan
    • Launch a local Phage agent
      • Have that agent run a bunch of commands

...but I think this approach should be flexible enough to accommodate more complicated deployment processes in the future.

Test Plan

Successfully deployed secure without typing a bunch of different commands.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

  • Don't write unconditionally to the debug logfile (I'll add some flags for this later).
This revision is now accepted and ready to land.Feb 17 2017, 11:52 PM
This revision was automatically updated to reflect the committed changes.