Closed kevindrosendahl closed 5 years ago
starting to lay down code and feel it out
required changes:
still deep in the refactoring, no clear blockers so far
current milestone goal is to get builds working again only allowing you to deploy the whole system (i.e. no external interface change) but with all of the components properly shuffled around into their new homes.
from there adding in path-ed deploys should be a clear path
passed the above mentioned milestone last week.
had to take a bit of a detour to change up the data structures that represent a system as access patterns have changed (used to be a build/deploy would operate on an entire system tree, now we're dealing with subpaths, both iterating on subpaths and replacing whole subpaths of the tree).
that work is mostly in place now so should be able to push this past the finish line in the next few days time permitting
mostly everything working. now just need to add proper locking then do a tidying up sweep
code is complete, adding a few final tests around template resolution but pretty much ready to merge
some (mostly breaking) changes in the api:
accepted
services
is now workloads
and returns builds for all leaf paths (both services and jobs)workload
sidecars will be omitted from the body if emptybuildId
is now nullable/component:subcomponent
pathfailure_mode
to failureMode
, omit if null/component:subcomponent
now with semver/branch references, it's interesting to be able to redeploy a subsystem of the same version of the system.
should be able to do something like:
which will redeploy the whole
/foo/bar
subsystem using the same version of the system as is currently deployed