Thank you for contributing to Boundary! Here you can find common questions around reporting issues and opening pull requests to our project.
When contributing in any way to the Boundary project (new issue, PR, etc), please be aware that our team identifies with many gender pronouns. Please remember to use nonbinary pronouns (they/them) and gender neutral language ("Hello folks") when addressing our team. For more reading on our code of conduct, please see the HashiCorp community guidelines.
We take Boundary's security and our users' trust very seriously. If you believe you have found a security issue in Boundary, please responsibly disclose by contacting us at security@hashicorp.com. Do not open an issue on our GitHub issue tracker if you believe you've found a security related issue, thank you!
If you believe you found a bug with Boundary, please:
- Build from the latest
mainHEAD commit to attempt to reproduce the issue. It's possible we've already fixed the bug, and this is a first good step to ensuring that's not the case. - Take a look at the Boundary Discuss to see if other folks have had similar issues.
- Ensure a similar ticket is not already opened by searching our opened issues on GitHub.
Once you've verified the above, feel free to open a bug fix issue template type from our issue selector and we'll do our best to triage it as quickly as possible.
Before writing a line of code, please ask us about a potential improvement or feature that you want to write into Boundary. We may already be working on it; even if we aren't, we need to ensure that both the feature and its proposed implementation is aligned with our road map, vision, and standards for the project. We're happy to help walk through that via a feature request issue.
You can see a public road map for Boundary on our docs site and we encourage everyone to look this over to understand at a high level what we're working on with Boundary.
When submitting a pull request, please ensure:
- You've added a changelog line clearly describing the new addition under the correct changelog sub-section.
- You've followed the above guidelines for contributing to Boundary.
Once you open your PR, our auto-labeling will add labels to help us triage and prioritize your contribution. Please allow us a couple of days to comment, request changes, or approve your PR. Thank you for your contribution!
The changelog is updated by PR contributors. Each contribution to Boundary should include a changelog update at the contributor or reviewer discretion. The changelog should be updated when the contribution is large enough to warrant it being called out in the larger release cycle. Enhancements, bug fixes, and other contributions that practitioners might want to be aware of should exist in the changelog.
When contributing to the changelog, follow existing patterns for referencing PR's, issues or other ancillary context.
The changelog is broken down into sections:
The current release cycle. New contributions slated for the next release should go under this heading. If the contribution is being backported, the inclusion of the feature in the appropriate release during the backport process is handled on an as-needed basis.
Any enhancements, new features, etc fall into this section.
Any bug fixes fall into this section.
Most tests require a postgres database instance to successfully run. This is provided via docker by running a customized postgres image that is optimized for boundary tests.
Before running the test suite, this docker container must be started:
$ make test-database-up
This can take a few seconds to initialize as it will create a template database with the boundary migrations. The progress can be checked b running:
$ docker logs -f boundary-sql-tests
Once a log line like the following is seen, the container is ready for running tests:
PostgreSQL init process complete; ready for start up.
Alternatively if the pg_isready command is installed, it can be used to
determine if the container is ready, i.e.:
$ until pg_isready -h 127.0.0.1; do sleep 1; done
To run the entire test suite run this command in the root of the project once the test database is ready:
$ make test
Before running any test please ensure that Docker is started. Boundary uses a Docker container to initiate a database for testing. If a test is interrupted check to make certain that all Docker containers have been properly destroyed.
If you don't want to run the entire test suite, you can just run a single test with go. For example, if you wanted to run the tests TestAuthTokenAuthenticator, you would run:
$ go test -run TestAuthTokenAuthenticator -v ./internal/auth
The test database container can be shutdown using:
$ make test-database-down
Note that the container does not need to be shutdown between each run of
make test or go test.
By default the container uses the host port of 5432. This can changed using an environment variable:
$ export TEST_DB_PORT=5433
$ make test-database-up
$ make test
By default the container name is boundary-sql-tests.
This can be changed in the same way as the port:
$ export TEST_CONTAINER_NAME="custom-name"
$ make test-database-up
$ docker logs custom-name
The default docker image is built using the postgres:12 base image.
The image can be changed using a make option to test against other versions:
$ make IMAGE_TAG=docker.io/hashicorpboundary/postgres:12-alpine test-database-up
$ make IMAGE_TAG=docker.io/hashicorpboundary/postgres:13-alpine test-database-up
$ make IMAGE_TAG=docker.io/hashicorpboundary/postgres:alpine test-database-up
Additional options can be passed to postgres to customize and override the configuration in the config file of the docker image. See the troubleshooting section below for more details.
The postgres configuration file included in the image is optimized to support running the full test suite in parallel in CI. As such, there may be issues starting the container locally, especially in cases where the container has less then 4GB of memory.
This is likely the case if the output of docker logs boundary-sql-tests shows:
pg_ctl: could not start server
In this case adjust the max_connections and/or shared_buffers:
make PG_OPTS="-c max_connections=1000" test-database-up
Note that if max_connections is set too low, it may result in sporadic test
failures if a connection cannot be established. In this case, reduce the number
of concurrent tests via GOMAXPROCS or selectively run tests.
Tests for the SDK and API modules can also be run. These do not require a test database:
$ make test-api
$ make test-sdk
Or all of the test can be run with a single target:
$ make test-all
Most of the indexes in the database are for enforcing data constraints. We have not added indexes for improving performance because we do not have a way to measure and test these types of indexes. We want a way to test and verify that indexes added to improve performance are actually being used by the system. And we want these same tests to fail when an index stops being used as we evolve the system. This is on our roadmap but we have not started work on it yet.