boundary

Commit Graph

Author	SHA1	Message	Date
Jeff Mitchell	25bce9e8ff	Fix linter warnings	2 years ago
Timothy Messier	1e51dbef4f	feat(test): Add docker images for additional postgres versions	2 years ago
Timothy Messier	e255284996	feat(test): Disable JIT for test database image	2 years ago
Timothy Messier	64995854a3	feat(dbtest): Allow host to be configurable (#2538 ) Normally the tests are run on a host machine with a docker container for the database. The docker container should be accessible via 127.0.0.1. However there might be cases where the test execution is run in a docker container, or the postgres server is configured to use a different docker network, in which case the container would be accessible via some other dns name or ip. In these cases, users can now set the TEST_DB_HOST environment variable so the tests can connect to the postgres server.	2 years ago
hashicorp-copywrite[bot]	29da0bcb92	[COMPLIANCE] License changes (#3567 ) * Adding explicit MPL license for sub-package. This directory and its subdirectories (packages) contain files licensed with the MPLv2 `LICENSE` file in this directory and are intentionally licensed separately from the BSL `LICENSE` file at the root of this repository. * Adding explicit MPL license for sub-package This directory and its subdirectories (packages) contain files licensed with the MPLv2 `LICENSE` file in this directory and are intentionally licensed separately from the BSL `LICENSE` file at the root of this repository. * Updating the license from MPL to Business Source License Going forward, this project will be licensed under the Business Source License v1.1. Please see our blog post for more details at https://hashi.co/bsl-blog, FAQ at www.hashicorp.com/licensing-faq, and details of the license at www.hashicorp.com/bsl. * Update copyright file headers to BUS-1.1 * Rerun make gen This will pick up the last of the license changes * Revert "Rerun make gen" This reverts commit `dbe0968bff`. * Remove copywrite from generation script The current version of copywrite is not sophisticated enough to only apply the copywrite changes to certain subdirectories, so to avoid accidentally relicensing our api and sdk modules, we will stop running the copywrite script until such time that it can do the right thing. * License protobuf API as MPL The protobuf API files are used to generate the SDK, since we want the SDK to be MPL, the protobuf files must also be MPL. This extends to all protobuf files whose sources end up in the SDK directory, including: - internal/proto/controller/api - internal/proto/controller/custom_options - internal/proto/plugin It also includes the generated service directory in internal/gen/controller/api/services, since they are generated from the protobuf sources used for the SDK. * Change website license file name This makes the naming scheme consistent with the rest of the repository. * Add note on licensing to README * Set copywrite license to BUSL * Revert "Add note on licensing to README" This reverts commit `4d865a91a7`. --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com> Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>	3 years ago
Jeff Mitchell	8322916fb4	Remove all deprecated Err/Wrap/E calls (#3286 )	3 years ago
Michael Gaffney	41bdfb4406	fix(db): Fix time zone consistency issues in monthly billing views The hcp monthly billing views build a range of buckets using the `generate_series` and the `now()` functions along with relative offsets like `+ 1 month`. The calculated start and end times for these views can vary depending on the time zone setting of the PostgreSQL server. This adds 3 table functions that call their respective views with the time zone set to UTC. Calling these functions instead of their underlying views directly prevents the returned values from varying when the server's time zone is not set to UTC. This also drops support for PostgreSQL 11. The included tests use the `date_trunc(field, source [, time_zone ])` function added in PostgreSQL 12. Fixes: `41b1b5b4b7`	3 years ago
Jim	d4e537c88d	chore: updgrade pgx direct deps to v5 (#3258 )	3 years ago
Timothy Messier	5e0957eb24	ci(test): Use docker mirror (#3018 )	3 years ago
Johan Brandhorst-Satzkorn	3c29308673	chore: Add license headers to all files	3 years ago
Johan Brandhorst-Satzkorn	da9adb0c02	feat: Build docker dev images for specified platform (#2493 ) Previously, building this target on an ARM machine would produce an image with a amd64 binary inside an arm OS.	3 years ago
Timothy Messier	eb61ac6304	refact(session): Add context to session factory This adds a context to the session.RepositoryFactory, allowing errors.NewDeprecated to be replaced with errors.New. It also removes the common.SessionRepoFactory, instead packages just directly import from the session package.	4 years ago
Johan Brandhorst-Satzkorn	de2c40fa77	Fork pgtap-docker to support arm64 (#2411 ) * feat(sql): Fork pgtap to support arm64 This forks pgtap-docker and builds the image locally, and updates our references to use our forked image. * fixup! feat(sql): Fork pgtap to support arm64	4 years ago
Johan Brandhorst-Satzkorn	aef9073fa6	Upgrade to Go 1.19 (#2347 )	4 years ago
Damian Debkowski	27e9f775be	feat: add initial migration hook	4 years ago
Todd	19b549c44a	Rename package servers to server (#2222 )	4 years ago
Todd	e379234259	Remove CanonicalAddress, GetApiTags(), and NewWorkerForStatus. (#2196 ) Minor testing tweaks are also included.	4 years ago
Todd	731a45eba6	Merge the worker_status table with the worker table (#2111 )	4 years ago
Todd	a281d10206	Add worker config table and view (#2090 ) * Remove the server_id from session table, change it to worker_id on session_connection This is step 1 in updating the worker table. The worker is becoming a public resource so it must have a public id. We drop the server_id column on the session_connection table and add the worker_id column so we can use the wt_public_key type. Since db migrations are applied while the controller is offline, it should be safe to assume all session connections are not in a running state, thus allowing us to null out all the worker ids in the session_connection table. For now we don't have very good enforcement of the wt_public_id constraints, since the id is currently defined in the worker config, but this will soon change and the worker's id will be generated by the controller.	4 years ago
Todd	2ecd550e27	Add fields to server_worker to be a boundary resource (#2083 ) * Remove the server_id from session table, change it to worker_id on session_connection This is step 1 in updating the worker table. The worker is becoming a public resource so it must have a public id. We drop the server_id column on the session_connection table and add the worker_id column so we can use the wt_public_key type. Since db migrations are applied while the controller is offline, it should be safe to assume all session connections are not in a running state, thus allowing us to null out all the worker ids in the session_connection table. For now we don't have very good enforcement of the wt_public_id contraints, since the id is currently defined in the worker config, but this will soon change and the worker's id will be generated by the controller. * Updating server_id references to controller_id. * Adding worker tag db writing test. * Move the server table back to the top. * Update comment for the worker object. * Update comment for the worker table. * Update the newWorkerId call to take a context and fix its error. * Correct comment for the wt_network_address domain.	4 years ago
Todd	472d7d520a	Remove the server_id from session table, change it to worker_id on session_connection (#2070 ) * Remove the server_id from session table, change it to worker_id on session_connection This is step 1 in updating the worker table. The worker is becoming a public resource so it must have a public id. We drop the server_id column on the session_connection table and add the worker_id column so we can use the wt_public_key type. Since db migrations are applied while the controller is offline, it should be safe to assume all session connections are not in a running state, thus allowing us to null out all the worker ids in the session_connection table. For now we don't have very good enforcement of the wt_public_id constraints, since the id is currently defined in the worker config, but this will soon change and the worker's id will be generated by the controller.	4 years ago
irenarindos	9e27605213	refact(servers): Split server table into worker and controller	4 years ago
Johan Brandhorst-Satzkorn	21b0d584ad	feat(dbtest): Add benchmark dump generator Generate dumps ahead of time so that they can be used for benchmarks without prohibitive startup costs. Fixes https://hashicorp.atlassian.net/browse/ICU-4039	4 years ago
Johan Brandhorst-Satzkorn	e864652b33	feat(sessions): Add list benchmarks The list benchmark tests uses pre-created database dumps to run its benchmarks. This benchmark will be used to guide optimizations around listing of sessions. Fixes https://hashicorp.atlassian.net/browse/ICU-4042	4 years ago
Johan Brandhorst-Satzkorn	5d042c7ec7	feat(dbtest): Mount DB dumps and create templates Mount the benchmark dump directory when running the test database and create a new script for creating templates from the dumps. This makes it easy to create pre-populated databases for benchmark tests. Fixes https://hashicorp.atlassian.net/browse/ICU-4040	4 years ago
Johan Brandhorst-Satzkorn	a7a2c82931	feat(dbtest): Add docker-load Makefile target The new docker-load target uses docker buildx to build a local image of each of the Dockerfiles, and load them into the local docker socket image store.	4 years ago
Johan Brandhorst-Satzkorn	89196f2ce7	Remove old migration code & Avoid db test image confusion (#2038 ) * refact(dbtest): Remove old migration code This is no longer needed, so we can clean up this script a bit. * refact(dbtest): Change test image env var The existing environment variable clashes with the one used in the top level Makefile. The new name prevents confusing behavior when setting the env var and creating the test database from the root of the repository.	4 years ago
Timothy Messier	839f9efcfb	chore(dbtest): Build test database docker image for arm64 This adds a new makefile target to build and publish the test database docker image for multiple architectures. It will create images for: - linux/amd64 - linux/arm64 The target uses docker buildx to build the images. To build the images: docker buildx create --driver docker-container --use make docker-buildx docker buildx rm See: https://docs.docker.com/buildx/working-with-buildx/	4 years ago
Timothy Messier	34d9842f85	fix(testing/docker): Correctly reset IFS (#1754 )	4 years ago
Timothy Messier	35a7c4f6e7	feat(dbtest): Make test container name configurable	4 years ago
Jeff Mitchell	d58e7670f1	Make PG resource usage nicer for dev (#1615 ) This overrides settings specifically in CI scenarios to the current values but reduces the resource requirements for local dev work.	4 years ago
Timothy Messier	2143940a4a	refactor(dbtest): Support new paths for migration files This updates the docker image used for tests to support the new location for sql migration files and the concept of editions. It continues to process the old paths for now if the new directory does not exist, so that the same image can be used during the transition.	4 years ago
Jim	8d6dee09a9	refact: Add db.DB wrapper and refact all test fixtures to use it. (#1535 ) * refact: Changes required for gorm v2 * refact: Add db.DB wrapper and refact all test fixtures to use it Stop leaking the gorm abstraction within our unit tests. * refact: Migrate direct calls to pq to pgx driver The refactor will remove the remaining direct dependencies on the pq driver which has been deprecated in favor of the pgx driver. It includes the addition of common.SqlOpen which is a wrapper around sql.Open, which is needed to deal with the driver name changing from "postgres" to "pgx" but in our code base the dialect and driver are synonyms.	4 years ago
Louis Ruch	96b0c18f25	docs(dbtest): corrects echo in makefile (#1548 ) After running make test-database-up, the output gave the incorrect command to run to see docker logs.	4 years ago
Todd Knight	e3986d5f9c	Running make fmt to fix formatting.	4 years ago
Timothy Messier	af5d1af568	test: Add dbtest package This is modeled after the internal/docker package to make it easy to use as a replacement. Instead of creating a new docker container for each test, it will create a new database in an existing database container, using a template database as a source. This assumes that the template database exists and already has the schema migrations run against it. The default template is `boundary_template` which should already have all migrations applied. However, some tests require an empty database to test the migration code. In these cases the `template1` template database should be used, ie: dbtest.StartWithTemplate("postgres", dbtest.WithTemplate("template1"))	5 years ago
Timothy Messier	c6cb7c8512	chore: Define custom docker image for tests This images is built from the official postgres docker image, but with updates to optimize the test execution: - A config file for postgres to increase the performance of the test server. - An initialization script to create a template database with all migrations run against it. There are new make targets to build and publish this docker image. The image can be pulled with: docker pull hashicorpboundary/postgres:13-alpine To use this image for tests start the container: make -C internal/db/docker database-up	5 years ago

37 Commits (fcafffdb24b84bba85d06fb208778efe2b9201c7)