cold-state-31010
04/13/2023, 3:44 PMchilly-gigabyte-83853
04/13/2023, 3:51 PMgarden deploy service1,service2 --dev=service1,service3
cold-state-31010
04/13/2023, 3:58 PMchilly-gigabyte-83853
04/13/2023, 3:59 PMcold-state-31010
04/13/2023, 6:58 PMbright-policeman-43626
04/14/2023, 4:34 PMgarden deploy --sync
, because Garden will understand which service it needs to change every time you deploy your service.
3. If the above makes sense, feel free to make more questions about it and I can help you build that example.
A couple of questions to help you a little bit more,
1. Are you guys using a mono-repo? or are your services segregated through multiple?
2. What is the end result in you guys want to achieve? Developer efficiency by having their own stack? Perhaps remote-link mode to sync with the cluster directly?
Hope this helps, feel free to keep the discussion this is going to a great place ❤️cold-state-31010
04/14/2023, 8:16 PMbright-policeman-43626
04/19/2023, 12:45 PMgarden deploy
without specifying the services, this will get the whole stack ready for your developers to start working on.
3. Any subsequent deployments your developers could do them either with a garden deploy service1,service2
to prevent shifting the ones that are already there.
4. Maybe another option could be that those "shared" services are part of a different Garden workflow, then you can easily spin them up separately with a CI job, then your developers can work with the other subset of applications freely (they won't have to specify which services they want to deploy, because the shared ones are going to be handled elsewhere).
Let me know if you would like me to go more in deep of any of the scenarios.cold-state-31010
04/21/2023, 9:04 PMbright-policeman-43626
04/26/2023, 7:38 AM