Scott Hood03/29/2022, 1:52 PM
and then use the same container image for each deployment repo, allowing them to directly reference the shared package from their code like they would locally.
- project_1 repo.py - project_2 repo.py - shared some_shared_resource
Wondering if anyone has good experience with this or examples of what their orgs did to manage multiple teams. Or if they simply found it easier to create one repo for all. The draw to multiple repos is more so simply a way of containing blast radius if one team causes a bad deployment, making it so that not all teams are affected. Other then that I don't see many examples of teams wanting to spin up different versions of python or different working environments for their code.
deployments: -name: "project_1" image: repository: "same_image" dagsterApiGrpcArgs: - "project_1/repo.py" -name: "project_2" image: repository: "same_image" dagsterApiGrpcArgs: - "project_2/repo.py"
Samuel Stütz03/29/2022, 2:51 PM
Scott Hood03/29/2022, 3:41 PM
Samuel Stütz03/30/2022, 7:41 AM