Hey all, so i have a dagster kubernetes instance , and i was wondering is it possible to let my instance execute on my local vm? The use case is to run tests on code that haven’t been deployed as images yet. I wondered if this was possible through a combination of celery-worker and api grpc.. 😅 LMK if more clarification is needed.

Hi Charles, you’re looking to test your jobs locally?

yes 🙂 . For a regression test for example, the code is in git, but i don’t want to produce an artifact until the test passes

Ideally you shouldn’t need to mess with Celery at all- the executor and run launcher abstractions exist to help you run jobs locally or in production without changing business logic

the complexity comes from the fact that we are trying to avoid giving our build agent permissions to execute locally in CI 😞

Not sure I fully follow, but some thoughts: • The best case would be if you could test your job in process, possibly by mocking out the resource/etc. that you don’t want available in your CI https://docs.dagster.io/tutorial/intro-tutorial/testable#testing-ops-and-jobs • If you do have to commit to launching jobs ‘remotely’, doing so over the graphql api is likely the best option