* This was initiated by new versions from Masterminds
* Linting was set to check for the same chart version as the other
checks of this were. >0.0.0-0. The -0 is important to pull in
prereleases. The latest version of semver Validate now finds
errors here properly where some were missed before
* 0.0.0 is a valid semantic version. Instead of expecting it to be
invalid in the tests to check validation now using an invalid
semantic version
Signed-off-by: Matt Farina <matt@mattfarina.com>
The other Kubernetes dependencies, such as client-go and apimachinery,
are pinned to 1.14.1 but Kubernetes itself was tracking the tip of the
1.14 release branch and picking up changes between releases. This
change pins Kubernetes to the same version as the other parts of it.
Signed-off-by: Matt Farina <matt@mattfarina.com>
This commits adds the possibility to back Tiller (or the future
Tiller-less Helm CLI) with any SQL database (only postgres has been
tested so far) to store release information.
The main motivation for this commit was to use a storage backend that
would allow releases larger that 1MB in size (ConfigMap or Secret
drivers don't, because of limits on value size in the underlying etcd
key-value store).
Signed-off-by: Étienne Lafarge <etienne.lafarge@gmail.com>
Co-authored-by: Elliot Maincourt <e.maincourt@gmail.com> (@emaincourt)
Co-authored-by: Paul Borensztein <hi@0x01.fr> (@commit-master)
Update to the latest Sprig version, which is a reversion of some of
the functions added in 2.18.
Signed-off-by: Matt Butcher <matt.butcher@microsoft.com>
* ref: Update Sprig to 2.18.0
This fixes a problem with Go 1.11 and also adds some new functions.
Signed-off-by: Matt Butcher <matt.butcher@microsoft.com>
* Added the glide.lock file.
Signed-off-by: Matt Butcher <matt.butcher@microsoft.com>
* fix: Update gRPC to get better TLS connection handling
To avoid backward compatibility breakers, we have been pinned to a very
old version of gRPC. But it appears that there have been some very
significant network fixes since then. Looking closely at #3480, it
appears that some of this fixes may be directly related to solving that
bug.
Note that this regenerates a few of the Go proto files, so the binary
wire format may be broken. That means this MUST be held to a minor
version, not a patch release.
To test:
- Build both client and server
- Install Tiller into your cluster
- Perform a number of Helm-Tiller interactions (`helm version`, `helm
list`)
Closes#3480
Signed-off-by: Matt Butcher <matt.butcher@microsoft.com>
* Switched to latest protobuf
Signed-off-by: Matt Butcher <matt.butcher@microsoft.com>
* Refactor test run to separate method
This will allow us to parallelise it more easily
Signed-off-by: Frank Hamand <frankhamand@gmail.com>
* Add --parallel flag to helm test
(No functionality in this commit)
Signed-off-by: Frank Hamand <frankhamand@gmail.com>
* Run helm tests in parallel with --parallel flag
Signed-off-by: Frank Hamand <frankhamand@gmail.com>
* Add a mutex to helm test message streams
This is to protect against data races when running tests in parallel.
Signed-off-by: Frank Hamand <frankhamand@gmail.com>
* Add tests for --parallel flag
Signed-off-by: Frank Hamand <frankhamand@gmail.com>
* Add concurrency limit for parallel helm tests
Signed-off-by: Frank Hamand <frankhamand@gmail.com>
* Add test for concurrency limit
Signed-off-by: Frank Hamand <frankhamand@gmail.com>
* Fix rebase introduced errors
Signed-off-by: Frank Hamand <frankhamand@gmail.com>
When using "helm repo add" with "--username" and without "--password",
hide user's input with a password prompt. This allows users to not
expose their passwords to the command line history.
There was an issue with functions not being able to pass to each
other. For example, the output of regex not being able to be
passed to first or last due to type issues. This update fixes
those problems
When running glide update there are errors due to pinned versions
in the glide.yaml file mixed with getting a more recent version of
kubernetes. client-go needs a newer version of go-autorest.
Note, go-autorest is pinned to v8.0.0 rather than the latest
release of v8.4.0 because kubernetes is pinned to v8.0.0.