https://pantsbuild.org/ logo
Join Slack
Powered by
Slightly off topic: A monorepo with multiple servi...
# general
f
Slightly off topic: A monorepo with multiple services - each service wants to be deployed independently - that should be support by github actions. So multiple yaml files, probably multiple per service and stage and multiple environments with secrets etc. that would be one “compatible” way of doing things, right? I guess that’s probably independent from pants and just a question about monorepos - there might be other “build system ways to deploy”? 🤔
h
Well, you can have a single CI config, and delegate "what gets deployed" to a lower level, perhaps using 
pants
queries (like the 
--filter-*
and 
--changed-*
flags) to figure out what needs to be deployed.
If you have separate actions for each service, they must all get triggered on every commit. And it's extra setup every time you add a service
f
You could filter triggers with regex patterns - so a subfolder f.e.
But ok, maybe using pants is better
h
But service A and service B both depend on local library C, that regex gets complicated, and hard to maintain
Pants already knows about dependencies, reconstructing them in regex form seems like a step back
Pants knows about your dependencies at a fine-grained level, based on your 
import
statements alone. So you get that sort of logic automagically.
Well, your 
import
statements plus whatever other dep inference magic you turn on
f
so pants would automatically redeploy as needed?
anyways this discussion is still too early for me, catching up with pants+docker
h
Pants can tell you what needs to be redeployed
whether it actually does the deploy depends on how you deploy
f
Ok got it
2 Views
Open in Slack
PreviousNext
Powered by