Hi All I've noticed that `ephemeral-storage` is ...
# ask-metaflow
m
Hi All I've noticed that
ephemeral-storage
is not part of the
resource
decorator. Is this intentional or an oversight? I'd like to use the
resource
decorator and not the
kubernetes
one as we wish to ensure that our flows can also be run locally, e.g., for code development.
1
s
great observation. the reason for this omission is that
@batch
doesn't support
disk=
and in many ways
@resources
is the intersection of capabilities supported by both AWS Batch and Kubernetes.
m
OK, I see. I had a suspicion this might be the cause. Is there any way to specify ephemeral storage without using the kubernetes decorator? Or a possibility of adding this functionality to the resource decorator? Want to avoid using the kubernetes decorator, given that it stops one from run a flow locally.
alternatively, do you think it would be possible to add a no-op type flag to the kubernetes decorator, so that it can be "deactivated" for local runs?
v
yep, this is a missing feature - not the first time this issue comes up! I recorded the issue here so we can follow up
m
cool, thanks. I'll leave some comments on the issue then.
thankyou 1
FYI: I've left some comments on this issue now. Would you mind having a look, please?
s
responded in the gh issue