Andreas Stenius

Workdirs and output paths for the shell command targets were a bit of a fuzz to implement as I recall, and not all scenarios where clear to me at the...

I'm sketching an idea, see if that could be in the right direction.. Example BUILD file: ```python python_tests(name="tests") docker_image(name="base-tools") docker_test_image(name="test-image", dependencies=[":tests"], instructions=["FROM :base-tools"]) ``` This new `docker_test_image` would come with...

@meganvw Thanks for letting us know. It helps knowing what features are valuable to implement.

Hi @ptrhck, It is not to be expected shortly. I've done some preliminary proof of concept work to try stuff out, but it is not actively being worked on by...

I think it looks like express-openapi indeed produces a complete specification, although you will have to write the spec for each route manually. The upside to that vs a completely...

looked a bit more at express-openapi, and I must say that I was stumped to learn that you had to put your implementation along with the spec.. I don't fancy...

Thanks for the update, looking forward to it :)

> @kaos by "value" do you mean the benefit, or the concrete value type of the mapping? the concrete type I think. Also I'm not sure I've come across the...

Taking inspiration from Bazel's `rules_docker`, I'm investigating the use of two tools, [umoci](https://umo.ci/) and [skopeo](https://github.com/containers/skopeo), to create and manage docker images without the need for a docker daemon. Another option...

Ah, ok. Thanks. I think we can leave this open. The feature is still useful to have, and there'll be others that may use it.