Page MenuHomeElementl

Introduce docker context fixtures
AbandonedPublicDraft

Authored by jordansanders on Jul 2 2021, 8:11 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Feb 4, 9:38 PM
Unknown Object (File)
Dec 30 2022, 10:37 AM
Unknown Object (File)
Nov 30 2022, 2:52 AM
Unknown Object (File)
Nov 18 2022, 12:35 AM
Unknown Object (File)
Nov 14 2022, 1:42 AM
Unknown Object (File)
Nov 10 2022, 4:15 PM
Unknown Object (File)
Oct 28 2022, 4:27 PM
Unknown Object (File)
Aug 29 2022, 7:49 PM
Subscribers
None

Details

Summary

Run every docker compose comand in its own context. This has a few
benefits over always using the default context:

  • It better segregates our tests from the other stuff that we have running locally. For example, if a test adds an ECS local simulation context, we don't need to worry about naming collisions with an ECS local simulation context that might already exist.
  • It provides an entrypoint through which to override context - for example, if we want to use an ECS local simulation context.
Test Plan

unit

Diff Detail

Repository
R1 dagster
Lint
Lint Passed
Unit
No Test Coverage