Refactor ibm cloud provider use go module

[jichenjc]

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/2019-03-19-go-modules.md
noticed this, should we follow this or keep using dep or take this a future action?

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

[xunpan]

I think keep consistent with cluster-api is fine.
go module should be future direction as it is official go dependecy management tool. However, currently, there is no painpoint for using dep in ibm cloud provider. When cluster-api switch its dependecy management tool. We can follow it up.

[jichenjc]

ok, let's take this as future item

[gyliu513]

cluster api is working for this kubernetes-sigs/cluster-api#1054 (comment)

[jichenjc]

Thanks, I am looking at it and hopefully to replicate to here soon...

[jichenjc]

/assign

let me try this

[fejta-bot]

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[gyliu513]

/remove-lifecycle stale

@jichenjc do you still have plan to work for this? I think we need to take this as priority now.

[k8s-ci-robot]

@jichenjc: The label(s) sig/ibmcloud cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

/kind feature
/sig ibmcloud

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/2019-03-19-go-modules.md
noticed this, should we follow this or keep using dep or take this a future action?

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

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.

[jichenjc]

@gyliu513 I am buried in some other stuffs recently, so unassign myself and let's see anyone can help on this, thanks for the reminder

[gyliu513]

/assign

Thanks @jichenjc for the heads up, let me check this.