This reverts commit 0768e1b7f6aa973f9879ac5b8f622dd2f3d88f1d.
In the original patch https://github.com/bazelbuild/rules_docker/pull/2077, tag and stamp_input fields of PushInfo were removed with the assumption that they become obsolete since bazel 5.0. However, bazel itself doesn't control our customized PushInfo provider. And we have been using them with bazel 5.3 with no issues.
We have some downstream rules that are relying on these field and would like to keep using them in latest version of rules_docker.
@philsc for vis.
PR Checklist
Please check if your PR fulfills the following requirements:
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
PR Type
What kind of change does this PR introduce?
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
This reverts commit 0768e1b7f6aa973f9879ac5b8f622dd2f3d88f1d.
In the original patch https://github.com/bazelbuild/rules_docker/pull/2077,
tagandstamp_inputfields ofPushInfowere removed with the assumption that they become obsolete since bazel 5.0. However, bazel itself doesn't control our customizedPushInfoprovider. And we have been using them with bazel 5.3 with no issues.We have some downstream rules that are relying on these field and would like to keep using them in latest version of rules_docker.
@philsc for vis.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information