Remove unchanged/useless output from k8s_object about rules_k8s HOT 6 CLOSED

I changed the title. Currently this does nothing, so we should just remove it.

from rules_k8s.

I am not sure it is useless. What is the reason for not outputting the expanded yaml file when running build?

from rules_k8s.

What comes out during the build isn't expanded (pushing wouldn't be hermetic).

Right now it is literally copying the input to the output :)

from rules_k8s.

Yes, the current output is not useful. It would only be useful if it would output a yaml with images resolved. It should be hermetic, since the image would point to the digest.

from rules_k8s.

Right, and we can only publish the image and produce a resolved template on bazel run since that is inherently not hermetic.

from rules_k8s.

Just to be clear, our hermetic references are to different things :)

What I'm saying is non-hermetic is publishing an image, since it talks to the registry service and accesses things outside of the sandbox like your credential keyring. This would not run successfully on a distributed build system without network (or your local filesystem) for instance.

The result of bazel run (the resolved output) is what I'd call pseudo-hermetic because all of the external references are now content-addresses. So while it isn't closed per-se, the only way you can successfully deploy it is if get exactly what you intended.

from rules_k8s.