add prune and remove unused packages

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/CONTRIBUTING.md

@@ -1,31 +0,0 @@
-# Contributing Guidelines
-
-Welcome to Kubernetes. We are excited about the prospect of you joining our [community](https://github.com/kubernetes/community)! The Kubernetes community abides by the CNCF [code of conduct](code-of-conduct.md). Here is an excerpt:
-
-_As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities._
-
-## Getting Started
-
-We have full documentation on how to get started contributing here:
-
-<!---
-If your repo has certain guidelines for contribution, put them here ahead of the general k8s resources
--->
-
-- [Contributor License Agreement](https://git.k8s.io/community/CLA.md) Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests
-- [Kubernetes Contributor Guide](http://git.k8s.io/community/contributors/guide) - Main contributor documentation, or you can just jump directly to the [contributing section](http://git.k8s.io/community/contributors/guide#contributing)
-- [Contributor Cheat Sheet](https://git.k8s.io/community/contributors/guide/contributor-cheatsheet.md) - Common resources for existing developers
-
-## Mentorship
-
-- [Mentoring Initiatives](https://git.k8s.io/community/mentoring) - We have a diverse set of mentorship programs available that are always looking for volunteers!
-
-<!---
-Custom Information - if you're copying this template for the first time you can add custom content here, for example:
-
-## Contact Information
-
-- [Slack channel](https://kubernetes.slack.com/messages/kubernetes-users) - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. 
-- [Mailing list](URL)
-
--->

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/OWNERS

@@ -1,11 +0,0 @@
-# See the OWNERS docs: https://git.k8s.io/community/contributors/guide/owners.md
-
-approvers:
-- saad-ali
-- msau42
-- pohly
-
-reviewers:
-- saad-ali
-- msau42
-- pohly

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/README.md

@@ -1,51 +0,0 @@
-# [csi-release-tools](https://github.com/kubernetes-csi/csi-release-tools)
-
-These build and test rules can be shared between different Go projects
-without modifications. Customization for the different projects happen
-in the top-level Makefile.
-
-The rules include support for building and pushing Docker images, with
-the following features:
- - one or more command and image per project
- - push canary and/or tagged release images
- - automatically derive the image tag(s) from repo tags
- - the source code revision is stored in a "revision" image label
- - never overwrites an existing release image
-
-Usage
------
-
-The expected repository layout is:
- - `cmd/*/*.go` - source code for each command
- - `cmd/*/Dockerfile` - docker file for each command or
-   Dockerfile in the root when only building a single command
- - `Makefile` - includes `release-tools/build.make` and sets
-   configuration variables
- - `.travis.yml` - a symlink to `release-tools/.travis.yml`
-
-To create a release, tag a certain revision with a name that
-starts with `v`, for example `v1.0.0`, then `make push`
-while that commit is checked out.
-
-It does not matter on which branch that revision exists, i.e. it is
-possible to create releases directly from master. A release branch can
-still be created for maintenance releases later if needed.
-
-Release branches are expected to be named `release-x.y` for releases
-`x.y.z`. Building from such a branch creates `x.y-canary`
-images. Building from master creates the main `canary` image.
-
-Sharing and updating
---------------------
-
-[`git subtree`](https://github.com/git/git/blob/master/contrib/subtree/git-subtree.txt)
-is the recommended way of maintaining a copy of the rules inside the
-`release-tools` directory of a project. This way, it is possible to make
-changes also locally, test them and then push them back to the shared
-repository at a later time.
-
-Cheat sheet:
-
-- `git subtree add --prefix=release-tools https://github.com/kubernetes-csi/csi-release-tools.git master` - add release tools to a repo which does not have them yet (only once)
-- `git subtree pull --prefix=release-tools https://github.com/kubernetes-csi/csi-release-tools.git master` - update local copy to latest upstream (whenever upstream changes)
-- edit, `git commit`, `git subtree push --prefix=release-tools git@github.com:<user>/csi-release-tools.git <my-new-or-existing-branch>` - push to a new branch before submitting a PR

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/RELEASE.md

@@ -1,5 +0,0 @@
-# Release Process
-
-No tagged releases are planned at this point. The intention is to keep
-the master branch in a state such that it can be used for all
-supported branches in downstream repos which use these files.

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/SECURITY_CONTACTS

@@ -1,14 +0,0 @@
-# Defined below are the security contacts for this repo.
-#
-# They are the contact point for the Product Security Team to reach out
-# to for triaging and handling of incoming issues.
-#
-# The below names agree to abide by the
-# [Embargo Policy](https://github.com/kubernetes/sig-release/blob/master/security-release-process-documentation/security-release-process.md#embargo-policy)
-# and will be removed and replaced if they violate that agreement.
-#
-# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE
-# INSTRUCTIONS AT https://kubernetes.io/security/
-
-saad-ali
-msau42

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/build.make

@@ -1,124 +0,0 @@
-# Copyright 2019 The Kubernetes Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-.PHONY: build-% build container-% container push-% push clean test
-
-# A space-separated list of all commands in the repository, must be
-# set in main Makefile of a repository.
-# CMDS=
-
-# This is the default. It can be overridden in the main Makefile after
-# including build.make.
-REGISTRY_NAME=quay.io/k8scsi
-
-# Revision that gets built into each binary via the main.version
-# string. Uses the `git describe` output based on the most recent
-# version tag with a short revision suffix or, if nothing has been
-# tagged yet, just the revision.
-#
-# Beware that tags may also be missing in shallow clones as done by
-# some CI systems (like TravisCI, which pulls only 50 commits).
-REV=$(shell git describe --long --tags --match='v*' --dirty 2>/dev/null || git rev-list -n1 HEAD)
-
-# A space-separated list of image tags under which the current build is to be pushed.
-# Determined dynamically.
-IMAGE_TAGS=
-
-# A "canary" image gets built if the current commit is the head of the remote "master" branch.
-# That branch does not exist when building some other branch in TravisCI.
-IMAGE_TAGS+=$(shell if [ "$$(git rev-list -n1 HEAD)" = "$$(git rev-list -n1 origin/master 2>/dev/null)" ]; then echo "canary"; fi)
-
-# A "X.Y.Z-canary" image gets built if the current commit is the head of a "origin/release-X.Y.Z" branch.
-# The actual suffix does not matter, only the "release-" prefix is checked.
-IMAGE_TAGS+=$(shell git branch -r --points-at=HEAD | grep 'origin/release-' | grep -v -e ' -> ' | sed -e 's;.*/release-\(.*\);\1-canary;')
-
-# A release image "vX.Y.Z" gets built if there is a tag of that format for the current commit.
-# --abbrev=0 suppresses long format, only showing the closest tag.
-IMAGE_TAGS+=$(shell tagged="$$(git describe --tags --match='v*' --abbrev=0)"; if [ "$$tagged" ] && [ "$$(git rev-list -n1 HEAD)" = "$$(git rev-list -n1 $$tagged)" ]; then echo $$tagged; fi)
-
-# Images are named after the command contained in them.
-IMAGE_NAME=$(REGISTRY_NAME)/$*
-
-ifdef V
-# Adding "-alsologtostderr" assumes that all test binaries contain glog. This is not guaranteed.
-TESTARGS = -v -args -alsologtostderr -v 5
-else
-TESTARGS =
-endif
-
-# Specific packages can be excluded from each of the tests below by setting the *_FILTER_CMD variables
-# to something like "| grep -v 'github.com/kubernetes-csi/project/pkg/foobar'". See usage below.
-
-build-%:
-	mkdir -p bin
-	CGO_ENABLED=0 GOOS=linux go build -a -ldflags '-X main.version=$(REV) -extldflags "-static"' -o ./bin/$* ./cmd/$*
-
-container-%: build-%
-	docker build -t $*:latest -f $(shell if [ -e ./cmd/$*/Dockerfile ]; then echo ./cmd/$*/Dockerfile; else echo Dockerfile; fi) --label revision=$(REV) .
-
-push-%: container-%
-	set -ex; \
-	push_image () { \
-		docker tag $*:latest $(IMAGE_NAME):$$tag; \
-		docker push $(IMAGE_NAME):$$tag; \
-	}; \
-	for tag in $(IMAGE_TAGS); do \
-		if [ "$$tag" = "canary" ] || echo "$$tag" | grep -q -e '-canary$$'; then \
-			: "creating or overwriting canary image"; \
-			push_image; \
-		elif docker pull $(IMAGE_NAME):$$tag 2>&1 | tee /dev/stderr | grep -q "manifest for $(IMAGE_NAME):$$tag not found"; then \
-			: "creating release image"; \
-			push_image; \
-		else \
-			: "release image $(IMAGE_NAME):$$tag already exists, skipping push"; \
-		fi; \
-	done
-
-build: $(CMDS:%=build-%)
-container: $(CMDS:%=container-%)
-push: $(CMDS:%=push-%)
-
-clean:
-	-rm -rf bin
-
-test:
-
-.PHONY: test-go
-test: test-go
-test-go:
-	@ echo; echo "### $@:"
-	go test `go list ./... | grep -v 'vendor' $(TEST_GO_FILTER_CMD)` $(TESTARGS)
-
-.PHONY: test-vet
-test: test-vet
-test-vet:
-	@ echo; echo "### $@:"
-	go vet `go list ./... | grep -v vendor $(TEST_VET_FILTER_CMD)`
-
-.PHONY: test-fmt
-test: test-fmt
-test-fmt:
-	@ echo; echo "### $@:"
-	files=$$(find . -name '*.go' | grep -v './vendor' $(TEST_FMT_FILTER_CMD)); \
-	if [ $$(gofmt -d $$files | wc -l) -ne 0 ]; then \
-		echo "formatting errors:"; \
-		gofmt -d $$files; \
-		false; \
-	fi
-
-.PHONY: test-subtree
-test: test-subtree
-test-subtree:
-	@ echo; echo "### $@:"
-	./release-tools/verify-subtree.sh release-tools

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/code-of-conduct.md

@@ -1,3 +0,0 @@
-# Kubernetes Community Code of Conduct
-
-Please refer to our [Kubernetes Community Code of Conduct](https://git.k8s.io/community/code-of-conduct.md)

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/travis.yml

@@ -1,14 +0,0 @@
-language: go
-sudo: required
-services:
-  - docker
-matrix:
-  include:
-  - go: 1.11.1
-script:
-- make -k all test
-after_success:
-  - if [ "${TRAVIS_PULL_REQUEST}" == "false" ]; then
-      docker login -u "${DOCKER_USERNAME}" -p "${DOCKER_PASSWORD}" quay.io;
-      make push;
-    fi

vendor/github.com/kubernetes-csi/csi-lib-utils/release-tools/verify-subtree.sh

@@ -1,41 +0,0 @@
-#! /bin/sh -e
-#
-# Copyright 2019 The Kubernetes Authors.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This script verifies that the content of a directory managed
-# by "git subtree" has not been modified locally. It does that
-# by looking for commits that modify the files with the
-# subtree prefix (aka directory) while ignoring merge
-# commits. Merge commits are where "git subtree" pulls the
-# upstream files into the directory.
-#
-# Theoretically a developer can subvert this check by modifying files
-# in a merge commit, but in practice that shouldn't happen.
-
-DIR="$1"
-if [ ! "$DIR" ]; then
-    echo "usage: $0 <directory>" >&2
-    exit 1
-fi
-
-REV=$(git log -n1 --format=format:%H --no-merges -- "$DIR")
-if [ "$REV" ]; then
-    echo "Directory '$DIR' contains non-upstream changes:"
-    echo
-    git log --no-merges -- "$DIR"
-    exit 1
-else
-    echo "$DIR is a clean copy of upstream."
-fi