Open rhuanbarreto opened 1 week ago
This could maybe be a preset: deploy
that sets all the default/necessary options?
A preset is good but this also needs to have its own command to help triggering it on CD for example.
moon deploy
would basically be the same code as moon run
though. I don't really see how they would be different.
what could be a filter to target those kind of tasks without having a name convention like moon run :deploy
?
Is your feature request related to a problem? Please describe.
moon check
runs alltest
andbuild
type tasks. Very useful for local development and CI. But in CD, after we merge to main, I need to add one naming convention in tasks to be calleddeploy
with the following config:Then in the CD pipeline I run
moon run :deploy
in order to deploy the whole monorepo.Describe the solution you'd like
It would be good to have one new task type called
deploy
which assume some defaults. This would simplify a lot for the ones configuring the monorepo. Also a commandmoon deploy
likemoon check
would be very useful and would make the mental model of using moon very homogeneous, once you could also use themoon deploy
command to run a deploy to a development environment locally in addition to CD.So the same task would be:
And I could run all deploy tasks with
moon deploy
Describe alternatives you've considered
Today only alternative is to run
moon run :deploy
or using filters or relying on naming conventions.