Add tags for go mod compatibility about api

[bbl]

+1 our old dependent builds are failing now:

go: github.com/openshift/[email protected]+incompatible: unknown revision v3.9.0

[HubertStefanski]

@mfojtik adding the following to .bashrc also seems to work for the meanwhile GOPROXY=https://proxy.golang.org as an alternative to your solution, at the very least it worked for the specific case we found in the operators used in Integr8ly

[mfojtik]

You can use:

go get -u github.com/openshift/api@master
go get -u github.com/openshift/[email protected]

To bump the openshift/api in your project. It will resolve to a commit and it is harder to track in go.mod. We are looking into automatic tagging for some repos, but it is not trivial as it might seem.

[grdryn]

Thanks folks! @HubertStefanski's workaround is sufficient for me for the moment, but @mfojtik's plan to have tags again in future sounds like a better eventual solution (some people may not be able to use proxy.golang.org for one reason or another).

[onlyjob]

IMHO this is a serious outstanding interoperability issue that requires urgent attention. Please tag.

Thanks.

[HubertStefanski]

Were tags used here before?

[grdryn]

This also seems to be related: operator-framework/operator-sdk#2394

[soltysh]

@smarterclayton @mfojtik since you've recently touched this, are we planning to start doing it? I think that applies not only to our API but every other one as well (client-go, library-go, etc).

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.