oci_push does not pass the runfile correctly to the dependent rule

[seyoung-song-walmart-com]

Assuming an executable rule X depends on a oci_push rule that depends on a oci_image rule, running the rule X build image using the oci_image but does not push the image using oci_push rule. The problem seems to be oci_push does not pass the push script the next executable rule while oci_image does.

[thesayyn]

I don't understand the problem here.

oci_push does not pass the push script the next executable rule while oci_image does.

I don't follow, oci_image does not have an executable in the DefaultInfo, and i am not sure what you mean by pass the executable.

[seyoung-song-walmart-com]

For example, let's assume that there are oci_image target t1, oci_push target t2 that is pointing t1 as dependency, and custom rule target t3 that has t2 in the deps.
When I execute "bazel run t3", t1 is executed, t2 is not executed and t3 is executed.
When I execute "bazel run t2", t1 is executed, then t2 is executed.
It means oci_image pass DefaultInfo correctly so that downstream target run executes dependent oci_image target.
However, oci_push does not pass DefaultInfo in the way that the downstream target run does not execute dependent oci_push target.
I hope this example explain the problem of oci_push clearly.