Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vendor: Glide update, droppping tectonic-node-controller and trimming cluster-api #291

Closed
wants to merge 1 commit into from

Commits on Sep 20, 2018

  1. vendor: Glide update, droppping tectonic-node-controller and trimming…

    … cluster-api
    
    Generated with:
    
      $ glide update --strip-vendor
      $ glide-vc --use-lock-file --no-tests --only-code
      $ bazel run //:gazelle
    
    using:
    
      $ glide --version
      (cd $GOPATH/src/github.com/Masterminds/glide && git describe)
      v0.13.1-7-g3e13fd1
      $ (cd $GOPATH/src/github.com/sgotti/glide-vc && git describe)
      v0.1.0-2-g6ddf6ee
      $ bazel version
      Build label: 0.16.1- (@non-git)
      Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
      Build time: Mon Aug 13 16:42:29 2018 (1534178549)
      Build timestamp: 1534178549
      Build timestamp as int: 1534178549
    
    The tectonic-node-controller removal catches us up with 596591b (.*:
    replace tectonic node controller with machine config operator,
    2018-09-10, openshift#232).
    
    The cluster-api trim adjusts the content from b00e40e (vendor: Add
    client from sigs.k8s.io/cluster-api, 2018-09-04, openshift#119).  Because
    cluster-api wasn't in glide.lock, I suspect neither glide nor glide-vc
    were run before that commit.
    wking committed Sep 20, 2018
    Configuration menu
    Copy the full SHA
    cbbe745 View commit details
    Browse the repository at this point in the history