fix imports to the canonical packages #14617
Conversation
| @@ -128,7 +128,7 @@ func TestLookup(t *testing.T) { | |||
| users: userRegistry, | |||
| } | |||
|
|
|||
| identity := authapi.NewDefaultUserIdentityInfo(tc.ProviderName, tc.ProviderUserName) | |||
| identity := authuserapi.NewDefaultUserIdentityInfo(tc.ProviderName, tc.ProviderUserName) | |||
There was a problem hiding this comment.
well, at least one failure. Hopefully I get a nice report
|
[severity:blocker] |
openshift-bot
added
the
needs-rebase
|
Mechanical change to set up for the API type moves. @mfojtik ptal |
|
No functional changes, fixes up imports for a later move. [merge] |
|
LGTM |
|
the extended tests built. |
openshift-bot
removed
the
needs-rebase
|
flaked #14385 |
|
Evaluated for origin testextended up to 15616f6 |
|
@smarterclayton hold on the flake? The rest passed https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/1043/ and I have test run with a passing minimal here: https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/2387/ |
|
continuous-integration/openshift-jenkins/testextended SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended/656/) (Base Commit: 442a747) (PR Branch Commit: 15616f6) (Extended Tests: core(builds)) |
|
[test] |
|
Evaluated for origin test up to 15616f6 |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/2415/) (Base Commit: b0c0635) (PR Branch Commit: 15616f6) |
|
[merge] |
|
Evaluated for origin merge up to 15616f6 |
|
continuous-integration/openshift-jenkins/merge FAILURE (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/1056/) (Base Commit: e50d999) (PR Branch Commit: 15616f6) (Extended Tests: blocker) |
|
Origin Action Required: Pull request cannot be automatically merged, please rebase your branch from latest HEAD and push again |
openshift-bot
added
the
needs-rebase
Makes sure that all api package imports which would change in a refactor to match kube have aliases set to make the next step run smoothly.
@liggitt @smarterclayton Mostly done by script, fixup in a separate commit, plan to tag for merge on green (but not force merge since non-conflicting conflicts are likely).
[test][testextended][extended:core(builds)]