You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CSV files is tucked away in a container and it's hard to understand exactly what the contents are. A nice way to get the contents would be for the HCO to add a file into the registry container with a list of key: value pairs of operators and their tag/sha sums. That way, users can figure out exactly the content of the container-registry by running something like docker run hco-registry cat /csv-content
The text was updated successfully, but these errors were encountered:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
kubevirt-bot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Jan 3, 2020
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
The CSV files is tucked away in a container and it's hard to understand exactly what the contents are. A nice way to get the contents would be for the HCO to add a file into the registry container with a list of
key: value
pairs of operators and their tag/sha sums. That way, users can figure out exactly the content of the container-registry by running something likedocker run hco-registry cat /csv-content
The text was updated successfully, but these errors were encountered: