Skip to content

Mount file on batch change steps containers

Created by: jensim

User outcome and current workflow

It's frequent for users to run complex scripts or internal tools in batch changes. To do so today, they gave two choices:

  • bake the script/ or binary inside the step container. This is painful and slows down iteration as it requires to rebuild the container.
  • Use steps.file, which is also painful and slows down iteration. To convince yourself, paste a python script of a 100 line in a batch spec and fix the indentation :).

Proposal

Allow users to mount a file (a script, a binary of an internal tool) on the batch spec container. This means the user can iterate on the file easily, without needing to copy-paste it inside the spec, or rebuild a container.

One thing we need to figure out is caching. If the spec does not change, but the file changes, we should invalidate the cache.

This is discussed in RFC 560 REVIEW: Mount file on Batch Changes container

Additional context

Impacted customers (details in thread)

Delivery plan