When copying data into the container, due to the id changes pointed
out in the previous attempt, the container couldn't read this data.
By creating a new user in the container, matching the host's UID/GID, we
can successfully copy data in/out of the container without worrying
about differing UID/GIDs.
See also: https://github.com/hashicorp/vault/pull/17658
Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
This appears to be due to a CI change that resulted in different user
IDs between the host and the container image.
Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
* Update go version to 1.19.2
This commit updates the default version of go to 1.19.2. This update
includes minor security fixes for archive/tar, net/http/httputil, and
regexp packages.
For more information on the release, see: https://go.dev/doc/devel/release#go1.19.2
* Update Docker versions in CI to 20.10.17
After updating Vault to go version 1.19.2, there were several SIGABRTs
in the vault tests. These were related to a missing `pthread_create`
syscall in Docker. Since CI was using a much older version of Docker,
the fix was to bump it to latest-1 (20.10.17).
While we're at it, add a note in the developer docs encouraging the use
of the latest Docker version.
* HCP link integration
* update configure-git.yml
* more OSS stuff
* removing internal repos
* adding a nil check
* removing config test to be included in ENT only
* updating hcp-sdk-go to v0.22.0
* remove Hostname and AuthURL link config params
Co-authored-by: Chris Capurso <1036769+ccapurso@users.noreply.github.com>
Update Go to 1.18
From 1.17.12
1.18.5 was just released, but not all packages have been updated, so I
went with 1.18.4
Co-authored-by: Steven Clark <steven.clark@hashicorp.com>
- Instead of installing semgrep through PyPI on every run, leverage
the upstream docker image.
- This should isolate us from dependency updates required to run newer
versions of semgrep
* Update semgrep to 0.106.0
* Add required deps to build new semgrep dependency ujson
- New Python dependency ujson for semgrep requires gcc, g++ and python3-dev.
- python3-dev to pull in Python.h
For some reason, GOPATH is being overridden in the `go mod download`
step after the latest machine image update in #15215.
This causes all of the modules to be downloaded to the
`/home/circleci/.go_workspace` cache instead of `/home/circleci/go` like
we require for the build (which will otherwise fail since we build with
`GOPROXY=off`).
Without this fix, the build will start to fail once the existing cache
is no longer used (after the root `go.mod`) is updated.
* Upgrade CircleCI machine image
* setting the path for ci-verify
* create GOPATH/bin
This is because CI failed with
cp: cannot create regular file '/home/circleci/go/bin/': Not a directory
* Update .circleci/config/jobs/pre-flight-checks.yml
Co-authored-by: Tom Proctor <tomhjp@users.noreply.github.com>
* updating config.yml
* source BASH_ENV
Co-authored-by: Tom Proctor <tomhjp@users.noreply.github.com>
* Fix semgrep 0.86.5 parsing failures
- semgrep https://github.com/returntocorp/semgrep/pull/4671 seems to have
introduce this parsing failure within version 0.86.0 and higher
- Workaround parsing failure by breaking out the if error check.
* Pin semgrep version to 0.86.5
* Fix formatting issues
* Remove unnecessary branch filters; we rely instead on exiting the jobs on inappropriate branches, since otherwise GH's required checks won't be satisfied.
* Check api and sdk dirs in go_test
* Update typo in script
* Append package names if non empty
* Don't fail command if no test packages found
* Add comments, clean up echoes
* Use pushd/popd, misc review fixes
* Update mongodb atlas plugin version
* go.mod was missing mongodbatlas plugin
* add changelog
* update build-go-dev circle ci job GOPROXY
* Revert "update build-go-dev circle ci job GOPROXY"
This reverts commit 0e6f339c779dac65ecb036735199f72d3d9e6a4a.
* ci: more complete go mod cache
* ci: doc use of go list ./... to populate mod cache
Co-authored-by: Sam Salisbury <samsalisbury@gmail.com>
* Revert "Saving and restoring the go cache was an experiment to reduce build times, but it worked too inconsistently. (#10493)"
This reverts commit 1e72bb1c41aef6648e9e219f6e44ae7942f463fe.
* make ci-config
* ci: update default go image to use docker mirror
* bump to go1.15.11
- Previously there was version skew: 1.15.10 and 1.15.4 were in use.
