Re: Migration endpoint removed in 226 :(

Home Messages Hashtags Subgroups

Dieu Cao <dcao@...> #3552 Apologies Mike. It was my understanding that the endpoint was incomplete/non functional and as it was marked experimental, was okay to remove. Dieu CF CAPI PM toggle quoted message Show quoted text On Wednesday, January 27, 2016, Mike Youngstrom <youngm(a)gmail.com> wrote: For anyone else that runs into this. I was able to revert https://github.com/cloudfoundry/cloud_controller_ng/commit/94ab558675641c8b325f821f9823721569c44fab from v227's CC commit a07fcc957ecf07d6c0f81d8f154b2b7bb8613f05 and the migrate functionality appears to work fine again. Mike On Wed, Jan 27, 2016 at 12:18 PM, Mike Youngstrom <youngm(a)gmail.com <javascript:_e(%7B%7D,'cvml','youngm(a)gmail.com');>> wrote: Not very nice removing the v1 service migration endpoint before actually removing v1 service support. Do you see any issue with my reverting that commit on the CC that went into v227? https://www.pivotaltracker.com/story/show/102725918 I don't see any issues using this for services that don't have any gateway data I'm not aware of? I used it with other simple v1 services successfully. Mike attachment.html
More All Messages By This Member

Join {cf-dev@lists.cloudfoundry.org to automatically receive all group messages.