WIP: Run 'dep init' to create Gopkg.{toml,lock}

[sttts]

Golang/dep does not support picking up these dependencies yet properly. But at least
dep will warn the user when he chooses incompatible dependencies (so did @munnerz report, but with dep init --gopath I did not even get warnings, but it picked up master which it shouldn't).

A test run was published to https://github.com/kubernetes-dep-experiment/client-go

The goal is to vendor k8s.io/client-go, api, apimachinery and all other direct and transistive dependencies of client-go in the versions that are specified in https://github.com/kubernetes-dep-experiment/client-go's Gopkg.{toml,lock} with only specifying the right branch or tag of client-go, i.e.

[[constraint]]
  name = "k8s.io/client-go"
  version = "5.0.1"

For testing purposes one has to define the source for client-go, api and apimachinery to be in the kubernetes-dep-experiment org:

[[constraint]]
  name = "k8s.io/client-go"
  version = "5.0.1"
  source = "https://github.com/kubernetes-dep-experiment/client-go.git"

[[constraint]]
  name = "k8s.io/api"
  source = "https://github.com/kubernetes-dep-experiment/api.git"

[[constraint]]
  name = "k8s.io/apimachinery"
  source = "https://github.com/kubernetes-dep-experiment/apimachinery.git"

Compare https://github.com/sttts/kube-dep-test/blob/master/Gopkg.toml for a test project.

[sttts]

/cc @carolynvs @munnerz

[k8s-ci-robot]

@sttts: GitHub didn't allow me to request PR reviews from the following users: carolynvs.

Note that only kubernetes members can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @carolynvs @munnerz

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.

[sttts]

/cc @sdboyer

[k8s-ci-robot]

@sttts: GitHub didn't allow me to request PR reviews from the following users: sdboyer.

Note that only kubernetes members can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @sdboyer

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.

[sdboyer]

so did @munnerz report, but with dep init --gopath I did not even get warnings, but it picked up master which it shouldn't

wait, this sounds like a dep bug? is the "report" you're referring to an issue that was filed? i don't recall seeing one, though i haven't been as diligent as usual this week.

[sttts]

wait, this sounds like a dep bug? is the "report" you're referring to an issue that was filed? i don't recall seeing one, though i haven't been as diligent as usual this week.

I believe that was only a quick test with https://github.com/kubernetes-dep-experiment/client-go. Don't know that we have an issue for that, probably not.

@munnerz can you comment?

[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

[sttts]

Possibly a simple route: #55

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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