Merge legacy provider#160
Conversation
|
/assign @andrewsykim |
|
/hold |
|
/hold Just putting a hold on this until @nicolehanjing 's PR is merged |
@andrewsykim FYI my PR has merged |
|
Ok I will rebase this |
f925c10 to
04c8b6c
Compare
|
/hold cancel |
04c8b6c to
fd6e918
Compare
|
/lgtm |
|
@ayberk: changing LGTM is restricted to collaborators DetailsIn response to this:
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. |
|
/cc @andrewsykim |
- Stop importing the v1 provider because we need to move it out of upstream. - Copy the v1 provider here, when this merges we need to stop accepting most or all features in the k/k (legacy-cloud-providers)
fd6e918 to
093f4f1
Compare
|
/cc @wongma7 |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ayberk, nckturner, wongma7 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This copies the v1 provider to the local v1 directory. This merge needs to be coordinated with an effort to stop accepting features into k/k (legacy-cloud-providers).
I was working off #151 (so those commits show up here too) as I am expecting us to get that in first, but I can separate this if for some reason we want this to merge first.
Does this PR introduce a user-facing change?: